Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

We finally found the original issue. It was related to the library from the sender that was dot stuffing using a regex without the Global flag in place... They sent a PR to the library. I learned some stuff with this issue ! Thanks everyone for your help here. Best regards, Cyril

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

> On 04.03.2024 at 11:42 Slavko via mailop: > > And what does aiosmtpd with message after it receive it? I guess, that it is > sending it out (to gmail), thus it acts as client... Does it quote (double) > that dot when message goes out? Just a little nitpick: aiosmtpd is a Python library to

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

Dňa 4. 3. o 11:09 Cyril - ImprovMX via mailop napísal(a): Pointing out the fact that the dot-stuffing works on the two sides (adding then removing) shows that in the current scenario, the issue is either caused by the sender or by us, and not between us and Gmail. And what does aiosmtpd with

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

Thanks everyone for your responses. I responded during the weekend but my email was too big and got rejected. It's not relevant anymore. Pointing out the fact that the dot-stuffing works on the two sides (adding then removing) shows that in the current scenario, the issue is either caused by the

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

Once upon a time, Cyril - ImprovMX said: > Just to clarify, I'm not trying to pin some issue on a company (Google) but > I'm trying to understand why aiosmtpd seems to follow an RFC that > appears to be clear on the behavior, that GMail doesn't do but doesn't > appear to be the only one (as my

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

On 01.03.2024 at 17:46 Cyril - ImprovMX via mailop wrote: Upon investigation, we discovered that indeed, checking the DKIM signature was failing because of a body mismatch. Digging further, we discovered that a dot was removed from the message when going through our servers. It turns out that

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

On 2024-03-01, Cyril - ImprovMX via mailop wrote: > @Julien Bradfield: > I've initially shared the exact line in the code on what Aiosmtpd - not my > software - is doing, which it is saying is following the RFC by removing > the first character if it's a dot. I could share emails that went I did

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

> From: Cyril - ImprovMX > It turns out that one of their link in the email is broken into multiple > line (following the RFC on that) Solution: don't follow the RFC on that, don't break into multiple lines. If you use Exim then in transports driver = smtp .ifdef

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

It appears that Cyril - ImprovMX via mailop said: >@John Levine , I'm not sure which line you are mentioning, >the one I used from the RFC ("... If the first character is a period and >there are other characters on the line, the first character is deleted.") >does mention "deleted", not

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

Unless I'm missing something, it's the first bullet in RFC5321 4.5.2. - Mark Alley On 3/1/2024 3:49 PM, Cyril - ImprovMX via mailop wrote: @Julien Bradfield: I've initially shared the exact line in the code on what Aiosmtpd - not my software - is doing, which it is saying is following the

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

@Julien Bradfield: I've initially shared the exact line in the code on what Aiosmtpd - not my software - is doing, which it is saying is following the RFC by removing the first character if it's a dot. I could share emails that went through Aiosmtpd and another that didn't, which would only show

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

It appears that Cyril - ImprovMX via mailop said: >-=-=-=-=-=- >-=-=-=-=-=- > >Just to clarify, I'm not trying to pin some issue on a company (Google) but >I'm trying to understand why aiosmtpd seems to follow an RFC that >appears to be clear on the behavior, that GMail doesn't do but doesn't

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

Just to clarify, I'm not trying to pin some issue on a company (Google) but I'm trying to understand why aiosmtpd seems to follow an RFC that appears to be clear on the behavior, that GMail doesn't do but doesn't appear to be the only one (as my user is generating a document that also doesn't

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

On Fri, Mar 1, 2024 at 8:46 AM Cyril - ImprovMX via mailop < mailop@mailop.org> wrote: > > Upon investigation, we discovered that indeed, checking the DKIM signature > was failing because of a body mismatch. Digging further, we discovered that > a dot was removed from the message when going

Re: [mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

On 2024-03-01, Cyril - ImprovMX via mailop wrote: > Upon further investigation, we realized that GMail does NOT respect that > RFC. They keep the dot. And if you add two dots, as per the RFC, GMail will > keep the two dots, making the URL broken. What *exactly* did you do to realize

[mailop] Dot as the first character of a line ? (RFC 5321, Section 4.5.2)

Hey everyone, I got a really strange issue today which boils down to how we interpret the RFC. A user reached out to us saying their email, when going through ImprovMX, where then failing the DKIM Signature. Upon investigation, we discovered that indeed, checking the DKIM signature was failing