Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Matthew McGehrin
Hi Johannes, Gone are the days of being able to send normal emails to these providers. They use automated algorithms that block your email automatically. Your IP reputation has a lot to do with it as well, along with the IPs in your /24. For example, looking up your IP reputation, I see that

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Robert Schetterer
Am 17.03.19 um 08:44 schrieb Matthew McGehrin: Hi Johannes, Gone are the days of being able to send normal emails to these providers. They use automated algorithms that block your email automatically. Your IP reputation has a lot to do with it as well, along with the IPs in your /24. For exam

Re: Problems with rspamd, DKIM and a body getting altered after dkim signing because of changed content-transfer-encoding

2019-03-17 Thread Michael Ludwig
Hello again. Again my question: Is it possible to influence / to change the order? So that postfix first does, what it has to do and then passes the content to rspamd for dkim signing? This is the output of postconf -n: = alias_database = hash:/etc/alia

Re: DKIM setup writeup for multi domain?

2019-03-17 Thread lists
> I found my notes. This is for RHEL: thanks for all the replies, all very helpful, half way there V

intermittent sasl auth fails?

2019-03-17 Thread lists
I have a user with TBird saying they get ocassional error when trying to send with SASL AUTH, looking at log, I see this; Mar 17 22:10:44 postfix/smtpd[11975]: connect from 111-222-333-444.static.tpgi.com.au[111.222.333.444] Mar 17 22:10:45 postfix/smtpd[11975]: Anonymous TLS connection establishe

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Erwan David
Le 17/03/2019 à 08:44, Matthew McGehrin a écrit : > Hi Johannes, > > Gone are the days of being able to send normal emails to these > providers. They use automated algorithms that block your email > automatically. Your IP reputation has a lot to do with it as well, > along with the IPs in your /2

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Czarek
Check if you are not an open relay. Configure SPF, DKIM, DMARC and Reverse DNS. Than contact to the spam lists. Here you can check where your IP is listed. Rgds Wesley. On Sun, Mar 17, 2019 at 8:24 PM Erwan David wrote: > > Le 17/03/2019 à 08:44, Matthew McGehrin a écrit : > > Hi Johannes, > >

Re: Problems with rspamd, DKIM and a body getting altered after dkim signing because of changed content-transfer-encoding

2019-03-17 Thread Wietse Venema
Michael Ludwig: > Hello again. > Again my question: Is it possible to influence / to change the order? > So that postfix first does, what it has to do and then passes the > content to rspamd for dkim signing? Maybe you can be more specific about what you want to happen before Postfix hands off the

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Johannes Bauer
Hi Wesley, On 17.03.19 13:44, Czarek wrote: > Check if you are not an open relay. Configure SPF, DKIM, DMARC > and Reverse DNS. Except for DMARC I have all of the above. > Than contact to the spam lists. How so? Best regards, Johannes

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Francesc Peñalvez
u can check dnsbl list here https://hetrixtools.com/blacklist-check/ El 17/03/2019 a las 20:10, Johannes Bauer escribió: Hi Wesley, On 17.03.19 13:44, Czarek wrote: Check if you are not an open relay. Configure SPF, DKIM, DMARC and Reverse DNS. Except for DMARC I have all of the above. Th

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Erwan David
Le 17/03/2019 à 13:44, Czarek a écrit : > Check if you are not an open relay. Configure SPF, DKIM, DMARC > and Reverse DNS. > Than contact to the spam lists. > Here you can check where your IP is listed. > Rgds > Wesley. > In my case thaere is no spam list, I am not an open relay, I have DKIM, D

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Robert Schetterer
Am 17.03.19 um 20:59 schrieb Erwan David: Le 17/03/2019 à 13:44, Czarek a écrit : Check if you are not an open relay. Configure SPF, DKIM, DMARC and Reverse DNS. Than contact to the spam lists. Here you can check where your IP is listed. Rgds Wesley. In my case thaere is no spam list, I am n

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Michael
> I even registered to MS as a sender. They accept my > emails, but the recipient does not receive it or it is in the spam. Same for me, finally I gave it up and inform my hotmail recipients, good luck not that many, manually. >this helps only sometimes , having SPF, DKIM, DMARC >a

Re: intermittent sasl auth fails?

2019-03-17 Thread @lbutlr
On 17 Mar 2019, at 05:40, li...@sbt.net.au wrote: > (both domains are valid, tld.com as well as tld.com.au) both are valid in your lookup table? Have you checked this with postman? -- 'There has to be enough light,' he panted, 'to see the darkness.'

Re: intermittent sasl auth fails?

2019-03-17 Thread @lbutlr
On 17 Mar 2019, at 15:47, @lbutlr wrote: > On 17 Mar 2019, at 05:40, li...@sbt.net.au wrote: >> (both domains are valid, tld.com as well as tld.com.au) > > both are valid in your lookup table? Have you checked this with postman? postmaP (sorry, spelling correcting one wild) -- Stone circle

Re: Semi-OT: Getting blacklisted by hotmail/Google again and again

2019-03-17 Thread Peter
On 18/03/19 09:27, Michael wrote: this helps only sometimes , having SPF, DKIM, DMARC and Reverse DNS are is a must have these days I agree only partially, my experiences sorted by relevance: 1. Reverse DNS: no chance without 2. SPF: increases propability to get Mails delivered I up to no

Re: intermittent sasl auth fails?

2019-03-17 Thread Viktor Dukhovni
On Sun, Mar 17, 2019 at 10:40:23PM +1100, li...@sbt.net.au wrote: > Mar 17 22:10:53 postfix/smtpd[11975]: warning: > 111-222-333-444.static.tpgi.com.au[111.222.333.444]: SASL LOGIN > authentication failed: UGFzc3dvcmQ6 Try to avoid pasting SASL-generated base64-encoded strings from verbose lo