all emails being rejected

H

hostu

Verified User
Joined
Jun 17, 2004
Messages
73
this is after update to latest da ver yesterday

another update,,, this is weird,,, maybe---- restarting exim with the org exim.conf all seems to work well, then change exim.conf back to the spamblocker 4 exim.conf - then the original all mail blocked as noted below this update, but just now caught this is the mail logs with spamblocker 4 exim.conf
---

2011-03-21 14:27:02 H=jbmc-software.com [216.194.67.119] sender verify fail for <[email protected]>: Unrouteable address
2011-03-21 14:27:02 H=jbmc-software.com [216.194.67.119] F=<[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-21 14:27:02 H=jbmc-software.com [216.194.67.119] incomplete transaction (QUIT) from <[email protected]>
2011-03-21 14:27:23 failed to expand condition "${perl{check_limits}}" for lookuphost router: You (unknown) have reach your daily email limit of 300 emails

---

? why is [email protected] even in the logs, why are they sending me an email, and i was under the impression that the 300 limit in /virtual/limit was outgoing ? chuckr has sent no more than 5 emails in the last 24 hrs, lots of spam incoming -- this limit is or is not for outgoing only ?

confused as usual
-------------------------------------------------------------------------------------------------



please help

had spamblocker 4 installed recently all worked well

did an update to da to 1.38.0 and now this morning all emails to the server are rejected,,, checked hostued domains at mxtools.com no black list etc,,, var/log/exim/reject log just shows all emails as rejected

just notice this in the log Sender verify failed on a lot of good emails like ebay.com and so on, what/ where should i temp change setting maybe to get things going till i can see the whole picture, any questions etc. will be answered best i can,, this is a little urgent so your help is appreciated,
chuck

update: this makes no sense to me, but iam a nube right, anyway this was happening on each server that i had upgraded yesterday, some on totally different networks and in two different countries, then just like "magic" they started working again,, how is this possible, is there some checkin to DA or ? guess if i knew it would be "oh that is smiple" :) note: forgot i switched back to the org exim.conf


seems i have it all working now , thanks to all
 
Last edited:
Have you tried turning off sender verify in SpamBlocker exim.conf file for DirectAdmin, Version 4?

It's at EDIT#38.

Jeff
 
Hello,

This is related to this:
http://www.directadmin.com/forum/showthread.php?t=38574&highlight=exim.pl+unknown

The "unknown" limits have always been there in previous DA versions. Only with the new version of DA is it telling you that the unknown limit is being hit. It's just referring to system messages/bounces.

If you want to allow unlimited bounces to be sent, use this:
Code: 
echo 0 > /etc/virtual/limit_unknown
which assumes you've updated to the latest exim.pl to support the per-user limits, as described here (middle part).

John
 
Jeff, i tried that, but emails quit being processed in some manner when using sb4 exim.conf but switching back to the ver that came when i installed da it begins to work again... seems sb4 works for a short period then no mail at all, put the org exim in place and restart all is fine, this as mentioned started with latest update to da-- using centos 5 exim.pl ver8,, i would realy like to get things working with sb4 again as it worked well before the update, do you or anyone else have any idea or areas i should look at to narrow this down, thanks a bunch and i do like strawberries too :D

current (working) exim.conf

# SpamBlocker.exim.conf.2.1.1-release #
# 05-Jun-2007 #
# Runtime configuration file for DirectAdmin/Exim 4.24 and above #
# Requires exim.pl dated 20-Apr-2007 17:09 or later #







jlasman said:
Have you tried turning off sender verify in SpamBlocker exim.conf file for DirectAdmin, Version 4?

It's at EDIT#38.

Jeff
Click to expand...
 
Last edited:
Hello,

If you're referring to the "Unrouteable address" error, see this guide:
http://help.directadmin.com/item.php?id=67

Once you hit your limit (eg: 300 emails), all outbound deliveries will get that error, as the method for blocking once the limit is reached is to prevent the lookup for working, hence the error. Increase the limit if it's not high enough.

John
 
@John,

Does your latest exim.pl file require any changes in exim.conf for the limit feature to work?

Jeff
 
