503 valid RCPT command must precede DATA

jason007

Member
Feb 15, 2003
5
0
151
Same thing on one of my servers

CentOS 4.3 with WHM 10.8.0 cPanel 10.8.1-S114

Seems to do it every Saturday night/Sunday morning.

Already had a ticket in with cPanel and they didn't really have anything useful to say.
 

t9clkclnr

Well-Known Member
Jun 11, 2004
254
0
166
Southern California
happens every sunday night for me

like clockwork. each sunday night this happens and all my emails bounce.

WHM 10.8.0 cPanel 10.8.1-S114
CentOS 4.2 i686 - WHM X v3.1.0
 

steve248

Member
Apr 11, 2003
10
0
151
steve248 said:
I just got this error and ran scripts/fixrelayd which foxed the problem for me.

Hmmm, well this did fix it for me but now it doesnt. The problem continued to reoccur every few days but was fixable using the fixrelayd method, however, this now does not work and I have had to instruct all users on the server to setup outgoing mail to require authentication.

This works but is a pain to say the least.

A solution would be very welcome! :)
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,437
31
473
Go on, have a guess
Have yo checked that fixrelayd is running and that POP requests are being logged in /var/log/maillog?

You do also have to be sure you check syslog.conf as I mentioned before - i.e. that it's not getting the duplicate line logging, or you will have problems.
 

jmcole

Active Member
Aug 17, 2004
25
0
151
if you are using courier instead of cppop I'd suggest forcing a reinstall with /scripts/courierup --force

this worked for one of our servers that was having this same issue tonight... /var/log/maillog was not logging pop3d connections and /etc/relayhosts was not being written to.

good luck!
 

jason007

Member
Feb 15, 2003
5
0
151
chirpy said:
Have yo checked that fixrelayd is running and that POP requests are being logged in /var/log/maillog?

You do also have to be sure you check syslog.conf as I mentioned before - i.e. that it's not getting the duplicate line logging, or you will have problems.


mail logs as of this morning after it did it's weekly failure

-rw------- 1 root root 0 Apr 16 04:02 maillog
-rw------- 1 root root 4736709 Apr 16 12:15 maillog.1
-rw------- 1 root root 5085416 Apr 9 13:41 maillog.2
-rw------- 1 root root 4951267 Apr 2 18:56 maillog.3
-rw------- 1 root root 5771162 Mar 26 16:33 maillog.4

nothing being written to maillog obviously

logrotate ran with other stuff in cron at 4AM

syslog.conf is fine

a simple restart of syslog fixed the problem as usual
 
Last edited: