Re: [mailop] [EXTERNAL] OT re Munging was Re: Extortion spam from OVH-hosted *.sbs domains

Hello To neutralize URL, lots of cyber-security company use the X-ARF format : E.g. : hxxps://domain[.]tld It prevents miss click and accidental exposure of any kind of treat. -- Alexandre Dangréau Head of Trust & Safety CLO - VU.Ethics & Compliance Twitter | Link

[mailop] Meta outgoing servers in black list (SORBS, 0SPAM...)

Hi, I've got a customer complaining that they don't receive emails from Meta for password reset. We have tracked down this to see that a lot of this servers are blacklisted in popular blacklists. A small subset of blacklisted addresses are: 66.220.155.136 66.220.155.140 66.220.155.142 66.220.1

Re: [mailop] Meta outgoing servers in black list (SORBS, 0SPAM...)

On Thu, Feb 01, 2024 at 10:32:14AM +0100, Eduardo Díaz Comellas via mailop wrote: > > Btw, how do you deal with this big players' blacklist problems? One (possibly naive) option is to extract from SPF the outbound MXes for domains you want to receive mail from, such as what I describe in http

Re: [mailop] Meta outgoing servers in black list (SORBS, 0SPAM...)

On 2/1/24 10:32, Eduardo Díaz Comellas via mailop wrote: Hi, I've got a customer complaining that they don't receive emails from Meta for password reset. We have tracked down this to see that a lot of this servers are blacklisted in popular blacklists. Let's face it, if you are using 0sp

Re: [mailop] Meta outgoing servers in black list (SORBS, 0SPAM...)

On 2024-02-01 17:32:14 (+0800), Eduardo Díaz Comellas via mailop wrote: I've got a customer complaining that they don't receive emails from Meta for password reset. We have tracked down this to see that a lot of this servers are blacklisted in popular blacklists. [...] I usually don't care wh

Re: [mailop] Admin contact for Protonmail

Postmaster is extremely responsive, and if for some reason they don't reply - I know the team personally if you need a hand. Best, Faisal On Wed, Jan 31, 2024, at 3:32 PM, Atro Tossavainen via mailop wrote: > On Wed, Jan 31, 2024 at 02:03:33PM +, Tarun Singh via mailop wrote: >> Hello Folks

Re: [mailop] Meta outgoing servers in black list (SORBS, 0SPAM...)

It would be helpful if Meta used a better PTR naming convention for these servers.. ;) host 66.220.155.136 136.155.220.66.in-addr.arpa domain name pointer 66-220-155-136.mail-mail.facebook.com. Not sure who dreamed up that one.. On 2/1/24 02:18, Philip Paeps via mailop wrote: On 2024-02-01

[mailop] AOL/Yahoo: Confusing enhanced SMTP codes in response?

I see occasional bounces from AOL/Yahoo that look like this: 554 5.7.9 Message not accepted for policy reasons. See https://postmaster.yahooinc.com/error-codes However, the "554 5.7.9" doesn't make sense to me. The "554" part is "Transaction failed" (RFC 5321), which is fair enough (although u

Re: [mailop] AOL/Yahoo: Confusing enhanced SMTP codes in response?

On Thu, Feb 1, 2024 at 1:01 PM Robert L Mathews via mailop < mailop@mailop.org> wrote: > I see occasional bounces from AOL/Yahoo that look like this: > > 554 5.7.9 Message not accepted for policy reasons. See > https://postmaster.yahooinc.com/error-codes > > However, the "554 5.7.9" doesn't make s

Re: [mailop] AOL/Yahoo: Confusing enhanced SMTP codes in response?

On Thu, Feb 1, 2024 at 10:12 AM Todd Herr via mailop wrote: > > I've seen as yet unconfirmed speculation that this might be the error > response Yahoo is using for those that don't comply with the new (as of > today) requirements that mail be authenticated using SPF, DKIM, and DMARC. > > See also

Re: [mailop] Meta outgoing servers in black list (SORBS, 0SPAM...)

It appears that Renaud Allard via mailop said: >-=-=-=-=-=- >-=-=-=-=-=- > > > >On 2/1/24 10:32, Eduardo Díaz Comellas via mailop wrote: >> Hi, >> >> I've got a customer complaining that they don't receive emails from Meta >> for password reset. We have tracked down this to see that a lot of thi

Re: [mailop] [E] AOL/Yahoo: Confusing enhanced SMTP codes in response?

On Thu, Feb 1, 2024 at 10:03 AM Robert L Mathews via mailop < mailop@mailop.org> wrote: > I see occasional bounces from AOL/Yahoo that look like this: > > 554 5.7.9 Message not accepted for policy reasons. See > https://postmaster.yahooinc.com/error-codes Without knowing anything else, I'd click

[mailop] Support contact for Shaw.ca

Hi All: We are experiencing a problem with mail delivery to Shaw.ca. Since January 18th messages have been bounced with: 552 5.2.0 Message contains bare CR and is violating 822.bis section 2.3. We have tried to contact postmas...@shaw.ca but have not received any response yet. I was wondering if t

Re: [mailop] Support contact for Shaw.ca

Im replying on list for visibility. The issue you’re seeing is directly related to SMTP smuggling which was discussed on list ad nauseam about a month ago. The servers at shaw are configured to reject non-RFC bare linefeeds. Can you elaborate on why you’re sending them as they are not allowed.

[mailop] Ooops - sorry

Wound up way back in my archive and responded to an old, dead issue. -- -=[L]=- They Want to Kill Libraries - The Last Place in America Where You Are a Person, Not a Customer - Cory Doctorow Thoughts and Prayers are homeopathy for the mind ___ mailop

Re: [mailop] SPF behavior on email forwarding

On Fri, Apr 14, 2023 at 11:20:22AM -0400, John Levine via mailop wrote: > It appears that Jaroslaw Rafa via mailop said: > >Dnia 14.04.2023 o godz. 14:11:49 Slavko via mailop pisze: > >> In other words, SPF check is not something what helps with SPAM > >> here, seems that spammers adapted to it...