Hi Benoit,
I don't know if you already checked it, but this might be a useful source:
http://www.spamcop.net/fom-serve/cache/329.html
Exchange is mentioned there with either a solution for V 5.5 [1] or for 2k/2k3 [2].
[1] http://support.microsoft.com/default.aspx?scid=kb;en-us;837794 [2] http://support.microsoft.com/default.aspx?scid=kb;en-us;294757
I did not have a look at these URLs but they _might_ help you :-)
Anyway IMHO classifying mailservers as "spam"-servers just because of auto-responders is one thing why I would never use blacklists like spamcop. Imagine you have customers with so-called "catch-all" or "multidrop" accounts which are also using auto-responders. I cannot figure out a solution for this scenario without getting listed at spamcop at their current policy. If somebody knows a solution for qmail+vpopmail+chkuser => Please tell! Using another server for sending bounces/auto-responders is IMHO not a solution.
Cheers
Tobias
-----Ursprüngliche Nachricht----- Von: Benoit Panizzon [mailto:panizzon@woody.ch] Gesendet: Montag, 30. Januar 2006 09:35 An: swinog@swinog.ch Betreff: [swinog] Prevent Bounces from MS-Exchange?
Hi all
We got occasional complaint from spamcop and similar about exchange servers of customers sending bounces to faked sender addresses.
The only way to solve this problem I have found is to completely disable NDR in Exchange: http://support.microsoft.com/default.aspx?scid=kb;en-us;294757
Isn't there any way to make exchange reject unknown users during smtp handshake like all other MTA do?
-Benoit-
Hi all,
Tobias Orlamuende wrote:
Anyway IMHO classifying mailservers as "spam"-servers just because of auto-responders is one thing why I would never use blacklists like spamcop. Imagine you have customers with so-called "catch-all" or "multidrop" accounts which are also using auto-responders. I cannot figure out a solution for this scenario without getting listed at spamcop at their current policy. If somebody knows a solution for qmail+vpopmail+chkuser => Please tell! Using another server for sending bounces/auto-responders is IMHO not a solution.
Spamcop again... I really don't know what they're on. There are lots of DNSBL servers that do a good job, spamcop ist just about to drive all it's users crazy...
I kicked Spamcop when they started blacklisting 127.0.0.1 so that no system logs could be sent out by E-Mail...
CU Tobias
I kicked Spamcop when they started blacklisting 127.0.0.1 so that no system logs could be sent out by E-Mail...
Why would you subject internally generated mail to blacklist processing at all? I find it a bit questionable to use any blacklists in a binary fashion (unless you're _really_ 100% in line with their listing policy, which I'm normally not unless I compose the list myself;-)). Assign a hit a weight, and only drop if you're above a treshold (and if your recipient mailbox agrees to such drops, or the threshold). And certainly only do this with traffic from the "Most Evil Internet", not from trusted networks... Just my $0.02;-)
Markus
'llo,
swinog-list@dudes.ch wrote:
Why would you subject internally generated mail to blacklist processing at all?
good question. Problem is that my central mail-relay is shown to the outside (as a mail relay is supposed to be) - and it generates some triggers and alert mails upon special events (i.e. ssh probes etc.). And if those mails don't slip through... well...
I find it a bit questionable to use any blacklists in a binary fashion (unless you're _really_ 100% in line with their listing policy, which I'm normally not unless I compose the list myself;-)).
Well, this is a bit difficult if you're running a mail system with about 60 messages / minute for private purposes...
Assign a hit a weight, and only drop if you're above a treshold (and if your recipient mailbox agrees to such drops, or the threshold). And certainly only do this with traffic from the "Most Evil Internet", not from trusted networks... Just my $0.02;-)
that's the problem... my central mail relay is processing a lot evil content :-)
CU Tobias
-
swinog-list＠dudes.ch -
Tobias Goeller -
Tobias Orlamuende