Re: [mailop] Apple mail admins?

[John Levine via mailop]

It appears that Mendel Kucharzeck via mailop  
said:
>Hi,
>
>I would try contacting icloudad...@apple.com 

Or, of course, you could tell us what domain and what server and quite possibly
someone would spot the problem.

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

Re: [mailop] [External] Gmail has a thing about dots

[John Levine via mailop]

It appears that Kevin A. McGrail via mailop  
said:
>Gmail treats dots as non-existent. 

These dots aren't in the Gmail address.  They're in the return address in the 
message.

>On 5/2/2024 3:02 PM, John Levine via mailop wrote:
>> While debugging something else, I've been trying to send messages to myself
>> from the address a...@m.jl.ly.  RFC 5321 says two dots in a row need to be
>> quoted, and I have checked that my mail system does indeed put in the quotes
>> and it says
>>
>> MAIL FROM:<"a..b"@m.jl.ly>
>>
>> But Gmail still doesn't like it, with the error message suggesting that 
>> something at
>> their end stripped the quotes too early   Huh?
>>
>> Outlook/Hotmail accepts it but puts it in the spam folder which I guess is 
>> OK.
>>
>> R's,
>> John
>>
>> Connected to 2607:f8b0:4004:0c17::::001a but sender was rejected.
>> Remote host said: 553-5.1.7 The sender address  is not a valid 
>> RFC 5321 address. For
>> 553-5.1.7 more information, go to
>> 553-5.1.7  https://support.google.com/a/answer/3221692 and review RFC 5321
>> 553 5.1.7 specifications. 
>> e5-20020a0562141d0500b0069b3262b75fsi1739474qvd.226 - gsmtp
>>
>>   ...
>>
>> Return-Path: <"a..b"@m.jl.ly>
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Apple mail admins?

[Mendel Kucharzeck via mailop]

Hi,

I would try contacting icloudad...@apple.com 

Best,
Mendel

> Am 02.05.2024 um 23:13 schrieb Jason R Cowart via mailop :
> 
> Is anyone from the Apple email team here by chance?  If so, please contact me 
> off list.
>  It appears that Apple is sending to our users via a legacy mail server that 
> is no longer in our MX record.
>  Thanks,
> Jason Cowart
> Stanford University
> ___
> 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] Apple mail admins?

[Jason R Cowart via mailop]

Is anyone from the Apple email team here by chance?  If so, please contact me 
off list.

It appears that Apple is sending to our users via a legacy mail server that is 
no longer in our MX record.

Thanks,
Jason Cowart
Stanford University
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] [External] Gmail has a thing about dots

[Kevin A. McGrail via mailop]

Gmail treats dots as non-existent.  So kevin.mcgr...@gmail.com and 
kevinmcgr...@gmail.com are the same account.


https://support.google.com/mail/answer/7436150?hl=en

HTH, KAM

On 5/2/2024 3:02 PM, John Levine via mailop wrote:

RAPTOR REMARK: Alert! Please be careful! This email is from an EXTERNAL sender. 
Be aware of impersonation and credential theft.

While debugging something else, I've been trying to send messages to myself
from the address a...@m.jl.ly.  RFC 5321 says two dots in a row need to be
quoted, and I have checked that my mail system does indeed put in the quotes
and it says

MAIL FROM:<"a..b"@m.jl.ly>

But Gmail still doesn't like it, with the error message suggesting that 
something at
their end stripped the quotes too early   Huh?

Outlook/Hotmail accepts it but puts it in the spam folder which I guess is OK.

R's,
John

Connected to 2607:f8b0:4004:0c17::::001a but sender was rejected.
Remote host said: 553-5.1.7 The sender address  is not a valid 
RFC 5321 address. For
553-5.1.7 more information, go to
553-5.1.7  https://support.google.com/a/answer/3221692 and review RFC 5321
553 5.1.7 specifications. e5-20020a0562141d0500b0069b3262b75fsi1739474qvd.226 - 
gsmtp

  ...

Return-Path: <"a..b"@m.jl.ly>
___
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] Gmail has a thing about dots

[Benny Pedersen via mailop]

John Levine via mailop skrev den 2024-05-02 21:02:


Return-Path: <"a..b"@m.jl.ly>


less spammy without "

rfc or not

but imho < and > is required

in spamassassin From:addr "..." is spammy, while From:Name needs "

i noted you use rblsmtpd. with does imho not support tls

okay for testing :)



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

[mailop] Gmail has a thing about dots

[John Levine via mailop]

While debugging something else, I've been trying to send messages to myself
from the address a...@m.jl.ly.  RFC 5321 says two dots in a row need to be
quoted, and I have checked that my mail system does indeed put in the quotes
and it says

MAIL FROM:<"a..b"@m.jl.ly>

But Gmail still doesn't like it, with the error message suggesting that 
something at
their end stripped the quotes too early   Huh?

Outlook/Hotmail accepts it but puts it in the spam folder which I guess is OK.

R's,
John

Connected to 2607:f8b0:4004:0c17::::001a but sender was rejected.
Remote host said: 553-5.1.7 The sender address  is not a valid 
RFC 5321 address. For
553-5.1.7 more information, go to
553-5.1.7  https://support.google.com/a/answer/3221692 and review RFC 5321
553 5.1.7 specifications. e5-20020a0562141d0500b0069b3262b75fsi1739474qvd.226 - 
gsmtp

 ...

Return-Path: <"a..b"@m.jl.ly>
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] Microsoft breaking ARC?

[Chris Adams via mailop]

My $DAYJOB has a service that does some email processing for customers
with Microsoft email, where MS gets a message, passes it to us with a
criteria based route, and then we pass it back to MS.  We are setting up
ARC to meet MS's requirements, and I have found that MS is passing
messages to us with already-broken ARC sealing.

Specifically, if a Hotmail user (or any MS email user in a different
domain I believe) sends a message, it gets a bunch MS-specifc headers,
some of which are then included in the ARC-Message-Signature header
list.  The specific problem headers are:

X-MS-Exchange-AntiSpam-MessageData-0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount

Then the message goes to a different MS server for the recipient domain,
which does a second ARC seal, including those same headers in the AMS
list.  However, AFTER doing the seal, MS renames those headers,
inserting a "-Original" in the name (I assume because second MS server
sees "my header from an outside source").  Since they do this after
sealing, the message always gets to my edge server and fails an ARC
verify.

My understanding of the whole ARC process is that you should verify on
input, do any processing/modifications you need to do, then seal on
output (and not change the message from that point).

Am I misunderstanding, or is this a bug on MS's end?  If it's a bug...
any ideas on how to get that through to the right people at MS?  I'm
guessing front-line support is not going to understand this.
-- 
Chris Adams 
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop