[mailop] Microsoft BackScatter problem? Michael W, can you investigate?

2023-08-09 Thread Michael Peddemors via mailop
Having a few customers reporting a REAL strange case.. they are being 
overwhelmed by what looks like backscatter, but a very broken backscatter.


All IPs in the 40.92.NNN.NNN block.

The backscatter message coming from postmas...@outlook.com as NDR"s but 
not a normal NDR.  Being delivered to servers to domains with no A or MX 
records..


And we are seeing these IPs now appearing on backscatter.org as well.
NOTE: There is NO body in the message, indicating a reason for the NDR..

.

Headers below if it helps you..

Received: from mail-mw2nam10olkn2084.outbound.protection.outlook.com 
([40.92.42.84]:38112 helo=NAM10-MW2-obe.outbound.protection.outlook.com)
	by  with esmtps  (TLS1.2) tls 
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

(Exim 4.96)
id 1qTpwd-004JSX-0J
for Jahnya@;
Wed, 09 Aug 2023 23:38:15 +0300
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;

b=XhJ+kYhzxcA3XGZUqeNDfFGChhg6RRkeyxghrj5N2hKNVspJZp/781RbYyYOrp8SdNVnJE8xcAtT7GMMftQMpuzw71YpcfxWAiZm/ED9JLAGctYa4pL5QXHfbnKdlZPYFWWvWKKfBeEJblJkRO0pr1sicHomGiu9cEWfWjAXBtFeL+j9xtEmMPNWkTQNdK2ZhurpDT5FkVjf5EmIvpggWYx5EzWxeu8QQmi4hPcjnFoZX7+9VqpAQuNo0vWFmLGG+LG0GNwVc6K72FyV1RWanqM9Wrmn6jJx39Zw3ys9+Zix2k4za1VuXCQCtQ3BiK4hfheAPadTjrz1vz3ftybqdQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; 
d=microsoft.com;

 s=arcselector9901;

h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
 bh=/8Hlqr2Bkfq6i0TwJEPEzEnh2O5u2q/yfM7OsqSCGCQ=;

b=F9MM5U4+LLFaeZCE2N2k9Nf8u6Is8AMIG+M0km0xwWT8dO/Br1UtJtWDK9leiFKt4zTJwY0BgIrmWPbFLi5DJTn+6E/ujI4O6zQW7MSQOoVXHymPLO2gLjxWYAT4IGN8l9nXFPrJRJfz3UVYSA9x30mGIYZ511x6tKTQ22VMXsmV6BS8R0EJlVSuRVdlXLwNdFK9o7fUphomh++Sfz5u0QQOlHWQEBlVcYSnPXhLbtCgiC1Bwq/+QhHDNAB3gllgoI2+F33QkjdUbdPS+yA6IRJHLj2MUl6Gwp8qeEuY8EMHzaaB1DJYf5boQoDd78OfFdGby0gDw0qlnodEv9neVQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none;
 dkim=none; arc=none
MIME-Version: 1.0
From: 
To: 
Date: Wed, 9 Aug 2023 18:34:51 +
Content-Type: multipart/report; report-type=delivery-status;
boundary="cd27c922-00cc-442b-a258-661846c23260"
X-MS-Exchange-Message-Is-Ndr:
Content-Language: en-US
Message-ID:


In-Reply-To:


References:


Subject: Undeliverable: COUNTDOWN: Final Hours for Vital Upgrade and
 Monumental Electricity Savings!   geIBq
Auto-Submitted: auto-replied
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: MW4PR03MB6394:EE_
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:

