Re: [mailop] Support contact for Shaw.ca

2024-02-29 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-07 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-07 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-06 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-06 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-05 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-05 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-02 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-02 Thread 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

Re: [mailop] Support contact for Shaw.ca

2024-02-01 Thread 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.

[mailop] Support contact for Shaw.ca

2024-02-01 Thread 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