>>We have a "canned response" we send to people who send us
>>complaints where
>>the E-mail didn't originate from us (we have one domain that for some
>>reason gets occasional abuse@ complaints like the one you saw).

Would you care to share your response with us please? :))
The one we have is in the format:

---
Thank you for sending E-mail to [EMAIL PROTECTED] However, after reviewing the E-mail that you sent, it appears that it was not sent from any users of [organization name], and never went through any of our servers. If you feel that our analysis was in error, please re-send the E-mail and explain why you think that example.com was involved. Thank you.
---

This is for a domain that often gets abuse@ complaints that for E-mails that don't even have any IP/domain in them that are associated with our domain (the abuse@ address has accidentally been listed some places as a generic abuse@ address), so it may not be appropriate for all situations. I'm sure someone could come up with a more detailed canned response that would help explain why a spam with 'example.com' in the headers probably has nothing to do with example.com.
-Scott

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.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.

Reply via email to