No. Only if the exim.conf is very very old would it need updating.
And in that case, the features wouldn't get used.. but it wouldn't break deliveries (I think).

John
 
still problems with exim

what iam trying to say is that email was working fine and i was using spamblocker 4 . after updating to the latest da ver no incoming mails were being accepted for all domains. change back to the default exim.conf and emails start flowing again. switched back and fort between sb4 exim and da exim same results. with the sb4 exim and reset the emails stop being received after 30 minutes or so....

john
now to your post.. about the 300 limit, if a particular user reaches the 300 limit do all users cease to be able to send, this is not how it looks to be working, i do get the emails that notify me if a users reaches this limit, so i think it is all works as it should, its just the diff exim.con that are giving me a fit,...but the only thing doesn't is when iam eating- so goes life :D


i think i will set it back to th sb4 conf and tail the exim main and reject logs to see what i can see, if something shows unusual and if i knew what that might be i will post... thanks for even viewing by crazy odyssey :)

some log results --- after switching back to the sb4 exim.conf

from exim mainlog
2011-03-27 19:19:25 cwd=/ 5 args: /usr/sbin/exim -bd -q15m -oP /var/run/exim.pid
2011-03-27 19:19:25 exim 4.72 daemon started: pid=20178, -q15m, listening for SMTP on port 587 (IPv4)
2011-03-27 19:19:25 cwd=/var/spool/exim 2 args: /usr/sbin/exim -q

2011-03-27 19:21:45 cwd=/etc/csf 4 args: /usr/sbin/sendmail -f root -t
2011-03-27 19:21:45 1Q40DJ-0005H2-2q <= [email protected] U=root P=local S=1220 T="lfd on srv60.host-u.com: blocked 84.204.56.234 (RU/Russian Federation/-)" from <[email protected]> for root
2011-03-27 19:21:45 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1Q40DJ-0005H2-2q
2011-03-27 19:21:45 1Q40DJ-0005H2-2q User 0 set for local_delivery transport is on the never_users list
2011-03-27 19:21:45 1Q40DJ-0005H2-2q == [email protected] R=localuser T=local_delivery defer (-29): User 0 set for local_delivery transport is on the never_users list
2011-03-27 19:21:45 1Q40DJ-0005H2-2q ** [email protected]: retry timeout exceeded
2011-03-27 19:21:45 cwd=/var/spool/exim 7 args: /usr/sbin/exim -t -oem -oi -f <> -E1Q40DJ-0005H2-2q
2011-03-27 19:21:45 1Q40DJ-0005H4-3c <= <> R=1Q40DJ-0005H2-2q U=mail P=local S=2041 T="Mail delivery failed: returning message to sender" from <> for [email protected]
2011-03-27 19:21:45 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1Q40DJ-0005H4-3c
2011-03-27 19:21:45 1Q40DJ-0005H4-3c User 0 set for local_delivery transport is on the never_users list
2011-03-27 19:21:45 1Q40DJ-0005H4-3c == [email protected] R=localuser T=local_delivery defer (-29): User 0 set for local_delivery transport is on the never_users list
2011-03-27 19:21:45 1Q40DJ-0005H4-3c ** [email protected]: retry timeout exceeded
2011-03-27 19:21:45 1Q40DJ-0005H4-3c [email protected]: error ignored
2011-03-27 19:21:45 1Q40DJ-0005H2-2q Completed
2011-03-27 19:21:45 1Q40DJ-0005H4-3c Completed

can send

2011-03-27 19:28:00 1Q40JL-0005Jv-Uq <= [email protected] H=localhost (www.hostu.org) [127.0.0.1] P=esmtpa A=login:[email protected] S=895 [email protected] T="exin sb4 test" from <[email protected]> for [email protected]
2011-03-27 19:28:00 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1Q40JL-0005Jv-Uq
2011-03-27 19:28:02 1Q40JL-0005Jv-Uq => [email protected] F=<[email protected]> R=lookuphost T=remote_smtp S=928 H=gmail-smtp-in.l.google.com [74.125.91.27] X=TLSv1:RC4-SHA:128 C="250 2.0.0 OK 1301272082 g24si7333073qck.156"
2011-03-27 19:28:02 1Q40JL-0005Jv-Uq Completed


can send from webmail local but the above was the last and only entry in the mainlog after going back to the sb4 exim.conf...


this is what if have for sb4 test


#EDIT#41:
deny message = Email blocked by $dnslist_domain
hosts = !+relay_hosts
domains = +use_rbl_domains
domains = !+skip_rbl_domains
!authenticated = *
dnslists = \
b.barracudacentral.org : \
hostkarma.junkemailfilter.com=127.0.0.2

# dnslists = \
# cbl.abuseat.org : \
# dnsbl.njabl.org : \
# bl.spamcop.net : \
# dnsbl.ahbl.org : \
# combined.rbl.msrbl.net : \
# b.barracudacentral.org : \
# zen.spamhaus.org
# hostkarma.junkemailfilter.com=127.0.0.2
 
Last edited:
Hello,

The 300 limit only applies to the DA user and all of his email accounts.

However, the error you've posted is with regards to the "unknown" user, which tends to be for bounces, or unknown senders. If our forum sends you an email, but the sender-verify is doing an outbound check, that sender check may be triggered as a delivery, so each sender-verify would be "sent" from an unknown address ("sent" in this context is the verify, but not an actual delivery).

Have you done this yet?
Code: 
echo 0 > /etc/virtual/limit_unknown
Related:
http://help.directadmin.com/item.php?id=360

Note the "unknown" case has always been there, however it's only recently been noticed since DA alerts people of the limits it create. We're still investigating all of the cases that trigger the unknown message, but either way, using the above to allow those emails through should work (the above code only works with the new exim.pl. Old exim.pl files won't with that limit_unknown file).

John
 
thanks john

john thanks for your answer to that, but this is no longer the problem, perhaps i should have started a new post, the current and most pressing is in the inability for any customer to receive email when using spamblocker 4 with the latest update to directadmin, the limit thing is understood and working as it should...
many thanks again for your help...




DirectAdmin Support said:
Hello,

The 300 limit only applies to the DA user and all of his email accounts.

However, the error you've posted is with regards to the "unknown" user, which tends to be for bounces, or unknown senders. If our forum sends you an email, but the sender-verify is doing an outbound check, that sender check may be triggered as a delivery, so each sender-verify would be "sent" from an unknown address ("sent" in this context is the verify, but not an actual delivery).

Have you done this yet?
Code: 
echo 0 > /etc/virtual/limit_unknown
Related:
http://help.directadmin.com/item.php?id=360

Note the "unknown" case has always been there, however it's only recently been noticed since DA alerts people of the limits it create. We're still investigating all of the cases that trigger the unknown message, but either way, using the above to allow those emails through should work (the above code only works with the new exim.pl. Old exim.pl files won't with that limit_unknown file).

John
Click to expand...
 
Hello,

1) The "sender verify" is part of receiving emails.
I believe that's something that's enabled by default with sb4, which isn't with our default install.

Just for testing, find this code:
Code: 
require verify = sender
and comment it out by adding a # character at the front, then restart DA.

See if that helps. The "unknown" limit may be related to the sender verify code for *incoming* emails. (possible exim uses the lookuphost code for a sender verify)

Probably not realted, I believe sb4 comes by default for Maildir, but ensure that it's set anyway by typing
Code: 
grep Maildir /etc/exim.conf
you should get 2 lines of output with the word Maildir in it. The sb2 exim.conf that we provide, by default, does not have Maildir enabled (which dovecot requires), hence there is a re-patch requirement for all updates of the exim.conf from our system. I don't think the patch would be requires with sb4.. but check to ensure it's there anyway.

Beyond that, check the logs:
/var/log/exim/mainlog
/var/log/exim/paniclog
/var/log/exim/rejectlog

to see why it's not working.


2) If the above is totally unrelated (you may be a few steps ahead of me), try disabling the use_rbl_domains file (bottom part of guide), as I believe that's one big feature that sb4 has (which is the whole point of using it). That will let us know if it's one of the RBL systems blocking the IP (it might also show up in the rejectlog, so check there too). Turn it back on (if it was one) once your testing is done.

3) You might try commenting out both sections of "EDIT 41" and "EDIT 42", also to see if it's rbl related. (restart exim after editing the exim.conf).

If it is RBL related it might not be an issue with the exim.conf, perse, but rather the sending IP being blacklisted in the RBLs. If you're sending to your own server from a client (eg: outlook) set your SMTP settings to deliver to your server on port 587 instead of 25, which will bypass the RBL checks (many entire ISP ranges are blocked in RBLs, as clients are not supposed to be sending email from their machines, but rather via a designated mail server)

John
 
working ???

# require verify = sender done


once again john you are going beyond to help, thank you, thank you, and same to jeff and all you guys and gals are great on here... opps don't go over board chuck :D

i just kina by mistake and kind was heading that way, while checking out johns suggestions, had things set to sb4 and the exim.pl ver 8 - not working, stops all mail incoming - i switched back to the exim.pl that jeff has with sb4 and things started to work ie: email flowing and the blocking is working per the settings in sb4, not sure if the limit will work yet to soon to see, i thing the v8 pl file is need here... so here is what i got so far

directadmin ->exim.conf ( exim.pl v8 ) does work - and limits work

spamblocker 4 ->exim.conf ( exim.pl sb4 ) does work - limits unknown

spamblocker 4 ->exim.conf ( exim.pl v8 ) does not work - all email for all customers is stopped for incoming but users can send..

comparing the two exim.pl files the biggest difference between the two is here - sub check_limits -, and i too smart to know what iam doing with the code so " i know nothing " :)

having fun now !!!


DirectAdmin Support said:
Hello,

1) The "sender verify" is part of receiving emails.
I believe that's something that's enabled by default with sb4, which isn't with our default install.

Just for testing, find this code:
Code: 
require verify = sender
and comment it out by adding a # character at the front, then restart DA.

See if that helps. The "unknown" limit may be related to the sender verify code for *incoming* emails. (possible exim uses the lookuphost code for a sender verify)

Probably not realted, I believe sb4 comes by default for Maildir, but ensure that it's set anyway by typing
Code: 
grep Maildir /etc/exim.conf
you should get 2 lines of output with the word Maildir in it. The sb2 exim.conf that we provide, by default, does not have Maildir enabled (which dovecot requires), hence there is a re-patch requirement for all updates of the exim.conf from our system. I don't think the patch would be requires with sb4.. but check to ensure it's there anyway.

Beyond that, check the logs:
/var/log/exim/mainlog
/var/log/exim/paniclog
/var/log/exim/rejectlog

to see why it's not working.


2) If the above is totally unrelated (you may be a few steps ahead of me), try disabling the use_rbl_domains file (bottom part of guide), as I believe that's one big feature that sb4 has (which is the whole point of using it). That will let us know if it's one of the RBL systems blocking the IP (it might also show up in the rejectlog, so check there too). Turn it back on (if it was one) once your testing is done.

3) You might try commenting out both sections of "EDIT 41" and "EDIT 42", also to see if it's rbl related. (restart exim after editing the exim.conf).

If it is RBL related it might not be an issue with the exim.conf, perse, but rather the sending IP being blacklisted in the RBLs. If you're sending to your own server from a client (eg: outlook) set your SMTP settings to deliver to your server on port 587 instead of 25, which will bypass the RBL checks (many entire ISP ranges are blocked in RBLs, as clients are not supposed to be sending email from their machines, but rather via a designated mail server)

John
Click to expand...
 
Last edited:
i had trouble with sender verify aswell BUT just with exim.pl v6 from directadmin with SB4

Atm im using SB4 exim.conf + exim.pl v8 from directadmin without any problem.

For what ive learn should be a dns problem, i would suggest you to use exim.pl v8 + sb4 and comment the line

Code: 
require verify = sender

untille there will be a solution.

Some ppl suggested me to keep that line disabled cause is not much usefull as i think.

Regards
 
thanks, that is the settings that are not working now, i saw you post elsewhere,, mine did not work with v6 pl and sb4, so went back to default conf then loaded the v8 pl and it seemed to work for a while then quit, now it just starts and no incoming at all, an the "require verify = sender" is commented out... iam on line now but not limit monitoring but sb4 is working using the .pl supplied with/by sb4...
thanks again


