Not receiving email - R=domain_filter - Yet I have no filters

americanintel

Verified User
Joined
Mar 1, 2004
Messages
133
Location
Granbury, TX
I have noticed far too many email being blocked lately and was seemingly getting worse....now I can't receive email at all.

The R=domain_filter is the only tell tale.

I have NO filters in place via DA, no sex filters, no domains, no keywords...nothing. I have nothing in my /etc/virtual blacklist or whitelist files. Yet I still get this filter error...doesn't make sense.

Domain has been changed to mydomain.com and my gmail address altered.

I've tried sending from other accounts and TO other accounts on the server... nada.

Here's an excerpt from my /var/log/exim/mainlog

2010-04-25 16:19:50 1O69Ew-00011U-8c <= [email protected] U=mail P=spam-scanned S=7974 id=l2p416b96571004251419gf83cefb6r625197b5b50b9b44@mail.gmail.com T="Fwd: New Private Message at Message Boards" from <[email protected]> for [email protected]
2010-04-25 16:19:50 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1O69Ew-00011U-8c
2010-04-25 16:19:50 1O69Ew-00011U-8c => discarded <[email protected]> R=domain_filter
2010-04-25 16:19:50 1O69Ew-00011U-8c Completed
2010-04-25 16:19:50 1O69Ev-00011Q-HD => brad <[email protected]> F=<[email protected]> R=spamcheck_director T=spamcheck S=7845
2010-04-25 16:19:50 1O69Ev-00011Q-HD Completed


-------------
And my filter file in /etc/virtual/mydomain.com file:

# Exim Filter

# created by DirectAdmin, version 1.35.1
# Do not modify this file as any changes will be
# overwritten when the user makes a change.
# (data is only written to this file, not read)

if error_message then finish endif







if
$h_X-Spam-Status: contains "Yes,"
then
seen finish
endif



#end filter

And filter.conf for the same domain:

[root@server mydomain.com]# cat filter.conf
action=action=drop
adult=OFF
high_score=15
high_score_block=no
where=delete
[root@server mydomain.com]#


I've checked everything I know to check but am drawing a blank.

I even deleted the filter file for this domain and let DA recreate it... nothing.
 
Last edited:
Updated to RC 3.2.5 and still the same thing. This is driving me crazy as I have no filters but it's picking up on something somewhere.

Jeff this is one I may need your help with....

Oh.. .and if you see this, I'm getting the following 'error' in /exim/mainlog but couldn't find anything in the exim.conf that spells out what I need to do about that file.

2010-04-25 21:19:12 unknown named host list "+relay_hosts"
 
Now I'm cookin'....

Checked a filter file for a domain that I had added after I moved to a new server and it is different:
# Exim Filter

# created by DirectAdmin, version 1.35.1
# Do not modify this file as any changes will be
# overwritten when the user makes a change.
# (data is only written to this file, not read)

if error_message then finish endif



finish






#end filter

Copied that file over and chowned it and insto presto... we have email.

So that go me thinking...which hurt...what does the filter.conf look like in the newer domain?

Guess what? Empty, file is there but it's blank.

So, I believe I'm going to empty the offending domain's filter.conf files and see how that works and use the newer domain's filter file and go from there.

Any thoughts?
 
Deleted the filter and filter.conf files in several of my older domains and then copied over the conf file from a working domain, logged in to DA and triggered the Spamassassin update by saving the config.

Then I started getting emails with super high scores:

Content analysis details: (6.6 points, 4.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.4 DNS_FROM_OPENWHOIS RBL: Envelope sender listed in bl.open-whois.org.
3.4 FH_DATE_PAST_20XX The date is grossly in the future.
0.0 HTML_MESSAGE BODY: HTML included in message
0.8 AWL AWL: From: address is in the auto white-list

So after doing a bit of reading I figured I needed to update Spamassassin:

So.. sa-update ...ooops problem there too so I did a:

perl -MCPAN -e 'install Archive::Tar'

and then:

sa-update && /sbin/service exim restart

and that seems to have fixed things as my scores are correct and anything over my score threshold (some I have set at 4.0) are deleted and not delivered.

Seems that updating to 3.2.5 requires you having an up to date SA install.

All seems happy now except for the +relay_hosts thing going on in the mainlog file. Otherwise I think everything is ok now.
 
Seems that updating to 3.2.5 requires you having an up to date SA install.
I won't argue with that, since I now have an up-to-date spamassassin installation on my testbed server.

Anyone else seeing a problem with the latest SpamBlocker Technology version 3.2.5 exim.conf file?
All seems happy now except for the +relay_hosts thing going on in the mainlog file. Otherwise I think everything is ok now.
Someone may not be reading the instructions for using the SpamBlocker Technology version 3.2.5 exim.conf file.

Search your installed exim.conf file for hostlist relay_hosts and you should find two lines. One of them must be uncommented, and then restart exim.

Jeff
 
Someone may not be reading the instructions for using the SpamBlocker Technology version 3.2.5 exim.conf file.

Search your installed exim.conf file for hostlist relay_hosts and you should find two lines. One of them must be uncommented, and then restart exim.

Jeff

Actually, I read the thing so many times that I can almost quote it to you but after a long day clearing trees and brush my brain was mush and I was literally searching for +relay_hosts instead of relay_hosts. :D However you are quite correct, I did skip that section for some reason.

Thank you for your enlightenment!
 
Last edited:
I just wanted to say thanks for the above process in getting sa updated and working properly.... I too was having the same bug with sa on the 20XX date issue.

Here is what I needed to do in my case since it was timing out with lwp.

export FTP_PASSIVE=1
perl -MCPAN -e 'install Archive::Tar'
sa-update && /sbin/service exim restart

then
export FTP_PASSIVE=0

to return to normal.
 
Back
Top