Re: [mailop] Support contact for Shaw.ca

[Hugh E Cruickshank via mailop]

From: Hugh E Cruickshank via mailop Sent: February 5, 2024 16:52
> From: Scott Undercofler via mailop Sent: February 1, 2024 17:04
> >
> > The servers at shaw are configured to reject non-RFC bare linefeeds.
> 
> Silly me I was looking for bare CRs as the error message advised. I
> will now go back and review the code for bare LFs. I am also having
> the code reviewed by someone else.
> 
> > Can you elaborate on why you’re sending them as they are not
> > allowed.
> 
> If we are sending them we are not doing so intentionally. The code in
> question was reviewed and updated for CR/LF pairing many years ago and
> has been running fine until now.

Hi All:

Just a quick post to confirm that we have resolved our issue...

The problem was indeed a "bare CR". The code in question had been
updated many years ago to ensure the all LFs were replaced by a CR/LF
however there was one line of code that applied this same replacement
to the body of a message without first checking to see if already
contained a CR/LF. If this occurred then we would end up with CR/CR/LF
hence the "bare CR" error message.

Cleaning up this code has resolved the problem. If there is anyone out
there working with OpenEdge and the FreeFrameWork smtpmail.p library
just drop me a line and I will pass on my code.

I would like to express my great appreciation to all who contributed.

Regards, Hugh

-- 
Hugh E Cruickshank, Payroll Guardian, www.PayrollGuardian.com

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

Re: [mailop] Support contact for Shaw.ca

[Scott Undercofler via mailop]

I never was good at goodbye. 

> On Feb 7, 2024, at 6:10 AM, Jaroslaw Rafa via mailop  
> wrote:
> 
> Dnia  6.02.2024 o godz. 15:26:33 Aric Archebelle-Smith via mailop pisze:
>> Beginning in late January, we received user reports that mail was not
>> being delivered to Shaw.ca addresses.  Users did not receive a
>> non-delivery notification, but our logs show the following rejection:
>> `status=sent (250 2.0.0 xxx...@pobox.com sender rejected.)`
> 
> Wonderful nonsense. Status code 250 and "sender rejected".
> -- 
> 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] Support contact for Shaw.ca

[Jaroslaw Rafa via mailop]

Dnia  6.02.2024 o godz. 15:26:33 Aric Archebelle-Smith via mailop pisze:
> Beginning in late January, we received user reports that mail was not
> being delivered to Shaw.ca addresses.  Users did not receive a
> non-delivery notification, but our logs show the following rejection:
> `status=sent (250 2.0.0 xxx...@pobox.com sender rejected.)`

Wonderful nonsense. Status code 250 and "sender rejected".
-- 
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] Support contact for Shaw.ca

[Scott Undercofler via mailop]

Replied of list. Sent from my iPhoneOn Feb 6, 2024, at 1:42 PM, Aric Archebelle-Smith via mailop  wrote:Hi all,I'm also looking for a contact for Shaw.ca, but it is not related to the changes due to the SMTP smuggling vulnerability. I've reached out to postmas...@shaw.ca, but have not received a response. Beginning in late January, we received user reports that mail was not being delivered to Shaw.ca addresses. Users did not receive a non-delivery notification, but our logs show the following rejection: status=sent (250 2.0.0 xxx...@pobox.com sender rejected.)If anyone could point me in the right direction, it'd be greatly appreciated.Cheers,Aric Archebelle-Smith___mailop mailing listmailop@mailop.orghttps://list.mailop.org/listinfo/mailop___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Support contact for Shaw.ca

[Aric Archebelle-Smith via mailop]

Hi all,

I'm also looking for a contact for Shaw.ca, but it is not related to the 
changes due to the SMTP smuggling vulnerability. I've reached out to 
postmas...@shaw.ca, but have not received a response.

Beginning in late January, we received user reports that mail was not being 
delivered to Shaw.ca addresses. Users did not receive a non-delivery 
notification, but our logs show the following rejection: `status=sent (250 
2.0.0 xxx...@pobox.com sender rejected.)`

If anyone could point me in the right direction, it'd be greatly appreciated.

Cheers,
Aric Archebelle-Smith
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Support contact for Shaw.ca

[Randolf Richardson, Postmaster via mailop]

> From: Scott Undercofler via mailop Sent: February 1, 2024 17:04
> > 
> > The issue you´re seeing is directly related to SMTP smuggling which
> > was discussed on list ad nauseam about a month ago.
> 
> I did see those but they did not appear to relate to anything we are
> doing so I did not read them in detail. I will now go back to these in
> the list archives.
> 
> > The servers at shaw are configured to reject non-RFC bare linefeeds.
> 
> Silly me I was looking for bare CRs as the error message advised. I will
> now go back and review the code for bare LFs. I am also having the code
> reviewed by someone else.

Feel free to contact me off-list so I can set up a special test 
address for you -- we're rejecting incorrectly formatted messages as 
well, and won't mind you running tests against our systems in the 
hopes that it helps you in your work on resolving this problem.

