On 08/26/2011 12:08 PM, Gilbert T. Gutierrez, Jr. wrote:
Getting used to using spamdyke. I have never used it before and it seems
to be causing problems for some of my customers. I have had to IP
whitelist a couple IPs for people who have always relayed their alarms
through my server..
The issue I still have not solved is my server requiring TLS on port
587. My old server did not (It was optional before and I cannot find the
setting to make it optional again). require TLS on 587. I am sure as I
look through Spamdyke files I will find that option.
Gilbert
---------------------------------------------------------------------------------
Let me see if I can clarify a couple things.
Port 587 requires authentication, but TLS is not required for smtp
(although TLS is highly recommended).
Spamdyke operates on port 25, and is not connected to port 587 in any
way. Running spamdyke on port 587 would be pointless, as port 587
requires authentication, and spamdyke bypasses all filters on
authenticated connections (in case any client program were to submit
using port 25).
Whitelisting certain IPs for relaying operational emails is not
uncommon. It's better to configure the client software to send with
authentication (and TLS), although that's sometimes not practical.
With this in mind, would you like to try again? ;)
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