qoiU3K41Ci+5WTB5cAYw7UBzXMmO04KwHRaCMwqBl7e9Sz7+iyonvAZPRoYDxbKPQ5XFhXI4ldG2jJt/NtjWberFBcH/Httg5cspC9M6GYyQLvQku4Qonj7ej+gVeLFl+LMw5n3Smqfqg8Pzmk/Akj3quj9SPiRsCbMZcP3p/Ybuoqjid5ZA/O3fgI48jxFzghlZR9SDrJRKn+gLmya2hIy3eS+9ArGfYVb7Nt86iYbikDjUqlGo/pheebwIWsIlnpRC9QcK3c0WJizEZUsirtPqzlegaBqz7ZhsPrLVmAxdqJd/Ag5jFhc7nbxr0PNuzoNJdvTcsdw+++B/7D19HxF+b/SdiTtIFg+9qmg+r+eL3mOflAnh9o3vHsijygejNVaA/qRIv2nCtPakOpx0mC0ooEKrvsyC1/GTXdQ7IQzg1BLf7hR/nH6f2rhhu5dnEEyNUr4ewPda02NYfmngtqDPQ7vG1QBQCmusXP4WHyz2f+AV3pwV0JWdrRezQK7e8HjCXfy81Ulbhl3I9+lC8PlxuqV3nCQQopHKlCbvF/cui9rOG02pzpyOz/+O74Kp/O8d8MXwj7KMOD8oMpdgKrWfDAiNHdmz+nOGGajkhCimq8BSAua7eueg8Qxk7ue8R9ds113RPqvCGKYzly9L0H1f54UrW30Tk4CkyQKf47s+7RJVrbFFB7Jv2WrKwxnY3RPlkfcQOdXGCs5u8SuQwPhkB18hHDlYd9pm4subA4/R1i21e0Wqx4pQdY8sGa/w
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0:

PYwOPBlt5Z1lxNc2cOsbgPB02t5rBb/VkDolnGBkVASJUUkke/pHd9cxJqs67Fl4vwHJI5BzzsO5s+PccTsWiivERCz/1+9gEvzOQXMdY3SyLSh+D9HTB+iKl+6XpYpKzCWS2ktiHbC2e3eGYpqF48XtTFE1Xcq1mjkUi+2DA138jVUAOE6075AEICO/coue
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Aug 2023 18:34:51.8668
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-AuthSource: 
MW4PR03MB6394.namprd03.prod.outlook.com

X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-Network-Message-Id:
478f709d-648c-44e3-de5d-08db990751c3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW4PR03MB6394


--
"Catch the Magic of Linux..."

Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] [E] Help With a Sudden AOL/Yahoo Issue

2023-08-09 Thread Lili Crowley via mailop
We are having an outage actually. Please stay tuned. I can let everyone
know here when it has passed.

Thanks!

*Lili Crowley*

she/her

Postmaster








On Wed, Aug 9, 2023 at 4:54 PM Michael E. Weisel via mailop <
mailop@mailop.org> wrote:

> Hi Mailop community.  We have experienced a sudden Yahoo/AOL/Verizon block
> for one of our clients that we are trying to figure out.  We saw no
> indication of any issues until we started seeing TSS04 messages in the logs
> around 3:00pm today.  It would be greatly appreciated if someone on the
> list from the AOL/Yahoo/Verizon team could please reach out to me.
>
>
>
>
>
> Thanks,
>
>
>
> Michael
>
>
>
> Michael E. Weisel
>
> CTO / Deliverability Lead
>
> Gold Lasso
>
> (301) 990-9857 Corporate
>
> (240) 813-0174 Direct Dial
>
>
> ___
> mailop mailing list
> mailop@mailop.org
>
> https://urldefense.com/v3/__https://list.mailop.org/listinfo/mailop__;!!Op6eflyXZCqGR5I!CeB23jpM0FEkjNENNj2FtTPZMSu2dxLcaQYDoPVzJK2r-82fWTSYwdtbrZxRixPwxt8QNLiAmHbEXI38b98$
>
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] [E] Re: Help With a Sudden AOL/Yahoo Issue

2023-08-09 Thread Lili Crowley via mailop
Thanks Alex! We are and are recovering now. You should start seeing
improvements soon.


*Lili Crowley*

she/her

Postmaster








On Wed, Aug 9, 2023 at 5:02 PM Alex Burch via mailop 
wrote:

