#1480 new

issues with redirecting mail from sent folder

Reported by Lars | June 4th, 2016 @ 11:52 PM

Hi Benny

I am having trouble with redirecting mail from my sent folder.

What I am trying to achieve is that mail I once sent out myself gets redelivered via my incoming mail server (because that server encrypts incoming mail). The server will then move the now encrypted mail to my sent folder and I have rules in place in MailMate to a) delete the unencrypted original as well as the redirected mail from my sent folder and b) mark the new message as read.

First issue (redirection only working once):

I am trying to trigger the redirecting via rules as well, so I have set up a rule in my sent folder that triggers on unencrypted messages and redirects them to a specific address. However, when I have already redirected a message in the past, the rule stops performing. It does still trigger (I have defined a sound action besides the redirecting for it), but it does not actually redirect the mail again. Manual redirection works well.

I have tried to remove the $Redirect flag and also Reset the mail to have it refetched from the server. Still, the rule doesn't seem to perform on mails that have once been redirected before. The rule itself triggers (hearing the sound), but it doesn't trigger another redirect. Again, manual redirection works well.

How do I make sure redirection works every time? (Mainly important for debugging now, but also confusing behaviour not to.)

Second issue (determining wrong account when redirecting sent folder messages):

When I redirect mail that was originally sent to an address that is also set up in MailMate (be it as another account or as an e-mail address in one of the accounts), MailMate is trying to be clever and chooses that account as the originating account for redirecting the mail. I would prefer to have the same server redirect the message that currently holds the message, which in case of mails stored in the sent folder, usually is not the server from the To header field.

Suggestion: Allow to specify an account to use for redirection or disable MailMate's smart prediction for the account to use when redirecting messages from the sent folder.

Looking forward to your valued reply :-)

Comments and changes to this ticket

  • benny

    benny June 6th, 2016 @ 12:54 PM

    • State changed from “new” to “accepted”

    First issue: In order to prevent infinite redirection issues then I put in a limit which means that a message can only be redirected once (within some period of time). I recently changed that to 5 redirects. Hold down ⌥ when clicking “Check Now” in the Software Update preferences pane to try this out.

    Second issue: In other words, I should disable the follow-up detection when doing redirects. I guess that makes sense.

  • Lars

    Lars June 9th, 2016 @ 06:57 PM

    First issue: I was using multiple redirects in a row for debugging (the second issue). Have updated to v5249 and multiple redirects work now.

    Just thinking out loud here, but wouldn't it make sense, since you are setting the $Redirect flag anyway, to reset your counter (may it be 1 or 5) whenever the $Redirect tag is removed from a message? Generally, the counter is a great idea, though, I just had a nice loop going on ;)

    Second issue: I'll keep an eye on this ticket for a fix there! It would make my life a bit easier since I currently have to redirect every sent mail and when I write mails from one of my addresses to another, the follow-up detection keeps changing the account, making an error message pop up (or worse).

    As a side note, when I updated to v5249, I have seen you introduced retiredAddressPattern recently. Please make sure those don't interfere with redirects, either :) I haven't tested it yet as I'm not entirely sure how to use the feature.

  • benny

    benny June 12th, 2016 @ 02:34 PM

    First issue: You mean if the user has cleared the $Redirect tag then the loop detection should be disabled. I guess that makes sense although I doubt that would be needed very often.

    The retiredAddressPattern should not result in any problems. Its purpose is for the user to state that an email address belongs to the user, but it's no longer in use. In other words, when replying then a different identity should be used while the old address is still automatically not used for cc.

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.

New-ticket 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.

Shared Ticket Bins

People watching this ticket