TROUBLE in check_mail

Amavis issues go here

Moderators: Admins, Forum Moderator

TROUBLE in check_mail

Postby ldejager » Mon Mar 20, 2006 3:55 pm

Hi,

I followed the FC4 guide on setting up Postfix/amavis etc on a FC3 box and it's working fine, however due to the amount of email being passed through the machine I have decided to upgrade the hardware to a dual cpu box with 1GB of RAM.

I followed the same guide, did exactly as I di the previous time and for some reason I get the following errors;

--

Mar 20 19:23:12 fzscan postfix/smtpd[5735]: connect from mx1.domain.com[1.2.3.4]
Mar 20 19:23:14 fzscan postfix/smtpd[5735]: warning: libero.it.dun.dnsrbl.net: RBL lookup error: Host or domain name not found. Name service error for name=libero.it.dun.dnsrbl.net type=A: Host not found, try again
Mar 20 19:23:14 fzscan postfix/smtpd[5735]: 04D187781E8: client=mx1.domain.com[1.2.3.4]
Mar 20 19:23:14 fzscan postfix/cleanup[5730]: 04D187781E8: message-id=<rtf8bW.squirrel@216.180.225.170>
Mar 20 19:23:14 fzscan postfix/smtpd[5735]: disconnect from mx1.domain.com[1.2.3.4]
Mar 20 19:23:14 fzscan postfix/qmgr[5644]: 04D187781E8: from=<dtrotter@libero.it>, size=1409, nrcpt=1 (queue active)
Mar 20 19:23:14 fzscan amavis[5741]: (05707-01) run_command: child process [5741]: Error closing main::stdin: Bad file descriptor at /usr/sbin/amavisd line 1872.\n
Mar 20 19:23:14 fzscan amavis[5707]: (05707-01) TROUBLE in check_mail: parts_decode_ext FAILED: parsing file(1) results - missing last 1 results at (eval 41) line 154.
Mar 20 19:23:14 fzscan amavis[5707]: (05707-01) PRESERVING EVIDENCE in /var/amavis/tmp/amavis-20060320T192314-05707
Mar 20 19:23:14 fzscan postfix/smtp[5731]: 04D187781E8: to=<fz-justiceakanbi@domain.com>, relay=127.0.0.1[127.0.0.1], delay=2, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=05707-01, parts_decode_ext FAILED: parsing file(1) results - missing last 1 results at (eval 41) line 154. (in reply to end of DATA command))

--

I've searched google for the errors and saw a thread that suggested running the file(1) command as the user (who normally calls it, amavis) and check the exit code.

I've done that and the exit code is 0, which to means it finished sucessfully. I checked the working server's file(1) version and it's the same version as on the new machine.

Both machines were updated prior to following the guide (yum update)

Does anyone know what could be causing these errors?

Thanks in advance!
ldejager
 
Posts: 3
Joined: Mon Mar 20, 2006 3:45 pm

Postby Netopia » Mon Mar 20, 2006 4:11 pm

In your /etc/postfix/main.cf file, remove

reject dun.dnsrbl.net

It no longer exists and is causing your box to throw errors. I had the same problem.

Joe
I love admins who remove 30 second delays for ID10Ts like me who make lots of speeling eerors.

Thanks Dave!
User avatar
Netopia
Moderator
 
Posts: 412
Joined: Mon Oct 10, 2005 5:05 pm
Location: Maryland, USA

Postby mr88talent » Mon Mar 20, 2006 5:30 pm

There have been many recent posts on the amavis user lists regarding this. It is due to the use of Net::Server 0.91 with amavisd-new versions 2.3.3 or earlier. The fix is to downgrade to Net::Server 0.90. You can also use the current pre-release of amavisd-new 2.4.0 if you like.

http://www.ijs.si/software/amavisd/amav ... re7.tar.gz

or for you convenience, you can grab a copy of 0.90 from me:

Code: Select all
cd /usr/local/src
wget http://www.xmission.com/~jmcrc/Net-Server-0.90.tar.gz
tar xzvf Net-Server-0.90.tar.gz
cd Net-Server-0.90
perl Makefile.PL
make && make test && make install

It should simply install over the top of 0.91
User avatar
mr88talent
Moderator
 
Posts: 1653
Joined: Tue Mar 08, 2005 4:19 pm
Location: Salt Lake City

Postby ldejager » Mon Mar 20, 2006 5:46 pm

Hi,

Thanks for the replies, I finally got an answer by reading through amavis.user lists and it was necesary to downgrade to Net::Server 0.90 from 0.91.

I have removed the dun.dnsrbl.net from postfix main.cf but I am still getting loads of lookup errors;

Mar 20 21:35:16 fzscan postfix/smtpd[9524]: warning: 1.0.0.127.sbl.spamhaus.org: RBL lookup error: Host or domain name not found. Name service error for name=1.0.0.127.sbl.spamhaus.org type=A: Host not found, try again
Mar 20 21:35:16 fzscan postfix/smtpd[9524]: warning: 1.0.0.127.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=1.0.0.127.relays.ordb.org type=A: Host not found, try again
Mar 20 21:35:16 fzscan postfix/smtpd[9524]: warning: 1.0.0.127.opm.blitzed.org: RBL lookup error: Host or domain name not found. Name service error for name=1.0.0.127.opm.blitzed.org type=A: Host not found, try again
Mar 20 21:35:16 fzscan postfix/smtpd[9524]: warning: 1.0.0.127.list.dsbl.org: RBL lookup error: Host or domain name not found. Name service error for name=1.0.0.127.list.dsbl.org type=A: Host not found, try again
Mar 20 21:35:16 fzscan postfix/smtpd[9524]: warning: 1.0.0.127.cbl.abuseat.org: RBL lookup error: Host or domain name not found. Name service error for name=1.0.0.127.cbl.abuseat.org type=A: Host not found, try again
Mar 20 21:35:16 fzscan postfix/smtpd[9524]: warning: 1.0.0.127.dul.dnsbl.sorbs.net: RBL lookup error: Host or domain name not found. Name service error for name=1.0.0.127.dul.dnsbl.sorbs.net type=A: Host not found, try again

I double checked resolv.conf and did a dig on one of the domains listed above (without the 1.0.0.127) and it works... anyone know why the 1.0.0.27 is added?

Thanks again for the replies, helped a lot!
ldejager
 
Posts: 3
Joined: Mon Mar 20, 2006 3:45 pm

Postby Netopia » Mon Mar 20, 2006 5:51 pm

I don't know about the other stuff, but 1.0.0.127 is just your reversed localhost address (127.0.0.1)

Joe
I love admins who remove 30 second delays for ID10Ts like me who make lots of speeling eerors.

Thanks Dave!
User avatar
Netopia
Moderator
 
Posts: 412
Joined: Mon Oct 10, 2005 5:05 pm
Location: Maryland, USA

Postby mr88talent » Mon Mar 20, 2006 6:04 pm

Yet it appears Postfix thinks your DNS is broken. It may be a chroot problem? Have you run the LINUX2 script?
User avatar
mr88talent
Moderator
 
Posts: 1653
Joined: Tue Mar 08, 2005 4:19 pm
Location: Salt Lake City

Postby ldejager » Tue Mar 21, 2006 7:09 am

Hi,

Postfix is not running chrooted, maybe a reboot would solve the issue... haven't rebooted the server since I started working on it and I did make a few networking changes.

Thanks
ldejager
 
Posts: 3
Joined: Mon Mar 20, 2006 3:45 pm


Return to Amavisd-new

Who is online

Users browsing this forum: No registered users and 0 guests

cron