> Yes I think this is widespread. I am 90% sure Yahoo is looking into it
> right now
>
> Thanks,
> Alex
>
>
> --
>
> Alexander Burch
> ActiveCampaign / Senior Deliverability Engineer
> abu...@activecampaign.com
> 1 North Dearborn St Suite 500, Chicago IL, 60602
>
> 
>
> 
>
> 
>
> 
>
>
> 
>
>
> On Wed, Aug 9, 2023 at 1:53 PM Michael E. Weisel via mailop <
> mailop@mailop.org> wrote:
>
>> Hi Mailop community.  We have experienced a sudden Yahoo/AOL/Verizon
>> block for one of our clients that we are trying to figure out.  We saw no
>> indication of any issues until we started seeing TSS04 messages in the logs
>> around 3:00pm today.  It would be greatly appreciated if someone on the
>> list from the AOL/Yahoo/Verizon team could please reach out to me.
>>
>>
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Michael
>>
>>
>>
>> Michael E. Weisel
>>
>> CTO / Deliverability Lead
>>
>> Gold Lasso
>>
>> (301) 990-9857 Corporate
>>
>> (240) 813-0174 Direct Dial
>>
>>
>> ___
>> mailop mailing list
>> mailop@mailop.org
>>
>> https://urldefense.com/v3/__https://list.mailop.org/listinfo/mailop__;!!JIZ-LZtDGnv5HBqN_A!JVXDOEALHhOUVaL-yoRNYvDIIiuZ7sh9uF1FrSCdqtetQVoUam2HFY_MmgguigQcL0Gq2kvRE6tokrLOQM0$
>>
> ___
> mailop mailing list
> mailop@mailop.org
>
> https://urldefense.com/v3/__https://list.mailop.org/listinfo/mailop__;!!Op6eflyXZCqGR5I!Fkb2Q_8JnZ1fUEh7NDCKK8lIY2NzsIQWZJ-V2YSkCnT-YLETe00an0Blfik9je2Mg4D2VhksX1-urZUFEYc$
>
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Help With a Sudden AOL/Yahoo Issue

2023-08-09 Thread Eric Tykwinski via mailop
My spool is already starting to slowly go down, so I think it was probably just 
a temporary blip.

Sincerely,

Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300

> On Aug 9, 2023, at 4:58 PM, Alex Burch via mailop  wrote:
> 
> Yes I think this is widespread. I am 90% sure Yahoo is looking into it right 
> now
> 
> Thanks,
> Alex
> 
> 
> --
> 
>   
> Alexander Burch
> ActiveCampaign / Senior Deliverability Engineer
> abu...@activecampaign.com 
> 1 North Dearborn St Suite 500, Chicago IL, 60602
>    
>   
>   
> 
>  
> 
> 
> On Wed, Aug 9, 2023 at 1:53 PM Michael E. Weisel via mailop 
> mailto:mailop@mailop.org>> wrote:
> Hi Mailop community.  We have experienced a sudden Yahoo/AOL/Verizon block 
> for one of our clients that we are trying to figure out.  We saw no 
> indication of any issues until we started seeing TSS04 messages in the logs 
> around 3:00pm today.  It would be greatly appreciated if someone on the list 
> from the AOL/Yahoo/Verizon team could please reach out to me.
> 
>  
> 
>  
> 
> Thanks,
> 
>  
> 
> Michael
> 
>  
> 
> Michael E. Weisel
> 
> CTO / Deliverability Lead
> 
> Gold Lasso
> 
> (301) 990-9857 Corporate
> 
> (240) 813-0174 Direct Dial
> 
>  
> 
> ___
> mailop mailing list
> mailop@mailop.org 
> https://urldefense.com/v3/__https://list.mailop.org/listinfo/mailop__;!!JIZ-LZtDGnv5HBqN_A!JVXDOEALHhOUVaL-yoRNYvDIIiuZ7sh9uF1FrSCdqtetQVoUam2HFY_MmgguigQcL0Gq2kvRE6tokrLOQM0$
>  
> 
>  
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop

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


Re: [mailop] Help With a Sudden AOL/Yahoo Issue

2023-08-09 Thread Mike Hillyer via mailop
This is an issue on Yahoo’s end and they are working on it currently. Many 
people in the deliverability community are reporting the same thing.

From: mailop  On Behalf Of Michael E. Weisel via 
mailop
Sent: Wednesday, August 9, 2023 4:16 PM
To: mailop@mailop.org
Subject: [mailop] Help With a Sudden AOL/Yahoo Issue

