Im still learning spamdyke, and we are using it with QMAIL, and Im stuck on this one.
We have 5 distribution lists, lets call them emaila@domain.com, emailb@domain.com, etc., that receive messages from the same address, based on criteria lets call that sendera@domain.com.
Regardless of the destination, there are always the same details in my maillog when a message is received from sendera@domain.com. Here are the details
Jun 24 00:16:53 mail spamdyke[49849]: FILTER_WHITELIST_IP ip: 66.xxx.xxx.xxx file: /var/qmail/control/lists/w
Jun 24 00:16:53 mail spamdyke[49849]: ALLOWED from: sendera@domain.com to: emaila@domain.com origin_ip: 66.xxx.xxx.xxx origin_rdns: mailserver.domain.com auth: (unknown)
Jun 24 00:16:53 mail spamd[21324]: spamd: connection from localhost [127.0.0.1] at port 59444
Jun 24 00:16:53 mail spamd[21324]: Use of uninitialized value in concatenation (.) or string at /usr/local/bin/spamd line 2103, <GEN2442> line 2.
Jun 24 00:16:53 mail spamd[21324]: Use of uninitialized value in concatenation (.) or string at /usr/local/bin/spamd line 2108, <GEN2442> line 2.
Jun 24 00:16:53 mail spamd[21324]: Use of uninitialized value in scalar chomp at /usr/local/bin/spamd line 2115, <GEN2442> line 2.
Jun 24 00:16:53 mail spamd[21324]: spamd: processing message <prefix.mail.domaincolo.co
Jun 24 00:16:53 mail spamd[21324]: spamd: processing message <prefix.mail.domaincolo.co
Jun 24 00:16:58 mail spamd[21324]: spamd: clean message (-1.1/5.0) for emaila@domain.com:58 in 5.3 seconds, 1530 bytes.
Jun 24 00:16:58 mail spamd[21324]: spamd: result: . -1 - AWL,BAYES_05,RDNS_NONE scantime=5.3,size=1530,use
When I first noticed this entry, my assumption was that it was a rDNS issue but the rDNS does resolve from the sender domain. Oddly enough as well, mail from 1 of the 5 distribution lists was coming through although the message about AWL,BAYES_05,RDNS_NONE was displayed.
To test, I created a whitelist_ip entry for the IP of their mail server. It seems to have helped so we now receive e-mail from 2 of the 5 entries, but the message above still references the AWL,BAYES_05,RDNS_NONE. And, as a result, we are still not receiving messages from 3 of the 5 distribution lists.
It appears the whitelist_ip didnt give me the desired effect. Any advice on how I can make adjustments so that this e-mail comes through from this sender? Or, work with the sender so that they make adjustments so that mail will flow to us without adjusting our spam filters? My preference would be to have this fixed without having to maintain the whitelist_ip entry.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I will try whitelisting the sender - I saw that documentation and read how it's not recommended to whitelist the sender since it is so easy to spoof. I wanted to take a better approach of doing the IP, but will try this and see what happens, if only temporarily.
I'll post back with results - I'm only with QMAIL for a few more months until we migrate to Exchange, so, if I can avoid it, I don't want to tamper with SpamAssassin.
I WIW HOWD BY PONGUE about your transition to Exchange... but there is a REASON why Exchange experts are paid a LOT of money... and it's NOT likely because Exchange is so easy and intuitive to administer!
As for "changing" SpamAssassin, I'm only suggesting that it may need to be re-installed, not re-configured. Either your SpamAssassin file (spamd) has become corrupted (unlikely), or your PERL installation doesn't match with what SpamAssassin is expecting -- thus, updating both to the "latest versions" should get rid of those error messages.... error messages that MAY be the reason your messages are being blocked (vs. SpamDyke blocking them).
Then again, if you're relying solely on SpamDyke, you may want to consider REMOVING SpamAssassin to avoid those errors.
As regards the "name" vs. "IP" whitelisting, you already indicated that you didn't want to have to "maintain" the IP whitelist entries -- how else would you propose to identify the "allowed" messages?
I don't mean to sound flippant -- but you do need to think about what you're asking the system to do, and reconcile that with the resources available.
Good Luck!
Dan
IT4SOHO
I don't know what "I WIW HOWD BY PONGUE" means?
We have had a lot of rDNS issues with users not being able to e-mail us, and my preferred approach was to work out the issues with them (i.e. helping them create valid rDNS entries). I was looking for a translation to the rule AWL,BAYES_05,RDNS_NONE so I could take that approach as well. I'd like to fix the issue, as it appears to only be impacting this one company, vs. making an exception to which we currently aren't making any for any of our filters.
"I WIW HOWD BY PONGUE" is phonetically what it would sound like if I said "I WILL HOLD MY TONGUE" while I was actually holding my tongue! :-) [an attempt at humor while noting that Exchange as a QMail replacement may not be as easy as you're hoping]
You can disable the rDNS lookup in SpamDyke altogether (although I don't recommend it)... there are multiple settings you could use, such as
ip-in-rdns-keyword-whiteli
Which could be used, for example, to whitelist people whose rDNS entry contained a string (like verizon.net -- since Verizon won't give DSL customers -- even business DSL customers -- an rDNS entry).
There are MANY more entries than I can possibly list here... try searching the SpamDyke documentation for rdns at
http://www.spamdyke.org/do
Good Luck!
Dan
IT4SOHO
Business Accounts
Answer for Membership
by: it4sohoPosted on 2009-06-24 at 07:10:58ID: 24701253
Sounds like you want to whitelist the SENDER, not the IP address of the server...
Here's the documentation for SpamDyke (an awesome product, IMHO)
http://www.spamdyke.org/do
This should help!
BTW: The other error messages indicate something may be wrong with your SpamAssassin configuration (the notes about /usr/local/bin/spamd)... in particular, SpamAssassin is written in Perl, and it apparently doesn't like lines 2103 & 2108 very much.
I suggest re-installing the latest SpamAssassin (http://spamassassin.apach
I hope this helps!
Dan
IT4SOHO