T 20080916 125920 48cfacc7 Connection closed with 127.0.0.1, 1 sec. elapsed.
T 20080916 125951 48cfacc8 Connection from 127.0.0.1
T 20080916 125952 48cfacc8 EHLO localhost
T 20080916 125952 48cfacc8 MAIL FROM:<sphan@southlandcrossingtv.no-ip.org> SIZE=2576
T 20080916 125952 48cfacc8 RCPT TO:<steve.phan@gmail.com>
T 20080916 125952 48cfacc8 DATA - 49 lines, 2675 bytes.
T 20080916 125952 48cfacc8 QUIT
T 20080916 125952 48cfacc8 Connection closed with 127.0.0.1, 1 sec. elapsed.
The logs look like mail received normally. The question is does MercuryE (or MercuryC) get this as outbound mail to the GMail account.
12:59:27: Job MG00000B: from sphan@southlandcrossingtv.no-ip.org (local)
To: steve.phan@gmail.com (non-local) (Job MO00000C) -OK
Looks like core processed the MG file pair in the queue from MercuryS and created an MO outbound file pair for MercuryE/C. Now what we need to see is the MercuryE/C log to see if the outbound mail was processed. Since it looks like you have a randomly assigned IP address you should be using MercuryC to send via the ISPs SMTP host to prevent the outbound mail from being blocked by blacklists.
Looks like a good server.
220 www.southlandcrossingtv.no-ip.org ESMTP server ready.
ehlo thomas
250-www.southlandcrossingtv.no-ip.org Hello thomas; ESMTPs are:
250-TIME
250-SIZE 0
250-AUTH CRAM-MD5 LOGIN
250-AUTH=LOGIN
250 HELP
Requested action not taken: mailbox name not allowed
553 We do not relay without RFC2554 authentication.
Verify that the username and password used in the password files are the same as being used in the authentication. Mercury supports an Internet standard called Authenticated SMTP: when this feature is enabled, Mercury will advertise to connecting clients that it can accept SMTP authentication. If a client then authenticates correctly, it will be allowed to relay. Pegasus Mail and other widely-used Internet mail clients support authenticated SMTP, and it is an excellent way of allowing your roving users to use your server without opening yourself to relay abuse. Mercury supports three Authentication methods - CRAM-MD5, PLAIN and LOGIN, although LOGIN and PLAIN are very weak and you should avoid clients that use them.
Authenticated SMTP requires that both the client and server have access to a common password. For that reason, you need to provide Mercury with a list of usernames and the passwords that correspond to them - Mercury typically cannot get this information from the operating system for security reasons. Enter the name of the file where Mercury should store the user/password combinations, then click the Edit button to edit it. Each line contains one username/password pair.
Important note: There is nothing that requires you to have a different SMTP Authentication password for every user on your system, nor is there anything that says that your SMTP Authentication username has to match any real user on your system. If you wish, it is perfectly permissible for you to set up a single AUTH username/password pair and provide it to all your users, although clearly this will have some ramifications for security.
If you check the control marked Authenticated SMTP connections may relay mail, then any authenticated connection (one where the user has provided any valid username/password pair defined in your SMTP Authentication file) will be permitted to relay messages even if it would otherwise have been prevented from doing so by either the normal or strict relaying tests (see above).
If you check the control marked Only Authenticated SMTP connections may relay mail, then SMTP authentication becomes mandatory for relaying - a non-authenticated connection will not be permitted to relay mail even if it would otherwise have been permitted to do so by either the normal or strict relaying tests. Because this option supersedes all other tests, selecting it will check and disable the other three controls in the group.
<blockquote><p>T 20080916 125920 48cfacc7 Connection closed with 127.0.0.1, 1 sec. elapsed.
T 20080916 125951 48cfacc8 Connection from 127.0.0.1
T 20080916 125952 48cfacc8 EHLO localhost
T 20080916 125952 48cfacc8 MAIL FROM:&lt;<a href="mailto:sphan@southlandcrossingtv.no-ip.org">sphan@southlandcrossingtv.no-ip.org</a>&gt; SIZE=2576
T 20080916 125952 48cfacc8 RCPT TO:&lt;<a href="mailto:steve.phan@gmail.com">steve.phan@gmail.com</a>&gt;
T 20080916 125952 48cfacc8 DATA - 49 lines, 2675 bytes.
T 20080916 125952 48cfacc8 QUIT
T 20080916 125952 48cfacc8 Connection closed with 127.0.0.1, 1 sec. elapsed.</p></blockquote><p>The logs look like mail received normally. &nbsp; The question is does MercuryE (or MercuryC) get this as outbound mail to the GMail account.</p><blockquote><p>&nbsp;12:59:27: Job MG00000B:&nbsp; from <a href="mailto:sphan@southlandcrossingtv.no-ip.org">sphan@southlandcrossingtv.no-ip.org</a> (local)
&nbsp;&nbsp; To: <a href="mailto:steve.phan@gmail.com">steve.phan@gmail.com</a> (non-local) (Job MO00000C) -OK</p></blockquote><p>Looks like core processed the MG file pair in the queue from MercuryS and created an MO outbound file pair for MercuryE/C. Now what we need to see is the MercuryE/C log to see if the outbound mail was processed.&nbsp; Since it looks like you have a randomly assigned IP address you should be using MercuryC&nbsp; to send via the ISPs SMTP host to prevent the outbound mail from being blocked by blacklists.</p><p>Looks like a good server.
</p><p>220 www.southlandcrossingtv.no-ip.org ESMTP server ready.
ehlo thomas
250-www.southlandcrossingtv.no-ip.org Hello thomas; ESMTPs are:
250-TIME
250-SIZE 0
250-AUTH CRAM-MD5 LOGIN
250-AUTH=LOGIN
250 HELP</p><p>&nbsp;</p><blockquote><p>Requested action not taken: mailbox name not allowed
553 We do not relay without RFC2554 authentication.</p></blockquote><p>Verify that the username and password used in the password files are the same as being used in the authentication. &nbsp;Mercury supports an Internet standard called Authenticated SMTP: when this feature is enabled, Mercury will advertise to connecting clients that it can accept SMTP authentication. If a client then authenticates correctly, it will be allowed to relay. Pegasus Mail and other widely-used Internet mail clients support authenticated SMTP, and it is an excellent way of allowing your roving users to use your server without opening yourself to relay abuse. Mercury supports three Authentication methods - CRAM-MD5, PLAIN and LOGIN, although LOGIN and PLAIN are very weak and you should avoid clients that use them.
Authenticated SMTP requires that both the client and server have access to a common password. For that reason, you need to provide Mercury with a list of usernames and the passwords that correspond to them - Mercury typically cannot get this information from the operating system for security reasons. Enter the name of the file where Mercury should store the user/password combinations, then click the Edit button to edit it. Each line contains one username/password pair.
<i><b>Important note:</b></i>&nbsp; <i>There is nothing that requires you to have a different SMTP Authentication password for every user on your system, nor is there anything that says that your SMTP Authentication username has to match any real user on your system. If you wish, it is perfectly permissible for you to set up a single AUTH username/password pair and provide it to all your users, although clearly this will have some ramifications for security.</i>
If you check the control marked Authenticated SMTP connections may relay mail, then any authenticated connection (one where the user has provided any valid username/password pair defined in your SMTP Authentication file) will be permitted to relay messages even if it would otherwise have been prevented from doing so by either the normal or strict relaying tests (see above).
If you check the control marked Only Authenticated SMTP connections may relay mail, then SMTP authentication becomes mandatory for relaying - a non-authenticated connection will not be permitted to relay mail even if it would otherwise have been permitted to do so by either the normal or strict relaying tests. Because this option supersedes all other tests, selecting it will check and disable the other three controls in the group.&nbsp;
</p>
