-----Original Message----- From: Jeff Chan [mailto:jeffc@surbl.org] Sent: Tuesday, March 08, 2005 4:35 AM To: SURBL Discuss Subject: [SURBL-Discuss] RFC: Updated list removal statement
On a related note, I've updated the list removal statement on the SURBL web site to include: __
http://www.surbl.org/lists.html
List Removal
All of the data in SURBL lists come from external data sources. None of the SURBL lists come from data created here, so generally speaking to get a record off a list you should contact that data source as described earlier under each list. However, for the sc and ab lists you may send a removal request to whitelist at surbl dot org.
Note: Before reporting false positives, please check that they are actually on SURBL lists. This can be done for example with a name resolution or by using the SURBL+ checker tool. There is an intermittent bug with SpamAssassin that appears to show FPs when none actually exist. (See SpamAssassin Bugzilla id=3997.)
When sending a removal request, please include:
- Full and complete contact information for your organization including street address and telephone numbers,
- Information about your sending servers such as IP addresses,
- A sample message with full, sent headers and full message body including URIs,
- A brief description of your organization or a link to one,
- Your organization's published mail practices, especially its published anti-spam policies, or links to them.
If your organization does not publish and actually practice an anti-spam policy, it should. Please send your request from your organization's domain. Requests sent from Hotmail, Yahoo, gmail, etc. accounts may not be considered. __
How does this look to everyone? Too strict? Not strict enough? Too little info? Too much?
How about:
"Be prepaired to explain any UBE that is found to contain your domain."
"Understand that you ARE responsible for the actions of your affiliates."
"If you purchased a list which contains harvested addresses and use them in a mailing, then you are commiting a crime."
"'Just unsubscribe!', is NOT a valid response!"
--Chris