|
This can also come about through use
of a mail gateway. I used a Symantec SMTP
virus gateway for a while. I stopped using it because I couldn't turn off the
bounce messages.
When I
asked Symantec how to stop the bounces, they said they never even
considered making that possible because it would violate the RFCs.
They told me that the RFCs required that receiving mail server notify the
sender that it can't deliver, either with a 550 at envelope time or with a
bounce message.
Of course, if that's true, we
are all violating the RFCs every day.
-Dave Doherty
Skywaves, Inc.
----- Original Message -----
Sent: Tuesday, April 12, 2005 2:58
PM
Subject: RE: [Declude.JunkMail] SpamCop
blacklist "Misdirected bounces"
Let me guess, you
are using the evil BOUNCEIFYOUMUST action in Declude JM?
-----Original
Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Technical
Support
Sent:
Tuesday, April 12,
2005 11:34
AM
To: [email protected]
Subject: [Declude.JunkMail] SpamCop
blacklist "Misdirected bounces"
I just found out that our mail
server has been blacklisted by spamcop, apparently for "Misdirected bounces"
which seems to be nothing more than bouncing a message after first accepting
it (I pasted Spamcop's explanation below). I'm running Imail v8.05
with declude v1.82, and I'm not sure how to fix this to Spamcop's
satisfaction. Has anyone else had this issue before, and if so, what can
be done to fix it?
Problem: Misdirected bounces
Description: When a mail server accepts a
message and later decides that it can't deliver the message, it is required to
send back a bounce email to the sender of the original message. These bounce
emails are often misdirected.
Solution: Upgrade and/or configure your mail server
software so that this situation is never encountered. Configure your software
to either reject messages during delivery or accept them permanently. Do not
let your software make choices about delivery after it has accepted a message.
If you must accept delivery before you know the status of a message, then file
it internally - do not send, forward or bounce it outside your organization.
The errant message can be placed in a special folder or routed to your
postmaster
|
