similar to: handling spam from gmail.

Your logics sucks. There is a difference between how email works and how spamassassin works. You are assuming that everyone in the world is using spamassassin by including it in 'how email works'. Maybe you like to post a link to your bayes files???? Am 11.06.20 um 11:13 schrieb Marc Roos: > You do not understand how mail works. Google mail is only getting > through when spf

>> Yes tell that to the people that create rhel6, rhel7 and rhel8 and give >> lts support. > >as said that has nothing to do with your wrong training and RHEL has >always the same problem: you can't package the latest and greatest shit >over 10 years because it requrires newer versions of dependencies > >so what you get with your lazyness by using a LTS

You do not understand how mail works. Google mail is only getting through when spf checks and the likes are being passed. I am not creating any problems with this, I am just bouncing them back. Google has enough billions to handle these issues. If everyone would apply this procedures, people with legitimate email accounts would move from a spam network to some other provider. People joining

I know it is not dovecot who should fix this. But anyone using dovecot is using an MTA, and receiving spam ;) I know how to look at email headers. Spf and dkim is not solving anything here. -----Original Message----- From: Sebastian Nielsen [mailto:sebastian at sebbe.eu] Sent: donderdag 11 juni 2020 10:23 To: Marc Roos; 'dovecot'; 'users' Subject: SV: handling spam from

I am sick of this gmail spam. Does anyone know a solution where I can do something like this: 1. received email from adcpni444 at gmail.com 2. system recognizes this email address has been 'whitelisted', continue with 7. 3. system recognizes as this email never been seen before 4. auto reply with something like (maybe with a wait time of x hours): Your message did not receive the

I get two or three of these a day. They are not from Gmail but have a "reply to" address that is a Gmail account. The messages cone from an email account that passes SPF and DKIM. So the sender and reply domains differ, but that isn't unique. I have email that I need that arrives like that. I am on the Postfix list where this does belong, but I looked at the problem and decided it

This is not a job for dovecot. You should look into whatever is your MTA (exim, postfix etc) and implement the solution there. But my initial suggestion is to check SPF and DKIM of the email. Because I know that gmail does terminate spammers quick, but if you don't validate SPF or DKIM, you might be a victim of spoofed Gmail email. Best regards, Sebastian Nielsen -----Ursprungligt

On 11/06/2020 16.26, Marc Roos wrote: > I know it is not dovecot who should fix this. But anyone using dovecot > is using an MTA, and receiving spam ;) I know how to look at email > headers. Spf and dkim is not solving anything here. You can configure this sort of thing in postfix, exim etc. The part of the mail system to do with RECEIVING emails. Not really a dovecot function. Look

On Thu, Jun 11, 2020 at 10:19:50AM +0200, Marc Roos wrote: > > > I am sick of this gmail spam. Does anyone know a solution where I can do > something like this: > > 1. received email from adcpni444 at gmail.com > 2. system recognizes this email address has been 'whitelisted', continue > with 7. > 3. system recognizes as this email never been seen before >

Marc Roos wrote: > > > I am sick of this gmail spam. Does anyone know a solution where I can do > something like this: > > 1. received email from adcpni444 at gmail.com > 2. system recognizes this email address has been 'whitelisted', continue > with 7. > 3. system recognizes as this email never been seen before > 4. auto reply with something like (maybe

On Thu, Jun 11, 2020 at 05:02:03PM +0800, Plutocrat wrote: > On 11/06/2020 16.26, Marc Roos wrote: > > I know it is not dovecot who should fix this. But anyone using dovecot > > is using an MTA, and receiving spam ;) I know how to look at email > > headers. Spf and dkim is not solving anything here. > > You can configure this sort of thing in postfix, exim etc. The

Wrong mailing list. You need to ask on the list for the MTA you are using (Sendmail, Postfix, &c). Actually, this sounds like a job for a custom milter, which would look at the domain name of the sending system, and reject the mail with your message. Dunno if there is one that works exactly like this. On 6/11/20 1:19 AM, Marc Roos wrote: > > > I am sick of this gmail spam.

* Marc Roos: > 3. system recognizes as this email never been seen before > 4. auto reply with something like (maybe with a wait time of x hours): > Your message did not receive the final recipient. You are sending > from a known spam provider Generating backscatter is definitely not a good move, and it is even prone to punish yourself. Better to reject the offending message

> with broken or vulnerable software is there really a benefit? LTS distributions back port necessary patches

:) I really starting to feel a bit like an idiot, but all these 3 configs[0] give error 'Client not compatible with this binary' [0] service health-check { executable = script /bin/health-check.sh inet_listener health-check { port = 5001 } } service health-check { executable = script -e "HOME PATH" /bin/health-check.sh inet_listener health-check { port =

It is a 'special use' folder, so it only appears to exist in mail clients. # spam folders merging mailbox Junk { special_use = \Junk auto = create } mailbox Spam { special_use = \Junk auto = no } mailbox "Junk E-mail" { special_use = \Junk auto = no } On 16/04/2020 23:19, Marc Roos wrote: > I do not have the log file anymore from the

I ended up 'hacking' LMTP support into the external spam filter. Someone else already contributed 'real' patches to implement LMTP support, so once I go live with this mail platform it should be stable. Met vriendelijke groeten, William Edwards T. 040 - 711 44 96 E. wedwards at cyberfusion.nl ? ----- Original Message ----- From: Marc Roos (M.Roos at f1-outsourcing.eu) Date:

Yes, I have still inbox mbox format because I have sendmail delivering there. I trying to migrate/convert step by step, with least possible impact for users. -----Original Message----- From: Aki Tuomi Sent: dinsdag 14 mei 2019 6:19 To: Marc Roos; Marc Roos via dovecot Subject: Re: Userdb userdb_mail=, error Mailbox list driver maildir++: maildir_name not supported by this driver > On

I can't yet use -p, the version I have is not supporting it still :( Maybe it is better to wait until alpine linux updates the package. -----Original Message----- Subject: RE: Health check curl example No worries. Now you are not using the passthrough(-p) mode. That is why dovecot is telling you that your client is not compatible. Using "script" without -p would require you

With this setting, all folders are empty, I guess understandable, because the mdbox has its own indexes stored locally with it. Does not explain though why inbox is empty. [@ dovecot]# cat special-userdb test:x:8267:231:Account with special settings for dovecot:/home/popusers/test:/bin/false:userdb_mail=mdbox:~/mdbox:INBOX=/ var/spool/mail/%u:INDEX=/var/dovecot/%u/index With this setting