Ok...
exchange 5.5 SP4 with the update to the IMC to version 5.5.2655.55
and it's still relaying although hosts and clients that successfully authenticate is checked and routing for inbound is on (need it for remote clients..)
Just to check it out more i connected via telnet to: relay-test.mail-abuse.org and got this
:Relay test: #Test 17
>>> mail from: <spamtest@[***.***.***.***]>
<<< 250 OK - mail from <spamtest@[***.***.***.***]> <-!! removed ip to prevent more abuse !!
>>> rcpt to: <mail-abuse.org!nobody>
<<< 250 OK - Recipient <MAIL-ABUSE.ORG!NOBODY>
>>> QUIT
<<< 221 closing connection
Tested host banner: 220 host.domain ESMTP Server (Microsoft Exchange Internet Mail Service 5.5.2655.55) ready
System appeared to accept 1 relay attempts
Can anyone else verify this with their patched version?
I'm wondering if the local box should be allowed to relay for itself.. i'm half tempted to put the external IP and 127.0.0.1 as not allowed to route.. not sure of the consequences of this though.
exchange 5.5 SP4 with the update to the IMC to version 5.5.2655.55
and it's still relaying although hosts and clients that successfully authenticate is checked and routing for inbound is on (need it for remote clients..)
Just to check it out more i connected via telnet to: relay-test.mail-abuse.org and got this
:Relay test: #Test 17
>>> mail from: <spamtest@[***.***.***.***]>
<<< 250 OK - mail from <spamtest@[***.***.***.***]> <-!! removed ip to prevent more abuse !!
>>> rcpt to: <mail-abuse.org!nobody>
<<< 250 OK - Recipient <MAIL-ABUSE.ORG!NOBODY>
>>> QUIT
<<< 221 closing connection
Tested host banner: 220 host.domain ESMTP Server (Microsoft Exchange Internet Mail Service 5.5.2655.55) ready
System appeared to accept 1 relay attempts
Can anyone else verify this with their patched version?
I'm wondering if the local box should be allowed to relay for itself.. i'm half tempted to put the external IP and 127.0.0.1 as not allowed to route.. not sure of the consequences of this though.