Sieve rule for whitelisting domains after spam processing
Hello,
My mail server has a global Sieve rule defined in sieve_before to file
messages classified as spam by spamassassin into the Spam folder:
require ["regex", "fileinto", "imap4flags"];
if allof (header :regex "X-Spam-Status" "^Yes") {
fileinto "Spam";
}
This works great, except I'd like the ability to whitelist certain senders
or domains whose emails end up in Spam, usually due to a misconfigured SPF
DNS TXT record or something like that. I use Roundcube as my Webmail
client, so the easiest way to whitelist would be to create a rule for each
domain directly in Roundcube using its built-in Sieve integration to move
legitimate messages out of the Spam folder. I already have several rules
set up to flag and sort non-spam messages, and they're working fine. I
therefore tried adding a simple rule to move Spam into the Inbox:
# rule:[Not Spam]
if allof (header :contains "from" "u...@good-domain.com")
{
fileinto "INBOX";
}
However, the above rule does not work as I expected. When I receive an
email from good-domain.com that's classified as Spam by spamassassin, the
global rule sends it to the Spam folder and it is not re-filed into the
Inbox. The second rule doesn't seem to do anything. I'm probably doing
something simple wrong, but I can't figure out what (I'm a Sieve newb). Any
suggestions please?
Thanks,
Nick
Re: Submission Service Copy To Sent
On 8/9/2022 11:05 AM, spi wrote: Am 09.08.22 um 18:56 schrieb Asai: Greetings, We've had a longstanding problem with emails not being copied to the Sent folder that seems to be a bug with various email clients (Thunderbird, TypeApp.) I know that Dovecot has the option to use the Submission service to copy emails to Sent without using SMTP to do this. Would this solve the problem we've seen over the years of emails not being copied to the Sent folder on various clients under certain (unknown) conditions? I had the same issue some time ago, If I remember right, with submission the IMAP client needs to support some additional IMAP features which most clients currently don't do. I did it the other way round - my clients send mails by smtp and a postfix milter script catches the mail on the mail server and copies it locally to the user's IMAP mailbox - the clients don't upload any sent mails by IMAP anymore. Am using mailfromd as milter: https://puszcza.gnu.org.ua/software/mailfromd/ -- Cheers spi Thank you for your helpful response, Asai
Re: Submission Service Copy To Sent
Am 09.08.22 um 18:56 schrieb Asai: Greetings, We've had a longstanding problem with emails not being copied to the Sent folder that seems to be a bug with various email clients (Thunderbird, TypeApp.) I know that Dovecot has the option to use the Submission service to copy emails to Sent without using SMTP to do this. Would this solve the problem we've seen over the years of emails not being copied to the Sent folder on various clients under certain (unknown) conditions? I had the same issue some time ago, If I remember right, with submission the IMAP client needs to support some additional IMAP features which most clients currently don't do. I did it the other way round - my clients send mails by smtp and a postfix milter script catches the mail on the mail server and copies it locally to the user's IMAP mailbox - the clients don't upload any sent mails by IMAP anymore. Am using mailfromd as milter: https://puszcza.gnu.org.ua/software/mailfromd/ -- Cheers spi
Re: Submission Service Copy To Sent
As far as I know, the copy to "Sent" folder is done by using IMAP, not SMTP. This is for client non-local storage. Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 9/8/22 a les 18:56, Asai ha escrit: Greetings, We've had a longstanding problem with emails not being copied to the Sent folder that seems to be a bug with various email clients (Thunderbird, TypeApp.) I know that Dovecot has the option to use the Submission service to copy emails to Sent without using SMTP to do this. Would this solve the problem we've seen over the years of emails not being copied to the Sent folder on various clients under certain (unknown) conditions? Thanks for your insight here. Asai
Submission Service Copy To Sent
Greetings, We've had a longstanding problem with emails not being copied to the Sent folder that seems to be a bug with various email clients (Thunderbird, TypeApp.) I know that Dovecot has the option to use the Submission service to copy emails to Sent without using SMTP to do this. Would this solve the problem we've seen over the years of emails not being copied to the Sent folder on various clients under certain (unknown) conditions? Thanks for your insight here. Asai
Re: how to setup dovecot to accept client certificates signed with a private CA when the server certificate is signed by a public CA
@m...@f1-outsourcing.eu No, the private CA certificate was not present there as I thought that its presence in the bundle pointed to by was enough. Anyway, placing it in /etc/ssl/certs and restarting dovecot does not change anything for the client, as expected. On Tue, Aug 9, 2022 at 10:09 AM jean-christophe manciot wrote: > > @m...@f1-outsourcing.eu > No, the private CA certificate was not present there as I thought that > its presence in the bundle pointed to by was enough. > Anyway, placing it in /etc/ssl/certs and restarting dovecot does not > change anything for the client, as expected. > > On Mon, Aug 8, 2022 at 9:28 PM Marc wrote: > > > > Have you added your root CA to where the rest of the ca certs are stored on > > your distribution? > > > > > > > > > > I forgot to say that this mail server has been working perfectly for > > > many years (but without client certificates). > > > > > > On Mon, Aug 8, 2022 at 6:42 PM jean-christophe manciot > > > wrote: > > > > > > > > @build+dove...@de-korte.org > > > > > > > > ssl_ca = > > > contains actually the private CA certificate bundled with the > > > > private CA CRL. > > > > > > > > ssl_cert = > > > contains the public server certificate bundled with Let's > > > > encrypt CA X3 cross-signed certificate. > > > > > > > > Maybe the latter should rather contain the root and intermediate > > > certificates. > > > > > > > > On Mon, Aug 8, 2022 at 11:45 AM Arjen de Korte > > > > wrote: > > > > > > > > > > Citeren jean-christophe manciot : > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > I'm trying to setup dovecot to accept only client certificates > > > created > > > > > > with a private CA: > > > > > > auth_ssl_require_client_cert = yes > > > > > > ssl_verify_client_cert = yes > > > > > > ssl_ca = > > > > > > > > > This is wrong, you should enter your private CA here. If > > > > > 'ssl_verify_client_cert' is not set to 'yes', this field should > > > > > generally be empty / not configured. > > > > > > > > > > > At the same time, dovecot is setup with an SSL certificate created > > > by > > > > > > a public CA (let's encrypt): > > > > > > ssl = required > > > > > > ssl_cert = > > > > > ssl_key = > > > > > > > > > > > When I try to connect to the server with a client (evolution), I > > > get a > > > > > > connection error: > > > > > > "Client did not present valid SSL certificate" except that it is > > > valid. > > > > > > > > > > > > As you probably already know, let's encrypt does not create client > > > > > > certificates. > > > > > > It seems that using a different CA for client certificates and for > > > the > > > > > > server certificate is unsupported. > > > > > > > > > > > > Am I missing something? > > > > -- > Jean-Christophe -- Jean-Christophe
