[quote user="poopoo321"]
i had the same prob as zenic and i was looking at the first post you rote to him and i tried it and it didnt work! and ideas?
this is the error it gave me:
Warning: mail() [function.mail]: SMTP server response: 553 We do not relay without RFC2554 authentication. in C:\xampp\htdocs\tom\feedback.php on line 123
[/quote]
You need to provide a MercuryS session log to find out what is happening. If it is the ESMTP authorization problem then you will have to change your PHP application to use ESMTP authorization or turn off the anti-relay. You can turn off anti-relay setup in Configuration | MercuryS | Connection control as long as there is no access to MercuryS from the internet that the spammers can use to send mail through your server.
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).
[quote user="poopoo321"]<p>i had the same prob as zenic and i was looking at the first post you rote to him and i tried it and it didnt work! and ideas?</p><p>this is the error it gave me:</p><p>&nbsp;</p><p><b>Warning</b>: mail() [<a href="http://localhost/tom/function.mail" mce_href="http://localhost/tom/function.mail">function.mail</a>]: SMTP server response: 553 We do not relay without RFC2554 authentication. in <b>C:\xampp\htdocs\tom\feedback.php</b> on line <b>123</b>
</p><p>[/quote]</p><p>You need to provide a MercuryS session log to find out what is happening.&nbsp; If it is the ESMTP authorization problem then you will have to change your PHP application to use ESMTP authorization or turn off the anti-relay. You can turn off anti-relay setup in Configuration | MercuryS | Connection control as long as there is no access to MercuryS&nbsp; from the internet that the spammers can use to send mail through your server.</p><p>&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.
Important note:&nbsp; 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).</p><p>
</p>
