Re: Catch a forged Return Path

On 6/02/21 2:23 am, Matus UHLAR - fantomas wrote: while I support using postscreen, I'm not sure it would be able to catch backscatter, becsuse backscatter often comes from servers who properly follow SMTP RFCs. The question here is whether this is really backscatter, or just spam taking adva

AW: Catch a forged Return Path

Hi, >On 6/02/21 2:23 am, Matus UHLAR - fantomas wrote: >> while I support using postscreen, I'm not sure it would be able to >> catch backscatter, becsuse backscatter often comes from servers who >> properly follow SMTP RFCs. >The question here is whether this is really backscatter, or just spa

Re: Catch a forged Return Path

On 06 Feb 2021, at 02:19, ludic...@gmail.com wrote: > but not sure how to implement that on a Plesk machine. Does Plesk not give you access to the main.cf file? How do you configure postfix at all? > To use the postscreen(8) service to block mail,

TLS is required, but was not offered

I am trying to setup my postfix (on CentOS 8) to work with Amazon SES as SMTP relay host. Amazon SES requires: relayhost = [email-smtp.eu-west-2.amazonaws.com]:587 smtp_sasl_auth_enable = yes smtp_sasl_security_options = noanonymous smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_u

Re: TLS is required, but was not offered

On Sat, Feb 06, 2021 at 12:05:44PM +0100, OzyMate wrote: > TLS is required, but was not offered by host 127.0.0.1 127.0.0.1 is not Amazon SES. So you are not showing stuff or running into the wrong direction. Please follow the instructions laid down in http://www.postfix.org/DEBUG_README.html#ma

AW: Catch a forged Return Path

Hi, >Does Plesk not give you access to the main.cf file? How do you configure >postfix at all? Plesk does rewrite the main.cf file (and possible others) upon changes in the GUI or updates. Not everything gets thrown out, but quite some lines revert to a Plesk default. It is not bad when it is

ipv6, SPF, DMARC

I discovered today that setting     inet_protocols = all leads gmail to receive mail by ipv6, claim SPF soft fail (presumably because my DNS only specifies ipv4) and so DMARC fail, which causes mail to be classed as spam. Setting     inet_protocols = ipv4 fixes the issue. I've never seen a DN

Re: ipv6, SPF, DMARC

* Jeff Abrahamson: > I've never seen a DNS query return an ipv6 address, so this behaviour > surprised me. In that case, welcome to 2021. ;-) Seriously, what "a DNS query" returns, depends on the query details. # Find MX-record for a subdomain ❯ dig +short MX ml.seichter.de. 10 wedjat.horu

Re: ipv6, SPF, DMARC

Dnia 6.02.2021 o godz. 18:27:01 Jeff Abrahamson pisze: > I've never seen a DNS query return an ipv6 address, so this behaviour > surprised me. Yes, it does return IPv6 for Google: raj@jarek-02:~$ host -t mx gmail.com gmail.com mail is handled by 10 alt1.gmail-smtp-in.l.google.com. gmail.com mail

Re: TLS is required, but was not offered

On 6 Feb 2021, at 6:05, OzyMate wrote: I am trying to setup my postfix (on CentOS 8) to work with Amazon SES as SMTP relay host. Amazon SES requires: relayhost = [email-smtp.eu-west-2.amazonaws.com]:587 smtp_sasl_auth_enable = yes smtp_sasl_security_options = noanonymous smtp_sasl_password_ma

Re: TLS is required, but was not offered

On Sat, Feb 06, 2021 at 12:05:44PM +0100, OzyMate wrote: > I am trying to setup my postfix (on CentOS 8) to work with Amazon SES as > SMTP relay host. Will this be a relay for *all* or just some outbound email? I'll assume *all* for now. > Amazon SES requires: > > relayhost = [email-smtp.eu-we