At 2:58 PM -0800 01/07/2003, Paul Didzerekis wrote:

As I stated before there IS a bug in the latest version of SIMS. If I have EITHER the backup listed in the client host list OR have the

3-rivers.com = 3-rivers.com.smtp
The line above is what tells the secondary to BE a secondary for that domain. Without it, non-local users could not send mail to your domain via the "secondary" MX. Go ahead and try it; send mail to an account at 3-rivers.com through the "secondary" server from an address that is not trusted by that server. See what happens.


line in the router of the secondary then my secondary fails the open relay test that ORDB.org is using and they are getting their mail through using the foriegnaccount@foreigndomain@mydomain hack. My secondary will forward the message to the primary and then the primary will relay the message out to them.
It sounds to me like the secondary is a trusted client host of the primary server. If it's trusted, then naturally it will be allowed to send mail to any domain.


And that is my point how is my secondary supposed to work if I have to remove it from the client host list and remove the .smtp line from the router to close this hole?
Only remove the secondary as a client host from the primary. Leave the router line in the secondary's router.


I have done multiple test to confirm this and I am not going to do another because then my server gets blacklisted again.
Have you tried it WITH the router line on the secondary but without the secondary as a trusted host?

If you reread what I wrote you will see that I HAVE tried it with the router line and the secondary not in the client host list. You are not reading what I wrote before you reply.

Paul

#############################################################
This message is sent to you because you are subscribed to
the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to <[EMAIL PROTECTED]>



Reply via email to