SeLLeRoNe said:
i had trouble with sender verify aswell BUT just with exim.pl v6 from directadmin with SB4

Atm im using SB4 exim.conf + exim.pl v8 from directadmin without any problem.

For what ive learn should be a dns problem, i would suggest you to use exim.pl v8 + sb4 and comment the line

Code: 
require verify = sender

untille there will be a solution.

Some ppl suggested me to keep that line disabled cause is not much usefull as i think.

Regards
Click to expand...
 
I'm not sure where you're getting those version numbers from. I'm going to stop maintaining my own exim.pl, and rely on DirectAdmin keeping it updated. Can someone tell me, does my latest v4 file work with the latest (version 8?) exim.pl from DirectAdmin? If so, please email me as well as replying here and I can do it today.

Thanks.

Jeff
 
The exim.pl version 8 is from directadmin website.

the version is in the file

Code: 
>cat /etc/exim.pl | grep VERSION
#VERSION=8

and this is the first 2 line of mine exim.conf

Code: 
# SpamBlockerTechnology4.0-exim.conf.txt
# SpamBlockerTechnology* powered exim.conf, Version 4.0

and ive sender verify enabled:

Code: 
>cat /etc/exim.conf | grep "require verify"
  require verify = sender

And is working perfectly.

I had problem with directadmin exim.pl version 6, but with version 8 is working perfectly.

Regards
 
iam sorry if my little chart of what works and does not was not clear enough, i will try to clarify

sb4 exim.conf refers to the spamblocker ver 4 exim.conf file

sb4 exim.pl refers to the exim.pl downloaded from nobaloney.net

directadmin exim.conf refers to the exim.conf that was installed when directadmin was first installed on server

exim.pl v6 refers to the earlier file from DA i tried with the limit feature
exim.pl v8 refers to the current version from DA

i know splamblocker ver 4 and the exim.pl v8 has been reported to work for others and thats great and iam glad it does for them..

spamblocker4 worked great from me also until the exim.pl versions 6&8

spamblocker4 only works for me when used with the exim.pl downloaded from nobaloney.net

the test above has been the extent so far, i'am sure i will get it working at some point using the sb4 exim.conf and v8 exim.pl

again thank you all who have taken the painful time to sift this non-tech post to figure out what i was trying to say,, " old minds like mine may think young, but often react old just the same " surely i didn't just say that



jlasman said:
I'm not sure where you're getting those version numbers from. I'm going to stop maintaining my own exim.pl, and rely on DirectAdmin keeping it updated. Can someone tell me, does my latest v4 file work with the latest (version 8?) exim.pl from DirectAdmin? If so, please email me as well as replying here and I can do it today.

Thanks.

Jeff
Click to expand...
 
Last edited:
Today ive downloaded latest exim.conf sb4 (dec 2010 and i had pct 2010).

Customized as mine and restarted.

Noticed in logs some verify fail:

Code: 
2011-03-29 11:28:06 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-29 11:28:06 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-29 11:28:06 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-29 11:28:06 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-29 11:28:06 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-29 11:28:07 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-29 11:28:07 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-29 11:28:07 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed
2011-03-29 11:28:07 H=088156011099.olsztyn.vectranet.pl [88.156.11.99] F=<CarlaLó[email protected]> rejected RCPT <[email protected]>: Sender verify failed

But those seems to be totally correct checking host and ip

Other email are working correctly, so maybe the rDNS for domains your server is rejecting isnt correct or your server cant check it correctly, is that possible?

Regards
 
Checking your first post that error was cause riceving mail from directadmin.com, checked host and ip and are correct reversed, so, your system for some reason is unable to resolve the ip to host and vice-verse (well maybe just ip to host).
 
Is this the actual sender, or is it changed for the forum?
Code: 
F=<CarlaLó[email protected]>
... because it doesn't resolve, doesn't have an MX record... Hence it can't be verified. It doesn't matter which IP the email comes from. With the sender verify enabled, exim goes through all the delivery hoops in order to check the address.. MX lookup, connects to port 25, and tests the recipient.

John
 
You must log in or register to reply here.
Back
Top