WoW Forever Mail: Recipients, Items, and Gold
What saved mail controls define, plus the surname reports worth checking before a valuable send.
By HarenilPublished
Use this as a dated control reference, not a live mail walkthrough. The source names compose, postage, attachment, COD, retrieval, and return controls; player reports make exact recipient checks prudent before valuable sends.
Ask Our Sweaty Degenerate AI About Mail
Recipients, Postage & COD, Attachments, Return Controls, Bug Reports & More
Anything our guides cover. Answers come from this page and the rest of our guides, with the real values charted and the guide sections linked. It's AI, so check the source before you quote it.
TL;DR
The 1.60.1.70205 source defines mail fields and buttons, but its load path is mainline-scoped and Forever applicability is unresolved. No send or receipt was observed.
On This Page
Short Answer
The saved 1.60.1.70205 mail source defines a recipient field, subject and body fields, money entry, item-attachment controls, a postage display, a Send control, received-item controls, a COD confirmation path, and a Return control. These are code-defined controls, not proof that a Forever server accepts a message, transfers an attachment, or delivers it to the intended character.
The extracted mail-frame load file allows the Game add-on for mainline only. The bounded source set shows no Camelot mail-frame load path, so Forever applicability remains unresolved. Read the fields below as a snapshot reference and confirm the controls in your own current client before relying on them.
Compose and Receive Control Reference
Swipe sideways to see all columns.
| Task | What the source defines | Evidence boundary |
|---|---|---|
| Compose | Recipient autocomplete, subject, body, money input, item slots, postage display, and Send button. | A visible control definition, not a successful send. |
| Postage | The displayed amount is queried through GetSendMailPrice(). | No fixed fee or postage formula is provided here. |
| COD | The client source caps the input at 10,000 gold and includes a confirmation control. | UI input limit, not confirmed server acceptance or transfer. |
| Receive | Open mail exposes item and money retrieval controls. | No attachment was retrieved in this review. |
| Return | A control calls ReturnInboxItem for the open message. | A callback, not proof of a returned message. |
The source defines 12 outgoing attachment slots and 16 incoming slots. Those counts describe controls in the extracted code; they do not establish allowed item types, a server-side transfer maximum, or that the Forever client loads the same frame. Delivery time, restrictions, fees, and failure recovery are not supplied as confirmed values here.
Read the Recipient Carefully
Blizzard's naming article says a character's full name has first and last parts, and the complete combination is unique within its region. The article does not explain how the mail recipient resolver parses names. In the code snapshot, the compose callback passes the text entered in the recipient, subject, and body controls into SendMail. The send-button checks required fields and the COD amount; a button or callback still does not demonstrate a completed transaction.
Before sending a valuable item or amount, compare the intended character identity with the recipient entry. Do not assume a matching first name is enough. Blizzard announced a fix for mail ignoring surnames on September 24. On October 4, a forum player recalled the same-first-name self-mail error and said they thought it was fixed; an October 7 reply said they had experienced it, without a date. Neither post establishes that the bug returned after the fix.
- Confirm the complete recipient identity.
- Review subject, attachments, and entered money.
- Read the postage value the client displays.
- Check COD details before confirming.
- Treat Send as a control, not a receipt.
The source-based takeaway is to verify before sending something valuable. The official fix announcement and later player reports should remain visible together; neither guarantees current recipient resolution. No mailbox was opened, no message was sent or received, and no mail transaction was tested for this page.
Every row carries an evidence icon: Confirmed, Planned, Reported, Unverified or Not announced. Hover, focus or tap one for its source. Where sources disagree, both stay on the page. How we verify