SpamCop keeps listing my server as a spammer. I have my opinions about
SpamCop in general and mail servers who would bounce mail solely on a
rumor-mill service. But the fact remains that it's happening.
For the record... I have a small set of clients, I'm not an open relay, and
I'm certain no spam is being generated out of my server.
According to SpamCop, I must be bouncing undeliverable emails (which I am).
Apparently, the latest spammer trick is to put SpamCop's 'spam trap' email
address as the sender, so when I bounce the email as undeliverable, it goes
straight to SpamCop and I am now a "sender of spam".
SpamCop says my mail server should simply reject the request immediately as
undeliverable and not even accept it. The way I understand James working,
that's not possible. James accepts everything and then runs the mail
through the matcher/mailet/processor chain, right? So instead of an "I
can't accept this email" response, James accepts the mail, and then will
send a bounce response email later.
What is the answer here?
1) Simply turn off bouncing on undeliverable (that's my interim
fix). But this means users who send legitimate email to my clients with a
simple typo in the address will never know the email was not delivered.
2) leave as is and do delayed bounces (I'll go out of business if
SpamCop keeps listing me...)
3) have James do immediate rejection (don't know how to do it...)
and since I run virtual addressing, James would still have to run a mailet
or two on each inbound connection in order to allow me to tell it whether I
want to accept it. Is that possible?
Maybe this problem is already solved, and I'm just unaware. But at this
point, this is a very serious problem for me.
Has anybody else been hit by SpamCop?? What is the consensus of opinion on
bouncing undeliverable emails?
Please help!
Thx
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
