Re: [mailop] The oligopoly has won.

> On 14 Sep 2022, at 22:29, Matthias Leisi wrote: > > >> What I’ve said elsewhere is that what consumers, enterprises, and SMBs all >> need is a healthy selection of services from which to choose. The problem >> with the entry costs is that you have to be able to leverage a cloud >>

Re: [mailop] The oligopoly has won.

I’m sure it’s been mentioned somewhere upthread, but to reiterate, the concentration levels in the email market have been measured.[1] The OP on Twitter and elsewhere isn’t wrong that it’s a PITA to set up and run an SMTP server, but to do it right for an SMB or even a large enterprise offers

Re: [mailop] Anyone from gmx.ch here?

To close the loop, yes the problem was mine, not cmx’s. They just spotted the problem. Eliot > On 3 Dec 2021, at 10:18, Tobias Herkula via mailop wrote: > > Answered off list > > / Tobias Herkula (Web.de|GMX|Mail.com) > > -Ursprüngliche Nachricht- > Von: mail

[mailop] Anyone from gmx.ch here?

Seeing please contact offline. Thanks, Eliot signature.asc Description: Message signed with OpenPGP ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop

Re: [mailop] Google DNS Quad 8 Outage tonight

Al, Can you point me at that tweet? Thanks, Eliot > On 20 Nov 2021, at 17:11, Al Iverson via mailop wrote: > > I never thought to monitor for it but Twitter suggests yes, there was an > outage, both on 11/19 and maybe back on 11/12 too. > > Cheers, > Al Iverson > > On Fri, Nov 19, 2021 at

Re: [mailop] .eml Attachments and the 1000-character SMTP Limit

> On 12 Oct 2021, at 07:19, John via mailop wrote: > > Hello Matt, > > The answer is yes, it's not good practice to block messages containing long > lines in emails. That will likely cause problems at either the sender or > recipient. Senders may receive non-delivery notifications,

Re: [mailop] HIPAA compliant email (was Re: So uh... Zoom/Sendgrid... How's that webinar spam investigation coming?)

> On 6 Aug 2021, at 00:20, Dave Warren via mailop wrote: > > Even more annoying is a secure request to "please send the requested private > medical data to some.doctor6...@gmail.com > ", which could be knowingly waiving the > encryption requirement if I

[mailop] How important is an ipv6 ptr record?

Do people care about them if there is an appropriate SPF record in place? Thanks, Eliot signature.asc Description: Message signed with OpenPGP ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop

Re: [mailop] [FOR THE RECORD] Overnite update to Cisco IronPort may be causing problems..

I’m told they’re on it. Eliot > On 19 Mar 2019, at 14:26, John Johnstone > wrote: > > On 3/18/2019 12:58 PM, Michael Peddemors wrote: >> Reported to our support teams, an over night filter rule update on Cisco >> IronPorts results in messages being modified incorrectly.. >> If anyone is

Re: [mailop] Dealing with a DKIM replay attack

On 8/14/16 6:46 AM, Steve Atkins wrote: > If there were a protocol that said "if you receive mail signed by this > domain / this key and the recipient isn't in the To: or Cc: field, > block it", or some similar protocol that signed the envelope > recipient, that would pretty much eliminate DKIM

Re: [mailop] Dealing with a DKIM replay attack and yahoo's use of DKIM domains for FBL reports

If I understand what's going on, Y! is doing an OR on DKIM & SPF and in this case, your SPF record is bypassed by the DKIM pass. The only thing to be done on your end is to not publish a DKIM record, and then you're at risk for a prefix hijack, though that is visible to some receivers, and it