On 2022-04-27 15:30:33 -0400, Greg Wooledge wrote: > On Wed, Apr 27, 2022 at 07:26:31PM +0100, Brian wrote: > > On Wed 27 Apr 2022 at 08:05:46 -0400, Haines Brown wrote: > > > A message that you sent could not be delivered to one or more of its > > > recipients. This is a permanent error. The following address(es) failed: > > > > This message is from your smarthost, mail.guardedhost.com. > > It doesn't look like it to me.
Agreed. The mail was rejected by the smarthost, and the user's machine lenin.histomat.net reported this error back to the user as a mailer-daemon message. > > > sur...@popcon.devuan.org > > > host mail.guardedhost.com [216.239.133.245] > > > SMTP error from remote mail server after pipelined sending data block: > > > 553 5.7.1 <r...@histomat.net>: Sender address rejected: > > > not owned by user bro...@historicalmaterialism.info > > > > Reporting-MTA: dns; lenin.histomat.net > > > However, the devuan server apparently decides to look at what is in > > the mail being sent. At least, that is what I surmise from > > > > ...after pipelined sending data block > > > > It decides to reject the mail on what it sees, not on guardedhost.com > > being an inappropriate sender. > > That's a very interesting conclusion, but it's not what I'm seeing. > > First, I'm just ignoring the "after pipelined sending data block" part, > because I don't know what that means. I think that the data block was sent at the same time that the sender address was inspected (hence the word "pipelined", which just means that several operations overlap, which is common in SMTP to speed up things: the client doesn't have to wait for the server reply to send the next data). > The clearest part is "<r...@histomat.net>: Sender address rejected". > That sounds very much like it rejected the message specifically because > it didn't like the sender address. The "not owned by user...." part > is supporting detail. There's nothing here to indicate that it inspected > the body in order to make its rejection decision. > > So, what I'm seeing here: > > 1) The "Reporting-MTA: dns; lenin.histomat.net" tells us which MTA is > actually writing this error message. > > 2) "sur...@popcon.devuan.org" is the intended recipient address. > > 3) "host mail.guardedhost.com [216.239.133.245]" is the remote host the > MTA was talking to when the error occurred. > > 4) The "SMTP error ..." line is gibberish to me, except that it tells us > that the remote mail server (the smarthost) is who generated the error. > > 5) The two lines starting with "553 5.7.1 ..." were generated by the > smarthost, and reported here by the local MTA. > > As I've said, I don't use exim myself, so I might be mistaken about some > or all of these conclusions. But that's my interpretation. I entirely agree with this interpretation. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
