SA Bugzilla – Bug 3879
Compatibility of our software with Spamassassin
Last modified: 2004-10-06 09:49:45 UTC
I'm writing because my company has an add-in for Microsoft Outlook that I would like to make sure is compatible with your software. Our product, RelationshipSecure, helps users stay in touch with their contacts. It can send out emails to verify a contact's details are still correct or messages informing contacts about updates to one's own contact information. Our program competes with Plaxo, GoodContacts and Corex AccuCard. Some of our users have experienced difficulties getting our software to work on their systems because their spam blocking software was blocking messages from our system. When a user sets up RelationshipSecure for the first time, it sends a validation email to their computer which comes from server@relationshipsecure.com. Some messages our system sends will come from info@relationshipsecure.com. If the validation email is mistaken for spam, RelationshipSecure won't get activated. In this case, we often get support requests from our users complaining that the program's not working. In addition to the initial validation email, our system also sends automated emails to a user's system if they purchase the Professional version, to let them know one of their contacts opened an email, and in certain other situations. If you maintain any sort of global whitelist for your software, I would like to request that you add our domain to it. This will make our job of supporting any mutual customers we share with SpamAssassin much easier. Thank you very much Scott Brown CEO RelationshipSecure
If you want to get whitelisted, your best bet is to take a look at this page documenting how to avoid FPs as a sender: http://wiki.apache.org/spamassassin/AvoidingFpsForSenders If there are specific rules that are hitting legitimate email, please feel free to report those in new bugs, especially if you can provide a full example email (with full headers and body). Thanks for the report. I recommend we close this bug as WORKSFORME.
Oops, I didn't mean to close this yet... I was going to let someone else do that. ;-)
agreed. we generally do not whitelist specific sources, if it can be avoided.