From: jdow <jd...@ds...> - 2019-04-30 09:01:36
|
On 20190429 16:02:24, Matthias Andree wrote: > Am 27.04.19 um 23:28 schrieb jdow: >> fetchmaillog per item 5.txt >> >> Syslog from: env LC_ALL=C /usr/bin/fetchmail -d 60 --fetchmailrc >> /home/jdow/.fetchmailrc >> >> >> Apr 27 13:57:30 thursday fetchmail[31459]: starting fetchmail 6.3.24 >> daemon >> Apr 27 13:57:32 thursday fetchmail[31459]: 1 message for >> jd...@ea... at pop.earthlink.net (4706 octets). >> Apr 27 13:57:32 thursday postfix/smtpd[30762]: connect from >> localhost[::1] >> Apr 27 13:57:32 thursday postfix/smtpd[30762]: warning: Illegal >> address syntax from localhost[::1] in MAIL command: >> <JkiO@JkiO----------------------.us-west-2.compute.amazonaws.com> >> Apr 27 13:57:32 thursday fetchmail[31459]: reading message >> jd...@ea...@pop.earthlink.net:1 of 1 (4706 octets) (log message >> incomplete) >> Apr 27 13:57:32 thursday fetchmail[31459]: SMTP error: 501 5.1.7 Bad >> sender address syntax >> Apr 27 13:57:32 thursday fetchmail[31459]: not flushed >> Apr 27 13:57:32 thursday postfix/smtpd[30762]: disconnect from >> localhost[::1] > > > Joanne, > > This pretty much looks like the faulty message is in the > pop.earthlink.net account rather than the dslextreme.com, and I haven't > seen configuration or verbose logging of the earthlink polls yet in this > thread, unless I am overlooking something... and Postfix is right to > reject the mail address, it is outside the permitted syntax for MAIL > commands per the BNF syntax in RFC-5321 (page 41 bottom/42 top - in > prose that specifies that the hyphen cannot be head or tail of a > sub-domain part, but must be surrounded by "letter or digit"). > > The log message incomplete stems from the log "reading message" that > gets interrupted by the 501 5.1.7 error, logging makes this excursion, > and finally the "not flushed" concludes the original log message. > > HTH > For testing I disable the Earthlink accounts. That is why you don't see it. That said I doctored the .fetchmailrc file bringing down to a forced plain text. The message persisted. I rewrote the file (cleared it and retyped the text) and now the problem seems to have resolved. The data appears to be the same. The issue seems to be gone. I REALLY REALLY wish I know what change I made worked. But, I suspect it will be a phenomenon with nothing further known about it. (Yes, it was dumb of me to edit the way I did. I should have saved the old file to compare with the new. Ah well. I should know better. At least the log clutter is gone. Hm, I ought to play with tcpdump to see if there is an smtp connection going outside. I doubt it as that address bounced email from amazonaws with an account does not exit error. If there is such a thing you will hear from me again.) {O.O} Joanne |