> > Can you elaborate on why you´re sending them as they are not allowed.
> 
> If we are sending them we are not doing so intentionally. The code in
> question was reviewed and updated for CR/LF pairing many years ago and
> has been running fine until now.

Yes.  That's likely the case for a lot of people since this SMTP 
Smuggling issue got into the spotlight in mid- to late-December 2023.

> We are a little suspicious that the issue is only occurring with mail
> sent to shaw.ca email addresses. Shaw was recently acquired by Rogers
> and they are in the process of merging Shaw operations into Rogers so
> it is not inconceivable that problems might occur during this merger.
> We are trying to reach techs at Shaw but it is not easy.

This is not a Shaw-to-Rogers migration issue.  There's a patch that 
was released for various mail servers in late December 2023 to 
prevent SMTP Smuggling from working, which is isn't as widely 
deployed as it should be -- my guess is that Shaw/Rogers have 
recently implemented this patch in the normal course of installing 
security updates to their systems.

> In the interim, we will continue to review our code and operations to
> see if it is a problem at our end.
> 
> Thank you very much for your suggestions.
> 
> Regards, Hugh
> 
> -- 
> Hugh E Cruickshank, Forward Software, www.forward-software.com
> 
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop


-- 
Postmaster - postmas...@inter-corporate.com
Randolf Richardson, CNA - rand...@inter-corporate.com
Inter-Corporate Computer & Network Services, Inc.
Vancouver, Beautiful British Columbia, Canada
https://www.inter-corporate.com/


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

Re: [mailop] Support contact for Shaw.ca

[Hugh E Cruickshank via mailop]

From: Scott Undercofler via mailop Sent: February 1, 2024 17:04
> 
> The issue you’re seeing is directly related to SMTP smuggling which
> was discussed on list ad nauseam about a month ago.

I did see those but they did not appear to relate to anything we are
doing so I did not read them in detail. I will now go back to these in
the list archives.

> The servers at shaw are configured to reject non-RFC bare linefeeds.

Silly me I was looking for bare CRs as the error message advised. I will
now go back and review the code for bare LFs. I am also having the code
reviewed by someone else.

> Can you elaborate on why you’re sending them as they are not allowed.

If we are sending them we are not doing so intentionally. The code in
question was reviewed and updated for CR/LF pairing many years ago and
has been running fine until now.

We are a little suspicious that the issue is only occurring with mail
sent to shaw.ca email addresses. Shaw was recently acquired by Rogers
and they are in the process of merging Shaw operations into Rogers so
it is not inconceivable that problems might occur during this merger.
We are trying to reach techs at Shaw but it is not easy.

In the interim, we will continue to review our code and operations to
see if it is a problem at our end.

Thank you very much for your suggestions.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

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

Re: [mailop] Support contact for Shaw.ca

[Andrew C Aitchison via mailop]

On Thu, 1 Feb 2024, Scott Undercofler via mailop wrote:


I'm 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.


On Feb 1, 2024, at 5:52 PM, Hugh E Cruickshank via mailop  
wrote:

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 there was anyone on this list who could provide a support
contact at shaw.ca that might be able assist us with identifying and
correcting this issue.


If Hugh's problem is indeed bare linefeeds, your bounce message may be
leading him astray by suggesting he has sent bare carriage-returns.

--
Andrew C. Aitchison  Kendal, UK
   and...@aitchison.me.uk___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Support contact for Shaw.ca

[Gellner, Oliver via mailop]

On 02.02.2024 at 01:52 Hugh E Cruickshank via mailop wrote
> 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 there was anyone 
> on this list who could provide a support contact at shaw.ca that might be 
> able assist us with identifying and correcting this issue.
> Any suggestions would be greatly appreciated.

Does the message contain a bare carriage return? If so you don't need to 
contact anyone, because the message is syntactically broken and needs to be 
fixed:
https://www.rfc-editor.org/rfc/rfc2822#section-2.3
> CR and LF MUST only occur together as CRLF; they MUST NOT appear 
> independently in the body.

Depending on your MTA you can enable debug logs or redirect/duplicate the 
message into a local mailbox to check its body.
Maybe you can also configure your MTA so that it does not accept such messages 
in the first place and is then stuck with them.

--
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.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Support contact for Shaw.ca

[Scott Undercofler via mailop]

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. 

> On Feb 1, 2024, at 5:52 PM, Hugh E Cruickshank via mailop  
> wrote:
> 
> 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 there was anyone on this list who could provide a support
> contact at shaw.ca that might be able assist us with identifying and
> correcting this issue.
> 
> Any suggestions would be greatly appreciated.
> 
> Regards, Hugh
> 
> -- 
> Hugh E Cruickshank, Forward Software, www.forward-software.com
> 
> ___
> 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] Support contact for Shaw.ca

[Hugh E Cruickshank via mailop]

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 there was anyone on this list who could provide a support
contact at shaw.ca that might be able assist us with identifying and
correcting this issue.

Any suggestions would be greatly appreciated.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

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