|
Yes, I realise that, and am fully aware on the methods
to lock down the mail server but there are very good logistaical reasons why I
can implement that at the moment, so this is not the issue or the
solution for me at the moment.
I plan to implement SMTP AUTH in the near future,
BUT, the whitelisting in declude should still work.
This raises anotehr good question, if the
"whitelisting" does not work on more than a few email addresses, does this
mean that the "blacklisting" does not work either?
Kindest
Regards From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Bilbee Sent: Friday, July 28, 2006 7:54 PM To: [email protected] Subject: RE: [Declude.JunkMail] Max whitelists hit If
you are not authenticating your users then your SMTP server is open for spammers
to forge the “from” address to relay through your server! Unless you only allow
relaying from specific ip addresses. “Relay for local users only” is a great way
for spammers to hijack your server. “Relay
Mail for Addresses” and “No Mail Relay” are the only safe relay options.
Assuming the addresses trusted in relay for addresses are secure from
unauthorized relaying. Kevin
Bilbee From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig
Edmonds Thanks
John, but Authentication is not an option right now and I will suffer the few
forged addresses that come through. I did
not realise that there was a limit to the amount of domains I can put in the
whitelist and its worked until now whilst testing it with a few domains
but with a long list of 500 domains it does not work properly, when really it
should. Without
posting really really confidential information here, I need to be able
whitelist, the same way that I can blacklist. I have
one guy at domainA.com trying to send to another guy at domainB.com and both
domains are on the same server. Right
now I need to be able to use the whitelisting functionality of
declude. Kindest
Regards
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John T (Lists) 1.
Sorry, your email was not considered confidential and has been included in a
public archive for all to see. 2. As
I said before, please stop using the silly white listing of a domain. Haven’t
you heard of forged addresses? 3.
Please review your configuration and correct the problem causing your clients
outbound email to be scanned. What you are doing is a workaround, not fixing the
actual problem. You will have to bite the bullet and start forcing your users to
authenticate and in doing so can easily whitelist based upon the fact that they
authenticated. John
T eServices
For You "Seek,
and ye shall find!" -----Original
Message-----
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. |
- [Declude.JunkMail] Max whitelists hit Craig Edmonds
- RE: [Declude.JunkMail] Max whitelis... David Barker
- RE: [Declude.JunkMail] Max whit... Craig Edmonds
- RE: [Declude.JunkMail] Max ... John T \(Lists\)
- RE: [Declude.JunkMail] ... Craig Edmonds
- RE: [Declude.JunkM... John T \(Lists\)
- RE: [Declude.J... Craig Edmonds
- RE: [Declude.JunkM... David Barker
- RE: [Declude.JunkMail] ... Kevin Bilbee
- RE: [Declude.JunkM... Craig Edmonds
- Re: [Declude.J... Scott Fisher
- Re: [Declu... Matt
- Re: [Declude.JunkMail] Max ... Scott Fisher
- RE: [Declude.JunkMail] Max whit... Harry Vanderzand
- RE: [Declude.JunkMail] Max whitelis... IS - Systems Eng. \(Karl Drugge\)
- RE: [Declude.JunkMail] Max whit... GlobalWeb.net Webmaster
