Brotman, Alex via mailop skrev den 2024-05-20 15:09:
Hey folks,
Over the next few weeks, we're going to be disabling TLSv1/v1.1 inbound
to our platform. Most senders are already using TLSv1.2/v1.3, so I
don't think this will be an issue. However, keep in mind that if
you're not already usin
On Mon, May 20, 2024 at 10:43 AM Mark E. Jeftovic via mailop <
mailop@mailop.org> wrote:
> Either hard bouncing:
>
> Those contain the reason, a link with more information as well as how and
where to get support.
> Or worse: accepting the email *and then not delivering it*.
>
No.
We started getting reports Friday of Rogers addresses (handled by Yahoo)
Either hard bouncing:
Remote-MTA: dns; mta6.am0.yahoodns.net
Diagnostic-Code: smtp; 554 Message not allowed - [PH01] Email not
accepted for
policy reasons
Or worse: accepting the email /and then not delivering it/.
Just to validate Simon's issue, we are working with a sender having the exact
same issue. What's more, the domain clearly is *not* "likely suspicious due
to the very low reputation of the sending domain", as the exact same sending
domain has zero issue sending to Gmail from Mailchimp and Netsu
Am 20.05.2024 um 13:09:25 Uhr schrieb Brotman, Alex via mailop:
> However, keep in mind that if you're not already using those newer
> versions, you'll now revert to clear-text.
This depends on the MTA's settings.
With sendmail I experienced that the default is to try STARTTLS many
times - even w
Hey folks,
Over the next few weeks, we're going to be disabling TLSv1/v1.1 inbound to our
platform. Most senders are already using TLSv1.2/v1.3, so I don't think this
will be an issue. However, keep in mind that if you're not already using those
newer versions, you'll now revert to clear-text
Hi,
Please share the Domain name and IP address that is having the issues so that
we can better assist. If possible, can you also share the email header of an
email that is failing.
As for the error, Gmail is clearly seeing an issue with the domain in the SPF
and DKIM records. It is very poss
