Hello! I've been using SpamAssassin here for some time now, and haven't done much configuration. Procmail calls spamassassin on my Gentoo Linux box, configured without bayes but with network checks.
Now I realized that mail I send will be marked by such a setup as spam. There are mostly two rules that hit: HELO_DYNAMIC_IPADDR and RCVD_IN_SORBS_DUL. The latter one only happens some times, I guess it's a timeout issue, because it can happen or not for the very same mail. I'm connected through DSL with a dynamic IP, and using Thunderbird to send mails through an IMP called GMX using SASL authentication. I attached an email showing this behaviour, including report header. I got AWL for me, but I understand that AWL are local knowledge and I could not rely on them when writing to someone else for the first time. Is it intended that the two rules matching my mail both are based on the same fact, i.e. me using a dynamic IP? Each one already has quite a high rating, but together they are enough to reject mails on default config. My IMP did authenticate the submission, is there some way this can be used for whitelisting? Or should the IMP change something, drop Received headers or some such? Or is it simply not intended for users to run the default config, so I should fix this myself and anybody using a default config has to expect such drops? I would be glad for suggestions on how I can get my regular email through the increasing number of SpamAssassin setups out there. Greetings, Martin von Gagern
--- Begin Message ---Waiting for SORBS hit.
--- End Message ---
signature.asc
Description: OpenPGP digital signature