Hi Mailop community.  We have experienced a sudden Yahoo/AOL/Verizon block for 
one of our clients that we are trying to figure out.  We saw no indication of 
any issues until we started seeing TSS04 messages in the logs around 3:00pm 
today.  It would be greatly appreciated if someone on the list from the 
AOL/Yahoo/Verizon team could please reach out to me.


Thanks,

Michael

Michael E. Weisel
CTO / Deliverability Lead
Gold Lasso
(301) 990-9857 Corporate
(240) 813-0174 Direct Dial

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


Re: [mailop] Help With a Sudden AOL/Yahoo Issue

2023-08-09 Thread Alex Burch via mailop
Yes I think this is widespread. I am 90% sure Yahoo is looking into it
right now

Thanks,
Alex


--

Alexander Burch
ActiveCampaign / Senior Deliverability Engineer
abu...@activecampaign.com
1 North Dearborn St Suite 500, Chicago IL, 60602








On Wed, Aug 9, 2023 at 1:53 PM Michael E. Weisel via mailop <
mailop@mailop.org> wrote:

> Hi Mailop community.  We have experienced a sudden Yahoo/AOL/Verizon block
> for one of our clients that we are trying to figure out.  We saw no
> indication of any issues until we started seeing TSS04 messages in the logs
> around 3:00pm today.  It would be greatly appreciated if someone on the
> list from the AOL/Yahoo/Verizon team could please reach out to me.
>
>
>
>
>
> Thanks,
>
>
>
> Michael
>
>
>
> Michael E. Weisel
>
> CTO / Deliverability Lead
>
> Gold Lasso
>
> (301) 990-9857 Corporate
>
> (240) 813-0174 Direct Dial
>
>
> ___
> mailop mailing list
> mailop@mailop.org
>
> https://urldefense.com/v3/__https://list.mailop.org/listinfo/mailop__;!!JIZ-LZtDGnv5HBqN_A!JVXDOEALHhOUVaL-yoRNYvDIIiuZ7sh9uF1FrSCdqtetQVoUam2HFY_MmgguigQcL0Gq2kvRE6tokrLOQM0$
>
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] Help With a Sudden AOL/Yahoo Issue

2023-08-09 Thread Michael E. Weisel via mailop
Hi Mailop community.  We have experienced a sudden Yahoo/AOL/Verizon block for 
one of our clients that we are trying to figure out.  We saw no indication of 
any issues until we started seeing TSS04 messages in the logs around 3:00pm 
today.  It would be greatly appreciated if someone on the list from the 
AOL/Yahoo/Verizon team could please reach out to me.


Thanks,

Michael

Michael E. Weisel
CTO / Deliverability Lead
Gold Lasso
(301) 990-9857 Corporate
(240) 813-0174 Direct Dial

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


Re: [mailop] Any insight on whether to treat the Microsoft Consumer/Business MXes separately?

2023-08-09 Thread Mike Hillyer via mailop
Thanks Tara, that lines up with my expectation.

Mike

-Original Message-
From: Tara Natanson  
Sent: Wednesday, August 9, 2023 1:32 PM
To: Mike Hillyer 
Cc: mailop 
Subject: Re: [mailop] Any insight on whether to treat the Microsoft 
Consumer/Business MXes separately?

One of those  MXs is for Hotmail.com, outlook.com, msn.com and the other is for 
all domains hosted on Office365.  For reporting purposes we keep these very 
separate in our system as they have a tendency to treat the messages 
differently.  I would strongly recommend you keep them separate, especially if 
you were going to put rules in on a per
MX basis.   The filtering and the bounce responses from them can be
very different.

