Read-only server support
Reported by Pete | April 15th, 2020 @ 07:52 PM
I use MailMate to read the mail archive on the IETF server. With an account, you get read-only access to a bunch of mail folders (all within "Shared Folders" at the top level), you can subscribe or unsubscribe on the server to any of those folders that you want, you can set flags on messages (they are your own private set of flags; other people set their own flags), but you cannot add or remove messages or folders from the server. For the most part, MailMate deals with this reasonably well, but it does have some problems:
-
If you reply to a message (which it will attempt to do using the email address in the configuration info for this account) and then save the draft of the message, it attempts to create a Drafts folder. It creates the local folder, puts the message in the local folder, but fails when it tries to sync.
-
If you attempt to send the above message, it attempts to send it using the SMTP server in the configuration panel for this account and then create a Sent Messages folder and move the message to there, which fails upon attempt to sync.
-
If you try to delete a message (including any in the useless Drafts or Sent Messages folders), it attempts to create a Deleted Messages folder. Again, attempts to sync fail.
Ideally, MailMate would discover the nature of the server being read-only and then ask you which other account you would like to use for replies, and prevent you from deleting messages (or only mark them for delete but don't attempt to move or expunge them). I don't want the server treated as completely read-only, because I do have writeable flags.
You can play with this on the IETF server. Instructions for access are here:
https://trac.tools.ietf.org/group/tools/trac/wiki/Imap
And if you want to create an account for yourself so you can have writeable flags, you can do so here:
Comments and changes to this ticket
-
Pete April 15th, 2020 @ 07:53 PM
- no changes were found...
-
benny August 20th, 2020 @ 01:42 PM
- State changed from “new” to “accepted”
I haven't tested this:
- Try removing the email address from the Email Address(es) field
of the settings. This is what implicitly tells MailMate that emails
can be sent from this account.
- Given 1. then this shouldn't happen.
- That one is trickier. I'll update the ticket if I find a solution for that.
-
Pete February 2nd, 2022 @ 08:52 PM
- State changed from “accepted” to “new”
Update to this ticket: If you remove the email address from the Email Address(es) field, it attempts to send using whatever account is first in its list, which is definitely the wrong one in my case. Is there a way to assign an account to send from when there is no email address?
-
benny February 23rd, 2022 @ 03:49 PM
There's only the global “Default Account” setting in the Composer preferences pane, but this is still overridden if MailMate recognizes the recipient of the email as someone you have written to in another account.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Mac OS X email client.
benny