Common Issues

Check which mail resource you are using

These pages describe murphy_post, sold as Murphy's Telegram & Mail. The older murphy_telegram is a separate resource. Its configuration paths, events and updates are not interchangeable with Post. Check the folder and fxmanifest.lua before following an old support answer.

For installation, use Installation. Preserve documents, inbox records and item metadata when updating.

Sending, receiving and reading mail

A letter or telegram was sent, but the recipient's inbox is empty

Check these stages separately:

1. Was sending accepted, or did the sender receive an error?
2. Was it addressed to a person or to a shared mailbox?
3. Has the configured delivery delay elapsed?
4. Is the expected recipient or mailbox member checking the correct inbox?

Config.Delays controls delivery timing. An accepted send does not imply immediate delivery. Do not mark database rows as delivered or resend repeatedly while diagnosing a delay.

On VORP, support confirmed an inbox-insert bug corrected in 1.1.1. If documents are created but no inbox entry follows, check the installed adapter and first server error. Keep the failed document for diagnosis instead of deleting all mail.

The document is in the inbox, but pickup gives no inventory item

Check the exact names in Config.Items.letterItem and Config.Items.telegramItem in config/config.lua. The usual names are post_letter and post_telegram; your item registry must match the configured values.

An inventory carry check can fail because the item is unregistered or because the player cannot carry it. Verify both the definition and capacity. Add missing definitions using your inventory version's schema, then test one new document. Do not copy a generic SQL insert that assumes another server's columns or limits.

Using a letter or telegram item does not open it

Distinguish pickup from use: does the item actually exist in the inventory, and does its metadata identify the document? Compare a newly sent document with the affected item. Historical VORP item-use handling was corrected in 1.3.2. Update the matching adapter and preserve metadata; an ordinary item with the right display name is not necessarily a valid saved letter.

A recipient with spaces or accents cannot be found

The public 1.11.0 notes correct compound names with interior spaces. 1.13.0 adds case/accent-tolerant lookup and further compound-name handling. Check the exact stored character name and installed release. Do not rename all characters or remove spaces from the database.

Duplicate character names are a separate reported case without a confirmed resolution in the reviewed thread. For a custom integration, consult the recipient identifier supported by External API. Do not assume name normalization makes two identical names unique.

Why are there two post-office interactions?

Personal mail and a shared job mailbox serve different recipients. Check the configured mailbox and job access before treating the second prompt as a duplicate. See Configuration. A shared mailbox is not the same as a player-owned home mailbox.

How do I connect a home mailbox from another housing resource?

Use Player Home Mailboxes and its example integration. Compatibility with an unrelated housing resource is not automatic just because both resources have a mailbox prop. The integration must register the correct owner, location and mailbox lifecycle.

Post offices and interface

A post-office menu is slow or freezes

Capture the menu-opening action, the first F8/server error and a resource profile while opening it. Distinguish a slow interface from the configured mail delivery delay. Support has investigated inventory lookups in this flow; changing Config.Delays cannot repair an expensive menu-opening call. Test with the complete current Post and interaction-resource files before changing timers.

I set the clerk model to nil but the NPC still appears

Post 1.22.0 introduces disableNpc = true on an individual entry in Config.PostOffices; pnj = false is also supported in that release. The office interaction, blip and mail menu remain available. Merge the field into the existing office entry. Do not replace the complete office table with only this property, and do not expect the option to work on an older release.

Can I hide one post-office blip?

The public 1.13.0 notes add Config.Blips with global and individual controls. Use the complete structure supplied by your installed release. Removing a clerk and hiding a blip are separate settings.

Telegram fonts differ, or the interface language changed but labels did not

Telegrams use a randomly selected configured font; letters allow a font choice. For language, distinguish the UI selection and ui/lang.json from Lua labels in config/lang.lua. Preserve placeholder names and merge new keys when updating. See Templates & Stationery.

If the issue remains

Report the resource folder name, installed version, framework and inventory version, failing step, first error and whether the test used a person, shared mailbox or home mailbox. Use a test document without private correspondence, account identifiers or credentials in the report.

Sources: reviewed support cases and Versions on the Telegram & Mail product page, checked 10 September 2026. Release-specific fixes and diagnostic steps are distinguished here; the scenarios were not reproduced in RedM for this article.