Tara Natanson
(Constant Contact

On Wed, Aug 9, 2023 at 1:14 PM Mike Hillyer via mailop  
wrote:
>
> Hi All,
>
>
>
> I think I mentioned on here before that we are building an Open Source MTA 
> for senders (https://github.com/KumoCorp/kumomta).
>
>
>
> One of our features is that we throttle by MX group instead of the 
> destination domain, so that when someone sends to an o365 domain as an 
> example the mail is queued and throttled together with all the other mail 
> destined for o365. Keeps the server from consuming more ISP resources than 
> necessary like when a server queues and throttles by destination domain.
>
>
>
> We have a user who has noted that the two subdomains 
> *.olc.protection.outlook.com and *.mail.protection.outlook.com are grouping 
> separately and asked about them being merged so they could maintain only one 
> set of throttle configs.
>
>
>
> Before acting on that request I wanted to see if I could get context to make 
> sure we do the right thing.
>
>
>
> Does anyone have any context on whether those two subdomains end up at the 
> same set of servers? If not, I’d rather keep our current behavior and treat 
> them separately from a queueing and throttling perspective.
>
>
>
> Bonus points: if they are separate server banks, has anyone ever seen a need 
> to set different traffic shaping rules for them? I may enable combined 
> throttle config, with separate queueing and throttle tracking.
>
>
>
> Thanks,
>
> Mike
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Any insight on whether to treat the Microsoft Consumer/Business MXes separately?

2023-08-09 Thread Mike Hillyer via mailop
Yes, and it is, but I want to ensure that the default behavior is well behaved 
as the ISPs want.

-Original Message-
From: mailop  On Behalf Of Jaroslaw Rafa via mailop
Sent: Wednesday, August 9, 2023 2:19 PM
To: mailop@mailop.org
Subject: Re: [mailop] Any insight on whether to treat the Microsoft 
Consumer/Business MXes separately?

Dnia  9.08.2023 o godz. 17:13:01 Mike Hillyer via mailop pisze:
> 
> We have a user who has noted that the two subdomains 
> *.olc.protection.outlook.com and *.mail.protection.outlook.com are 
> grouping separately and asked about them being merged so they could 
> maintain only one set of throttle configs.
> 
> Before acting on that request I wanted to see if I could get context 
> to make sure we do the right thing.

I thinks such things could be configurable anyway? Ie. if the user wants to 
treat them separately, or to merge them, the MTA can be configured to do either 
one.
--
Regards,
   Jaroslaw Rafa
   r...@rafa.eu.org
--
"In a million years, when kids go to school, they're gonna know: once there was 
a Hushpuppy, and she lived with her daddy in the Bathtub."
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Any insight on whether to treat the Microsoft Consumer/Business MXes separately?

2023-08-09 Thread Jaroslaw Rafa via mailop
Dnia  9.08.2023 o godz. 17:13:01 Mike Hillyer via mailop pisze:
> 
> We have a user who has noted that the two subdomains
> *.olc.protection.outlook.com and *.mail.protection.outlook.com are
> grouping separately and asked about them being merged so they could
> maintain only one set of throttle configs.
> 
> Before acting on that request I wanted to see if I could get context to
> make sure we do the right thing.

I thinks such things could be configurable anyway? Ie. if the user wants to
treat them separately, or to merge them, the MTA can be configured to do
either one.
-- 
Regards,
   Jaroslaw Rafa
   r...@rafa.eu.org
--
"In a million years, when kids go to school, they're gonna know: once there
was a Hushpuppy, and she lived with her daddy in the Bathtub."
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Send emails over O365 to Google with a specific domain are rejected

2023-08-09 Thread John Levine via mailop
It appears that Otto J. Makela via mailop  said:
>I concur, Google seems to think that if you are using IPv6 for transport
>you must be Teh Master of Teh Internet™, and it'll be trivial for you
>to get every single detail right in your messages.

They've said for a long time that all mail to them over IPv6 has to be
authenticated. This should not be news to anyone.  If you can't do that,
use IPv4 until you can.

What has changed lately is that they have also gotten pickier about
unautnenticated IPv4 mail.

I do wish they'd figure out how to get rid of the plague of chatty B2B spammers
using throwaway gmail accounts.

R's,
John
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Any insight on whether to treat the Microsoft Consumer/Business MXes separately?

2023-08-09 Thread Tara Natanson via mailop
One of those  MXs is for Hotmail.com, outlook.com, msn.com and the
other is for all domains hosted on Office365.  For reporting purposes
we keep these very separate in our system as they have a tendency to
treat the messages differently.  I would strongly recommend you keep
them separate, especially if you were going to put rules in on a per
MX basis.   The filtering and the bounce responses from them can be
very different.

Tara Natanson
(Constant Contact

On Wed, Aug 9, 2023 at 1:14 PM Mike Hillyer via mailop
 wrote:
>
> Hi All,
>
>
>
> I think I mentioned on here before that we are building an Open Source MTA 
> for senders (https://github.com/KumoCorp/kumomta).
>
>
>
> One of our features is that we throttle by MX group instead of the 
> destination domain, so that when someone sends to an o365 domain as an 
> example the mail is queued and throttled together with all the other mail 
> destined for o365. Keeps the server from consuming more ISP resources than 
> necessary like when a server queues and throttles by destination domain.
>
>
>
> We have a user who has noted that the two subdomains 
> *.olc.protection.outlook.com and *.mail.protection.outlook.com are grouping 
> separately and asked about them being merged so they could maintain only one 
> set of throttle configs.
>
>
>
> Before acting on that request I wanted to see if I could get context to make 
> sure we do the right thing.
>
>
>
> Does anyone have any context on whether those two subdomains end up at the 
> same set of servers? If not, I’d rather keep our current behavior and treat 
> them separately from a queueing and throttling perspective.
>
>
>
> Bonus points: if they are separate server banks, has anyone ever seen a need 
> to set different traffic shaping rules for them? I may enable combined 
> throttle config, with separate queueing and throttle tracking.
>
>
>
> Thanks,
>
> Mike
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] Any insight on whether to treat the Microsoft Consumer/Business MXes separately?

2023-08-09 Thread Mike Hillyer via mailop
Hi All,

I think I mentioned on here before that we are building an Open Source MTA for 
senders (https://github.com/KumoCorp/kumomta).

One of our features is that we throttle by MX group instead of the destination 
domain, so that when someone sends to an o365 domain as an example the mail is 
queued and throttled together with all the other mail destined for o365. Keeps 
the server from consuming more ISP resources than necessary like when a server 
queues and throttles by destination domain.

We have a user who has noted that the two subdomains 
*.olc.protection.outlook.com and *.mail.protection.outlook.com are grouping 
separately and asked about them being merged so they could maintain only one 
set of throttle configs.

Before acting on that request I wanted to see if I could get context to make 
sure we do the right thing.

Does anyone have any context on whether those two subdomains end up at the same 
set of servers? If not, I'd rather keep our current behavior and treat them 
separately from a queueing and throttling perspective.

Bonus points: if they are separate server banks, has anyone ever seen a need to 
set different traffic shaping rules for them? I may enable combined throttle 
config, with separate queueing and throttle tracking.

Thanks,
Mike
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] ANY OVH Contact?

2023-08-09 Thread Michael Peddemors via mailop

On 2023-08-09 08:55, Mark Alley via mailop wrote:


On 8/9/2023 3:31 AM, Jaroslaw Rafa via mailop wrote:

Dnia  9.08.2023 o godz. 11:00:12 Otto J. Makela via mailop pisze:

Unless the situation has dramatically changed in the last year,
OVH has no functioning abuse team. I block a majority of their nets
from sending email, don't seem to getting any false positives.

Luckily you don't block the net where my server is located, otherwise you
would get a false positive, if I would send mail to you...


Even by merely glancing at one of those subnets 15.204.0.0/17, I see a 
relatively sizable mail filter, Vadesecure, hosting their MTAs there.


- Mark Alley

Hope they have their IP ranges SWIP'ed by OVH, or at least 'rwhois'


--
"Catch the Magic of Linux..."

Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.

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


Re: [mailop] ANY OVH Contact?

2023-08-09 Thread Mark Alley via mailop


On 8/9/2023 3:31 AM, Jaroslaw Rafa via mailop wrote:

Dnia  9.08.2023 o godz. 11:00:12 Otto J. Makela via mailop pisze:

Unless the situation has dramatically changed in the last year,
OVH has no functioning abuse team. I block a majority of their nets
from sending email, don't seem to getting any false positives.

Luckily you don't block the net where my server is located, otherwise you
would get a false positive, if I would send mail to you...


Even by merely glancing at one of those subnets 15.204.0.0/17, I see a 
relatively sizable mail filter, Vadesecure, hosting their MTAs there.


- Mark Alley
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] ANY OVH Contact?

2023-08-09 Thread Michael Peddemors via mailop
Just ONE ?? Hehehe.. Block and Forget.. Lot's of active affiliate 
spammers, malware senders, BEC actors, phishing, and throw away domains..


Sorry, but OVH team's are completely uncaring on this matter it appears.

It's a sad trend, those hosting providers who's 'in-use' IP count is 
more important..


Anne, sorry but persoanally think things aren't going to change, unless 
it costs them money, eg, fines, class action suits, or blacklist them 
enough that they don't get active customers.. IMHO..


And even worse, it encourages other industry players to follow suit..

On 2023-08-08 08:44, Anne Mitchell via mailop wrote:

Does anyone have *any* contact at OVH?  Reports to abuse@, and through the 
abuse page, have yielded nothing for this very unrepentant spammer. :-(

Thanks in advance for any assistance here.

Anne

---
Anne P. Mitchell
Attorney at Law
Email Law & Policy Attorney
CEO Institute for Social Internet Public Policy (ISIPP)
Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal email marketing law)
Author: The Email Deliverability Handbook
Board of Directors, Denver Internet Exchange
Dean Emeritus, Cyberlaw & Cybersecurity, Lincoln Law School
Prof. Emeritus, Lincoln Law School
Chair Emeritus, Asilomar Microcomputer Workshop
Counsel Emeritus, eMail Abuse Prevention System (MAPS)

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



--
"Catch the Magic of Linux..."

Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.

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


Re: [mailop] CS02 errors from Apple on Japanese emails only

2023-08-09 Thread Christine Borgia via mailop
Will do, Suresh. Thanks!

On Wed, Aug 9, 2023 at 10:41 AM Suresh Ramasubramanian 
wrote:

> Hi. Please feel free to forward me any ticket responses you got from the
> postmaster team, glad to take a look
>
> --srs
> --
> *From:* mailop  on behalf of Christine Borgia
> via mailop 
> *Sent:* Wednesday, August 9, 2023 7:57:06 PM
> *To:* mailop@mailop.org 
> *Subject:* [mailop] CS02 errors from Apple on Japanese emails only
>
> If anyone here is from Apple, I'd love to chitty chat with you about CS02
> errors we see only for our Japanese customers. The postmaster provides
> inconsistent responses, mostly regarding authentication as a solution. All
> of our mail is fully authenticated. I'd be interested in passing along some
> information to someone at Apple for you to use or not use as you please.
>
> Best,
> Christine
>
> --
> *Christine Borgia*
> Email Deliverability Manager
> [image: Shopify]
> 
>
-- 
*Christine Borgia*
Email Deliverability Manager
[image: Shopify]

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


Re: [mailop] CS02 errors from Apple on Japanese emails only

2023-08-09 Thread Suresh Ramasubramanian via mailop
Hi. Please feel free to forward me any ticket responses you got from the 
postmaster team, glad to take a look

--srs

From: mailop  on behalf of Christine Borgia via 
mailop 
Sent: Wednesday, August 9, 2023 7:57:06 PM
To: mailop@mailop.org 
Subject: [mailop] CS02 errors from Apple on Japanese emails only

If anyone here is from Apple, I'd love to chitty chat with you about CS02 
errors we see only for our Japanese customers. The postmaster provides 
inconsistent responses, mostly regarding authentication as a solution. All of 
our mail is fully authenticated. I'd be interested in passing along some 
information to someone at Apple for you to use or not use as you please.

Best,
Christine

--
Christine Borgia
Email Deliverability Manager
[Shopify]
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] CS02 errors from Apple on Japanese emails only

2023-08-09 Thread Christine Borgia via mailop
If anyone here is from Apple, I'd love to chitty chat with you about CS02
errors we see only for our Japanese customers. The postmaster provides
inconsistent responses, mostly regarding authentication as a solution. All
of our mail is fully authenticated. I'd be interested in passing along some
information to someone at Apple for you to use or not use as you please.

Best,
Christine

-- 
*Christine Borgia*
Email Deliverability Manager
[image: Shopify]

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


Re: [mailop] Send emails over O365 to Google with a specific domain are rejected

2023-08-09 Thread Gellner, Oliver via mailop
On 09.08.2023 at 10:05 Otto J. Makela via mailop wrote:

> On 8/7/23 03:06, Al Iverson via mailop wrote:

>> If MS is using IPv6 to send the mail to Google, you might be in an
>> extra difficult spot. Not everybody agrees/believes this, but in my
>> experience Gmail is more quick to block IPv6-sent mail; they're more
>> stringent about what they might let through versus IPv4. I can't
>> imagine that's something you can control, but, hey, if I'm wrong and
>> it is, it's worth checking.

> I concur, Google seems to think that if you are using IPv6 for transport you 
> must be Teh Master of Teh Internet™, and it'll be trivial for you to get 
> every single detail right in your messages.

Another explanation might be that Google wants to introduce additional security 
controls without breaking all kind of existing communications. So they enforce 
those controls primarily for new remote endpoints. When you try to send 
messages to Google from an IPv4 address that Google has not received 
connections from before, you might also be subjected to requirements which 
other servers that send emails from their IP addresses since years do not (yet) 
have to fulfill. And since most IPv6 addresses did not send emails multiple 
years ago, they can all be considered new.

--
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.


smime.p7s
Description: S/MIME cryptographic signature
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] ANY OVH Contact?

