Re: [mailop] No TLS reports from microsoft.com since March 29th

2023-04-19 Thread Gellner, Oliver via mailop 
On 18.04.2023 at 19:18 A. Schulze via mailop wrote:

Am 12.04.23 um 17:02 schrieb Paul Menzel via mailop:
>> Since March 29th, 2023 we have not received any (MTA-STS) TLS reports from 
>> microsoft.com.

> it seems it's not only TLS reporting: more then once over the last days we 
> received bounces for aggregated DMARC we sent to them.
> report -> itex-...@microsoft.com accepted and later bounced with "mailbox 
> full" :-/

itex-...@microsoft.com is hosted on O365, so they probably ran into their own 
100GB limit, because you know... 100GB ought to be enough for anybody. But the 
problem seems to be fixed by now as well.

As a sidenote, Microsoft apparently doesn't rely on its external sender 
identification feature, but rather appends the string "[EXTERNAL] " to the 
subject of every email.

--
BR Oliver


dmTECH GmbH
Am dm-Platz 1, 76227 Karlsruhe * Postfach 10 02 34, 76232 Karlsruhe
Telefon 0721 5592-2500 Telefax 0721 5592-2777
dmt...@dm.de * www.dmTECH.de
GmbH: Sitz Karlsruhe, Registergericht Mannheim, HRB 104927
Geschäftsführer: Christoph Werner, Martin Dallmeier, Roman Melcher

Datenschutzrechtliche Informationen
Wenn Sie mit uns in Kontakt treten, beispielsweise wenn Sie an unser 
ServiceCenter Fragen haben, bei uns einkaufen oder unser dialogicum in 
Karlsruhe besuchen, mit uns in einer geschäftlichen Verbindung stehen oder sich 
bei uns bewerben, verarbeiten wir personenbezogene Daten. Informationen unter 
anderem zu den konkreten Datenverarbeitungen, Löschfristen, Ihren Rechten sowie 
die Kontaktdaten unserer Datenschutzbeauftragten finden Sie 
hier.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] R: [E] Yahoo "Message not allowed" error

2023-04-19 Thread Rodolfo Saccani via mailop 
As far as I can see, envelope-from domains without a SOA record see their email 
rejected with 554 over some volume threshold.
This seems to be a fairly recent update. This requirement only recently 
appeared here: https://senders.yahooinc.com/smtp-error-codes/ (you can check 
the internet archive for the previous version which didn’t mention SOA).

Rodolfo Saccani
CTO @ Libraesva


Da: mailop  per conto di Jarland Donnell via mailop 

Data: mercoledì, 19 aprile 2023, 04:43
A: mailop@mailop.org 
Oggetto: Re: [mailop] [E] Yahoo "Message not allowed" error
That is actually the entirety of the SMTP response from
mx-eu.mail.am0.yahoodns.net at that time:

"554 Message not allowed - [299]"

Other error messages linked to
 
https://urlsand.esvalabs.com/?u=https%3A%2F%2Fpostmaster.yahooinc.com%2Ferror-codes=20266bc5=cb659c4b=y=y
  but not that one. Nothing
seems to help much on that page for this case unless I just assume the
message is "Those people can't email Yahoo anymore." I'm fairly
confused.

On 2023-04-18 16:25, Marcel Becker via mailop wrote:
> On Tue, Apr 18, 2023 at 12:16 PM Jarland Donnell via mailop
>  wrote:
>
>> id=<481770.862217189-sendEmail@srv4414> (554 Message not allowed -
>> [299])
>
> This is most likely not the full SMTP response we provide. The full
> one will tell you the reason -- including a link to a page explaining
> what to do and who to contact.
>
> -- Marcel
> ___
> mailop mailing list
> mailop@mailop.org
>  
> https://urlsand.esvalabs.com/?u=https%3A%2F%2Flist.mailop.org%2Flistinfo%2Fmailop=20266bc5=8e9e62e0=y=y
___
mailop mailing list
mailop@mailop.org
 
https://urlsand.esvalabs.com/?u=https%3A%2F%2Flist.mailop.org%2Flistinfo%2Fmailop=20266bc5=8e9e62e0=y=y

--
This message has been checked by Libraesva ESG and is found to be clean.
Follow this link to submit as spam/bad:
https://mail2.libraesva.com/action/4Q1Q8T2c0wzJmh9/submit-as-bad
Follow this link to blocklist sender:
https://mail2.libraesva.com/action/4Q1Q8T2c0wzJmh9/blocklist

--
This message was scanned by Libraesva ESG and is believed to be clean.

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop