gRDV Messages
| 开发者 | grdv |
|---|---|
| 更新时间 | 2026年9月2日 17:52 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Connect and manage multiple mailboxes with individual IMAP and SMTP settings.
- Assign WordPress users to authorized mailboxes for mobile access.
- Synchronize selected folders and perform supported move or delete operations on the configured IMAP server.
- Use near-live, focus-boost and burst synchronization while the web app is open.
- Send new messages and replies through the selected SMTP account.
- Keep incoming and outgoing messages grouped as conversations.
- Use one HTML reply template, a signature and brand styling.
- Use a separate follow-up signature for later replies in a conversation.
- Upload, receive and send attachments.
- Store attachments locally with authenticated encryption and random physical filenames.
- Filter conversations by mailbox and folder.
- Move messages between supported IMAP folders, move them to Trash or delete them permanently.
- Use a mobile web app for the inbox, conversations, new messages and replies.
- Keep account passwords encrypted with the WordPress authentication salts.
- Export or erase email-related local records through the WordPress privacy tools.
- Optionally delete local message copies and encrypted attachments after a configurable period.
安装:
- Upload the plugin folder to
/wp-content/plugins/or install the plugin through the WordPress plugin screen. - Activate
gRDV Messages. - Open
gRDV Messages > Mailboxen. - Enter the IMAP and SMTP settings for each mailbox that you are authorized to use.
- Send a test message and start syncing conversations.
屏幕截图:
常见问题:
Does gRDV Messages replace my email provider?
No. gRDV Messages connects to the mailbox and mail servers configured by the site administrator. Your existing email provider remains responsible for storing and delivering mail.
Can I use any sender address?
You can connect mailboxes from domains other than the WordPress installation domain. Each sender address must belong to a mailbox that you are authorized to use and for which you provide valid IMAP and SMTP credentials. gRDV Messages does not provide or authorize sender identities on your behalf.
Can I manage more than one mailbox?
Yes. You can configure multiple authorized mailboxes with separate IMAP, SMTP, sender, Reply-To, folder and user-assignment settings.
Does gRDV Messages restyle every email sent by WordPress?
No. The template and signature apply to messages composed and sent through gRDV Messages and to explicitly supported integrations. The plugin does not automatically replace email templates from WordPress core, WooCommerce, form plugins or unrelated third-party plugins.
Which external services does the plugin connect to?
The plugin connects only to the IMAP and SMTP servers entered by the site administrator. It does not connect to gR DV servers or any other vendor-operated service.
How does the external cron URL work?
The plugin can generate a private local sync URL for server-side cron jobs. Calling this URL triggers the IMAP sync inside your own WordPress installation. The request stays on your site and uses a token generated by the plugin; no email content, mailbox data or token is sent to gR DV.
Where are messages stored?
Synced messages, outgoing messages, conversation metadata and attachment metadata are stored in your WordPress database. Attachment files are stored locally below wp-content/uploads/grdv-messages/. The files use authenticated encryption and random physical filenames and are only decrypted in memory for authorized downloads and sending. Original filenames and MIME types remain in the database. No Apache, Nginx or IIS configuration is required.
The encryption key is generated independently when the first attachment is stored and saved as a non-autoloaded WordPress option. Include both the WordPress database and the uploads directory in backups; attachments cannot be decrypted if the database copy containing this key is lost.
When synchronization is disabled for a folder, locally imported messages that are assigned only to disabled folders are deleted in resumable background batches. Their locally stored attachment files and metadata are deleted as well. Empty conversations and contacts that are no longer referenced by another conversation are removed. A message remains stored if it is also assigned to a folder that is still enabled for synchronization. Copies in WordPress, database, hosting or external backups are controlled by the site operator and are outside the plugin's active storage.
Enable synchronization for the Trash folder of each mailbox when the plugin should detect messages that are later removed from Trash on the IMAP server. Folder visibility in the WebApp is independent of synchronization. Messages that were moved to and removed from an unsynchronized server folder cannot always be matched safely after the fact, so conversation and message rows should not be deleted directly from the database without also accounting for attachments and IMAP references.
Are mailbox passwords stored securely?
Mailbox passwords are encrypted with authenticated AES-256-GCM encryption before they are saved. The encryption key is derived from the WordPress authentication salts available on the site. Site administrators should still protect database, configuration and file-system access carefully.
更新日志:
- Remove a conversation from the WebApp immediately when it is moved to another folder, while the server request continues in parallel.
- Restore both the conversation list item and the open desktop detail panel automatically when a folder move fails.
- Clear the desktop detail panel reliably when its active conversation is deleted from the conversation list.
- Attach Push device context to folder moves and modern or legacy conversation deletion requests so Pro can synchronize badges without notifying the device that initiated the change.
- Update the plugin author branding to gR DV throughout plugin metadata, documentation, privacy text and bundled translations.
- Add generic per-thread WebApp authorization for extension-provided local conversation contexts.
- Allow extensions to adapt local thread presentation, displayed messages, unread totals and thread actions without changing the email data model.
- Add extension points for separate WebApp thread groups, message tools, status polling and deferred read acknowledgement.
- Show selected attachments before sending and allow individual files to be removed or replaced in replies and new messages.
- Exclude document-head and hidden preheader content from compact mobile message previews.
- Redesign the WordPress administration to match the shared gR DV visual system used by Anchor Transition and Widerruf.
- Add a consistent hero, section navigation, numbered settings cards and responsive sticky save status across the Messages backend.
- Save Template, Design and Settings changes automatically through a nonce-protected AJAX endpoint with permission checks and classic form submission as a fallback.
- Synchronize TinyMCE content before automatic saves and keep Free and Pro settings on the existing field-level sanitization path.
- Refresh template and signature previews immediately after automatic saving and place the compact reply editor directly above its preview.
- Compose the complete template preview before extension-provided preview elements are positioned.
- Highlight invalid automatic-save fields and move focus to the first field that needs correction.
- Confirm compatibility with WordPress 7.1.
- Count WebApp unread messages only when the message itself has an active IMAP reference in a synchronized, visible folder.
- Exclude stale unread rows whose former IMAP location is already marked as deleted.
- Limit the WebApp badge total to mailboxes authorized for the current user.
- Document Trash synchronization requirements and safe local cleanup behavior.
- Add German and British English translations for the background Sent-folder import progress.
- Align plugin metadata, request-header handling, database annotations, translation loading and uninstall cleanup with WordPress.org Plugin Check requirements.
- Import externally sent messages from enabled Sent folders and attach them to the matching conversation using message headers, participants and normalized subjects.
- Include the selected mailbox in WebApp synchronization and synchronize every active mailbox through authenticated external cron requests.
- Prevent Sent-folder messages from being skipped when an IMAP server advances UIDNEXT before the message becomes searchable.
- Import large existing Sent folders in resumable background batches with visible progress while prioritizing newly sent messages.
- Keep remote IMAP IDLE restricted to an active, licensed Pro installation while regular Free synchronization remains available.
- Remove the temporary message-card focus outline after pointer interaction without affecting keyboard accessibility.
- Add an opt-in, privacy-conscious synchronization trace for targeted diagnostics without enabling WordPress debug logging.
- Change all translatable source strings to US English for compatibility with WordPress.org language packs.
- Add separate German translations for informal and formal address.
- Update British English translations and localize previously hard-coded WebApp fallback labels.
- Clarify that the PHP IMAP extension is a mandatory server requirement for retrieving and synchronizing email.
changelog.txt.