2023-08-09 Thread Jaroslaw Rafa via mailop
Dnia  9.08.2023 o godz. 11:00:12 Otto J. Makela via mailop pisze:
> 
> Unless the situation has dramatically changed in the last year,
> OVH has no functioning abuse team. I block a majority of their nets
> from sending email, don't seem to getting any false positives.

Luckily you don't block the net where my server is located, otherwise you
would get a false positive, if I would send mail to you...
-- 
Regards,
   Jaroslaw Rafa
   r...@rafa.eu.org
--
"In a million years, when kids go to school, they're gonna know: once there
was a Hushpuppy, and she lived with her daddy in the Bathtub."
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] ANY OVH Contact?

2023-08-09 Thread Otto J. Makela via mailop

On 8/8/23 18:44, Anne Mitchell via mailop wrote:


Does anyone have *any* contact at OVH?  Reports to abuse@, and
through the abuse page, have yielded nothing for this very
unrepentant spammer. :-(


Unless the situation has dramatically changed in the last year,
OVH has no functioning abuse team. I block a majority of their nets
from sending email, don't seem to getting any false positives.

5.196.0.0/16
15.204.0.0/17
51.38.0.0/16
51.68.0.0/16
51.77.0.0/16
51.83.0.0/16
51.89.0.0/16
51.195.0.0/16
51.254.0.0/15
54.37.0.0/16
54.38.0.0/16
135.125.128.0/17
147.135.0.0/16
151.80.0.0/16
162.19.128.0/17
188.165.0.0/16

--
   /* * * Otto J. Makela  * * * * * * * * * */
  /* Phone: +358 40 765 5772, ICBM: N 60 10' E 24 55' */
 /* Mail: Mechelininkatu 26 B 27,  FI-00100 Helsinki */
/* * * Computers Rule 0100 01001011 * * * * * * */

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


Re: [mailop] Send emails over O365 to Google with a specific domain are rejected

2023-08-09 Thread Otto J. Makela via mailop

On 8/7/23 03:06, Al Iverson via mailop wrote:


If MS is using IPv6 to send the mail to Google, you might be in an
extra difficult spot. Not everybody agrees/believes this, but in my
experience Gmail is more quick to block IPv6-sent mail; they're more
stringent about what they might let through versus IPv4. I can't
imagine that's something you can control, but, hey, if I'm wrong and
it is, it's worth checking.


I concur, Google seems to think that if you are using IPv6 for transport
you must be Teh Master of Teh Internet™, and it'll be trivial for you
to get every single detail right in your messages.

Then again, I can easily see how spammers would use IPv6 addresses to
snowshoe their spam insertion.
--
   /* * * Otto J. Makela  * * * * * * * * * */
  /* Phone: +358 40 765 5772, ICBM: N 60 10' E 24 55' */
 /* Mail: Mechelininkatu 26 B 27,  FI-00100 Helsinki */
/* * * Computers Rule 0100 01001011 * * * * * * */

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