>> If I could I would bounce their C/R so it never get to us. I
tried it once and it got us in a loop with another ISP's C/R
<<
Yes, that's Declude's fault as much as it
is an unacceptable C/R implementation. NEITHER should be sending notices
from anything but NULL. If at least ONE party had their act together,
there would be no loops.
Declude has a HUGE flaw that it's OWN
bounce messages (and other notices), cannot be sent from the <> (null)
sender. They are using
the Imail mailer to generate their notices, which doesn't support <> as
the sender. They really need to allow us to define the path of one of the
readily available third party mailers that CAN send messages from
NULL. Best
Regards
|
Title: Message
- RE: [Declude.JunkMail] Earthlink now using challenge-respo... Andy Schmidt