Messages like user passwords and login details etc that MODx sends.
MODx tried to send the message as
[email protected], rather than the
[email protected] which is set in the MODx system configuration -> user settings tab.
Sun 2005-08-07 22:41:44: [6317:1] Accepting SMTP connection from [127.0.0.1 : 1606]
Sun 2005-08-07 22:41:44: [6317:1] --> 220 Domain ESMTP MDaemon 8.0.2; Sun, 07 Aug 2005 22:41:44 +1200
Sun 2005-08-07 22:41:44: [6317:1] <-- HELO Machine-Name
Sun 2005-08-07 22:41:44: [6317:1] --> 250 Domain Hello Machine-Name, pleased to meet you
Sun 2005-08-07 22:41:44: [6317:1] <-- MAIL FROM:<[email protected]>
Sun 2005-08-07 22:41:44: [6317:1] --> 250 <[email protected]>, Sender ok
Sun 2005-08-07 22:41:44: [6317:1] <-- RCPT TO:<[email protected]>
Sun 2005-08-07 22:41:44: [6317:1] --> 530 Authentication required
Sun 2005-08-07 22:41:44: [6317:1] <-- QUIT
Sun 2005-08-07 22:41:44: [6317:1] --> 221 See ya in cyberspace
Sun 2005-08-07 22:41:44: [6317:1] SMTP session successful (Bytes in/out: 92/234)
Sun 2005-08-07 22:41:44: ----------
As you see the MAIL FROM tag used during the SMTP session should have read
[email protected], but MODx (or something related) used the
[email protected] instead.
So I must have given it the admin address at some stage, but can only think maybe during the install. I must have then changed it to the briggsys address in the GUI but somewhere MODx still thinks its the orginal address. (which is why I think it might be a bug)
The email also has a Return-Path of
[email protected], not briggsys.
Also to prove its not the mailserver doing it, it was giving 550 errors (Sender Unkown) because that admin account no longer exists.