Re: [mailop] CVE-2019-10149 Exim 4.87 - 4.91 possible remote exploit

2019-06-05 Thread Stuart Henderson via mailop
On 2019/06/05 17:20, Heiko Schlittermann via mailop wrote: > The fix for CVE-2019-10149 is public now. > > https://git.exim.org/exim.git > Branch exim-4_91+fixes. > > Thank you to > - Qualys for reporting it. > - Jeremy for fixing it. > - you for using Exim. > > Sorry for con

Re: [mailop] Microsoft blacklisting a /16

2019-06-05 Thread John Levine via mailop
In article <139ccd39-d392-7000-25d0-5428e7a57...@hetzner.com> you write: >that send spam to Microsoft. Now, all of a sudden and without warning, >Microsoft has blacklisted the entire range 5.9.0.0/16. If the mail that range is sending Microsoft is anything like the mail it's sending my much smalle

Re: [mailop] Microsoft blacklisting a /16

2019-06-05 Thread Michael Peddemors via mailop
Point taken.. however, in his case, this is more about network operators, than email operators, which is probably why he suggested to keep it off list. However, the point has been raised in the past, whether this list should expand on it's allowable range of discussions. That hasn't been det

Re: [mailop] Microsoft blacklisting a /16

2019-06-05 Thread Stefan Bauer via mailop
Please keep this on-list. This is of great help for all other mailops to improve own setup. Thank you. -Ursprüngliche Nachricht- Von: Hetzner Blacklist via mailop  Gesendet: Mittwoch 5 Juni 2019 17:43 An: mailop@mailop.org; Michael Peddemors Betreff: Re: [mailop] Microsoft blacklistin

Re: [mailop] Microsoft blacklisting a /16

2019-06-05 Thread Hetzner Blacklist via mailop
Hi Michael, thanks for your post. Even if it doesn't really help with the issue we're having, you make some great points (as usual). I thought I'd respond to a few, in the hope this doesn't derail the reason for my initial post. > Hehehe.. how does that saying going about the "pot calling the ket

Re: [mailop] Microsoft blacklisting a /16

2019-06-05 Thread Michael Rathbun via mailop
On Wed, 5 Jun 2019 13:25:40 +0200, Hetzner Blacklist via mailop wrote: >For the past two years things have been going really well for us in >regards to the Microsoft blacklist. We've had very few issues, probably >because we aggressively check the SNDS and block/terminate IPs/clients >that send s

Re: [mailop] CVE-2019-10149 Exim 4.87 - 4.91 possible remote exploit

2019-06-05 Thread Heiko Schlittermann via mailop
The fix for CVE-2019-10149 is public now. https://git.exim.org/exim.git Branch exim-4_91+fixes. Thank you to - Qualys for reporting it. - Jeremy for fixing it. - you for using Exim. Sorry for confusion about the public release. We were forced to react, as details leaked. The

Re: [mailop] Forwarded messages stopped by Gmail as spam

2019-06-05 Thread Brandon Long via mailop
If you can share the email that's rejected with me (zip file or as text attachment), I can take a look. Brandon On Tue, Jun 4, 2019, 2:54 AM Guarascio Francesco < francesco.guaras...@italiaonline.it> wrote: > Hi Brandon, > > thank you very much for your answer. > > It was really helpful because

Re: [mailop] Microsoft blacklisting a /16

2019-06-05 Thread Michael Peddemors via mailop
Hehehe.. how does that saying going about the "pot calling the kettle black"? But aside from comments about what people are saying about Azure It really is when those /28's start firing up on your network.. I would 'like' to say it is a problem with vetting new customers, however I can't

Re: [mailop] Exim 4.87 - 4.91 possible remote exploit

2019-06-05 Thread Heiko Schlittermann via mailop
We will publish the fix today 2019-06-05 15:15 UTC on the exim-4_91+fixes branch of our public Git repo git.exim.org. Distros can release their packages by that date. Sorry for the inconveniences. -- Heiko Schlittermann (unterwegs) signature.asc Description: PGP signature _

[mailop] Microsoft blacklisting a /16

2019-06-05 Thread Hetzner Blacklist via mailop
Hello Mailop, For the past two years things have been going really well for us in regards to the Microsoft blacklist. We've had very few issues, probably because we aggressively check the SNDS and block/terminate IPs/clients that send spam to Microsoft. Now, all of a sudden and without warning, Mi