From: Skle.pik <sp...@ma...> - 2020-03-27 08:09:10
|
On 27/03/2020 07:41, Skle.pik wrote: > Hi, I've been using fetchmail for quite a while without any complain whatsoever, but recently I found some of the messages not to be delivered. The investigation of processing for not delivered mails shows Return-Path to be split to 2 lines: Return-Path: <noreply= abba.com__al4bl7qh36xreia2@35p 11.bnc.salesforce.com> Delivered-To: Unfortunately this makes mailer choking: SMTP> MAIL FROM:<noreply= abba.com__al4bl7qh36xreia2@35p 11.bnc.salesforce.com> SIZE=4070 SMTP< 553 5.0.0 .... Does anyone know who is to blame - is this Return-Path formatting violation on POP side, or maybe it is mailer being intolerant ? Cheers Sorry for broken formatting, seems like my web MUA can't do plaintext. Here is plaintext version of a message with some updates: Hi, I've been using fetchmail for quite a while without any complain whatsoever, but recently I found some of the messages not to be delivered. The investigation of processing for not delivered mails shows Return-Path to be split to 2 lines: Return-Path: <noreply=abba.com__al4bl7qh36xreia2@35p9h14cih4s.6f-1gv0suag.ap 11.bnc.salesforce.com> Delivered-To: Unfortunately this makes mailer choking: SMTP> MAIL FROM:<noreply=abba.com__al4bl7qh36xreia2@35p9h14cih4s.6f-1gv0suag.ap 11.bnc.salesforce.com> SIZE=4070 SMTP< 553 5.0.0 .... I did check POP3 side with Python poplib and clearly the Return-Path is split across lines - result below: (b'+OK', [b'Return-Path: <noreply=abba.com__al4bl7qh36xreia2@35p9h14cih4s.6f-1gv0suag.ap', b' 11.bnc.salesforce.com>', b'Delivered-To: Does anyone know who is to blame - is this Return-Path formatting violation on POP side, or maybe it is mailer being intolerant ? Cheers |