[mailop] mailop charter (Was: SMTP noise from *.bouncer.cloud)

2022-09-02 Thread Thomas Walter via mailop
Hello Christopher, On 03.09.22 00:13, Christopher Hawker via mailop wrote: Seems like a whole lot of bitching and whinging is going on here regarding bouncer.cloud. Pretty sure this is a mail operations list, not a “let’s whinge and complain about mail services” list On https://www.mailop.or

Re: [mailop] smtp dane/tlsa

2022-09-02 Thread John Levine via mailop
It appears that Carl Byington via mailop said: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >On Fri, 2022-09-02 at 18:42 +, ml+mailop--- via mailop wrote: >> Are you sure you want 3 0 1 and not 3 1 1? > >Yes. We are publishing the hash of the full certificate. Note there are >two tlsa r

Re: [mailop] SMTP noise from *.bouncer.cloud

2022-09-02 Thread Jarland Donnell via mailop
I've seen precisely one thing on this list, on this topic, that I would classify as "bitching" and I'm replying to it. On 2022-09-02 17:13, Christopher Hawker via mailop wrote: Seems like a whole lot of bitching and whinging is going on here regarding bouncer.cloud. Pretty sure this is a mail o

Re: [mailop] SMTP noise from *.bouncer.cloud

2022-09-02 Thread Christopher Hawker via mailop
Seems like a whole lot of bitching and whinging is going on here regarding bouncer.cloud. Pretty sure this is a mail operations list, not a “let’s whinge and complain about mail services” list. It’s very simple - if you don’t like or want traffic from their systems entering your network or serv

Re: [mailop] smtp dane/tlsa

2022-09-02 Thread Carl Byington via mailop
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2022-09-02 at 18:42 +, ml+mailop--- via mailop wrote: > Are you sure you want 3 0 1 and not 3 1 1? Yes. We are publishing the hash of the full certificate. Note there are two tlsa records, one corresponding to the previous LE certificate

Re: [mailop] SMTP noise from *.bouncer.cloud

2022-09-02 Thread Bill Cole via mailop
On 2022-09-02 at 14:16:25 UTC-0400 (Fri, 2 Sep 2022 18:16:25 +) Larry M. Smith via mailop is rumored to have said: On 8/31/2022, Bill Cole via mailop wrote: (snip) Who/what/where their clients are, and for what purpose of course, is not likely something we will find out unless they like to

[mailop] SMTP noise from *.bouncer.cloud

2022-09-02 Thread Radek Kaczynski via mailop
Hello Gentlemen, First of all, Andreas - I'm sorry that traffic from our solution has confused you. We are indeed providing email verification services ( https://www.usebouncer.com ( https://www.usebouncer.com/ ) ). I do understand and fully respect your opinion about that kind of service. An

Re: [mailop] smtp dane/tlsa

2022-09-02 Thread ml+mailop--- via mailop
> _25._tcp.mail3.five-ten-sg.com. IN TLSA 3 0 1 ( > 834d710b2feb790cc9b2c6d251c65b1fedc24c51a4149bdfeae4d40e0be11892 Are you sure you want 3 0 1 and not 3 1 1? Isn't the second number the selector: 0 -- Full certificate: the Certificate binary structure as defined in [RFC5280] 1 -- SubjectPubli

Re: [mailop] SMTP noise from *.bouncer.cloud

2022-09-02 Thread Larry M. Smith via mailop
On 8/31/2022, Bill Cole via mailop wrote: (snip) Who/what/where their clients are, and for what purpose of course, is not likely something we will find out unless they like to share more, but we can continue discussing this in terms of all the operators out there, and what constitutes the good

[mailop] smtp dane/tlsa

2022-09-02 Thread Carl Byington via mailop
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Years ago I setup automation for tlsa records to support smtp dane here. However, something is now broken, and I am not sure what is wrong. _25._tcp.mail3.five-ten-sg.com. IN TLSA 3 0 1 ( 834d710b2feb790cc9b2c6d251c65b1fedc24c51a4149bdfeae4d40e0be