If that was the issue then forwarding only non-spam would not work correctly and end up forwarding everything, right? So it’s definitely been processed by SpamAssassin and marked as spam before it hits any of the sieve rules, since the filters I use for sending non-spam only rely on the SpamAssassin headers. No, I don't actually think that’s the issue in this case. So why not add a sieve rule after it hits the spam folder to delete or only keep X days worth? It sounds like you're trying to catch spam before it's marked as spam, then when it is, it gets put into the spam folder correctly, but you don't process it further. In my cases, they still arrive in the Spam folder which seems to be incorrect said in Can't discard spam messages on arrival using Sieve filters: See if the message is really discarded per the sieve filter or if it's still arriving in the Spam folder. Send a message to the email account using the GTUBE string which SpamAssassin automatically marks with 1000 points, it's basically a test for spam filters: XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X Basically I can't get any filters to work when it's been identified as spam, only filters when it's NOT spam. no filter) after the redirect rule is applied, but still no-dice. I've tried variations of it too such as apply to all messages (i.e. will still see the email saved in the Spam folder. If allof (header :contains "x-spam-status" "Yes,") It seems maybe there's a priority filter going on elsewhere in Cloudron that's overriding my sieve filter? In my case, I want the spam messages to be discarded/deleted automatically as there's no sense in them remaining in the "forwarding only" mailbox. However, all messages marked as spam still save in the mailbox regardless of any filters I set to discard them. If allof (not header :contains "x-spam-status" "Yes,") I was able to setup redirects in the mailbox and they are working where they only forward non-spam messages by using the following filter: # rule: Use case: Discard spam messages on arrival using Sieve filters via Roundcube. Feedback is welcome.I am writing a dedicated bug report based on a post I made in another thread. The following sections describe some of these features, but remember that anything in this section can change in future updates of MailMate. This is typically features which have no graphical user interface. MailMate is under continuous development and many features implemented in MailMate have only reached an experimental level. Quit MailMate and edit the following file: You can work around this problem by explicitly telling MailMate that it’s a retired email address. This won’t work if you have listed the email address in one of your accounts, but if you have not listed it then MailMate is going to put the address in the “Cc” field (if you reply to all). If you have one or more email addresses which you no longer use for sending emails then you might face the following problem: After receiving an email sent to such an address then you would like to reply to it using a different email address. Here are the values needed for the bundles currently available. The UUID argument is a bit tricky to find. The definition of “next” can be controlled using the following preference:ĭefaults write MmBundleCommandLaunchedOnTab "46C1F8A8-A069-4E54-A427-30D45342674F" When moving or deleting a message MailMate automatically selects the “next” message in the current mailbox. Make sure the color used is supported on your version of macOS. It makes emails pending deletion colored red similar to what is currently fully hardcoded in MailMate.Ī color can also be one of the standard system color names. The last example is currently a semi-hardcoded option. The second example is the mailbox type which colors messages which are in any one of the available mailboxes and smart mailboxes (the UUID value of a mailbox can be put on the pasteboard by selecting the mailbox and then hit ⌘C). This can also be used for tags (which always map to an IMAP keyword). This colors emails matching a specific IMAP keyword. The first example is of the keyword type. FontStyle = "italic" // boldAndItalic can also be used
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |