Users cant send email / relayhosts not updating

[nyjimbo]

Since upgrading to 9.40-e13 (freebsd) users who send mail through our smtp server are complaining they get :

Task 'mail.xxxxxxxxxx.com - Sending' reported error (0x800CCC65) : 'Your
outgoing (SMTP) e-mail server has reported an internal error. If you continue
to receive this message, contact your server administrator or Internet service
provider (ISP). The server responded: 503 valid RCPT command must precede
DATA'"

This is happening for many domains on the server that worked fine before the upgrade.

We tried to run /exim4 to update but that didnt help. I noticed that the file "relayhosts" in /etc has not updated since last nights upgrade.

Anyone know what could fix this ????

[AlexF]

Same issue on one of our FreeBSD v5.1 box running cPanel 9.3.0 C56. Any suggestions?

[nyjimbo]

Originally posted by AlexF
Same issue on one of our FreeBSD v5.1 box running cPanel 9.3.0 C56. Any suggestions?

We were running 9.3.0 C56 flawlessly until this update to 9.4 e-13 so I dont think its the whole update, rather something is being pulled in with either cppop or exim or something mail related.

It could be anything, I tried to restore 'relayhosts' from a backup prior to the update but the permissions and info the same so its not that.

[AlexF]

It's funny because I have other users (domains) on this box that they have reported no problems.

I've also setup a temp. email address with their domain and it is working fine using outlook or outlook express. In addition, I mentioned the sysadmin to update the outlook settings to include 'My outgoing server (smtp) requires authentication' with 'Use same settings as my incoming mail server' (as I previously mentioned to them) and it seems to have worked on his console, but not others. Weird?!?!?

[SonServers]

Same thing for me here . . . After updating my FreeBSD server to 9.4.0-E13, some users are unable to send mail without turning on smtp authentication. So far that I know of, that has made it possible for everyone to send again but they are asking me "why the change?"

[nyjimbo]

Originally posted by SonServers
Same thing for me here . . . After updating my FreeBSD server to 9.4.0-E13, some users are unable to send mail without turning on smtp authentication. So far that I know of, that has made it possible for everyone to send again but they are asking me "why the change?"

Over the past hour or so we found that they have to turn on authentication and some have to make a change in their email user id.

I wish we could find out of this is a bug/fault in the server or if this is a "new feature".

[chirpy]

Check to make sure that antirelayd is running - this is the process that allows POP before SMTP and maintains /etc/relayhosts. If it isn't, you can start it with:
/etc/init.d/antirelayd

[AlexF]

Originally posted by chirpy
If it isn't, you can start it with:
/etc/init.d/antirelayd

Not listed in current running processes and can't run this command as it is not in etc. Advise?

[nyjimbo]

Originally posted by AlexF
Not listed in current running processes and can't run this command as it is not in etc. Advise?

I dont see the folder "/etc/init.d" however there is a perl script called "antirelayd" in /usr/sbin.

As a matter of fact I always see antirelayd running when I do a "ps ax" at the console but since the upgrade it has not started.

I rebooted the machine several times in the past day but antirelayd never starts (or does start but fails and I dont know about it).

[chirpy]

Well, you could try running antirelayd interactively to see if it fails with an error by just typing in:

/usr/sbin/antirelayd

Sorry about the startup location, I'm Linux-centric and don't know much about the BSD directory structures.

Another way to start it in the background would be (usually) to use:

/usr/sbin/antirelayd &


But don't do that the first time as you won't see any errors from it.

[nyjimbo]

Originally posted by chirpy
Well, you could try running antirelayd interactively to see if it fails with an error by just typing in:

/usr/sbin/antirelayd

Sorry about the startup location, I'm Linux-centric and don't know much about the BSD directory structures.

Another way to start it in the background would be (usually) to use:

/usr/sbin/antirelayd &


But don't do that the first time as you won't see any errors from it.

I just did that and it fired up. I didnt want to as I didnt know if it required any special syntax or had to be started at some point.

Now that its running I see "relayhosts" updated almost right away. My only question would be why is it not starting up at boot time. Even after 4 or 5 boots there was no antirelayd running.

This is freebsd, in case anyone is seeing the same thing on their bsd box.

[mnett]

Same problem here... And it is some problems with sending mail trough php script

[sjackson909]

Originally posted by nyjimbo
I dont see the folder "/etc/init.d" however there is a perl script called "antirelayd" in /usr/sbin.

As a matter of fact I always see antirelayd running when I do a "ps ax" at the console but since the upgrade it has not started.

I rebooted the machine several times in the past day but antirelayd never starts (or does start but fails and I dont know about it).

Try /usr/local/etc/rc.d/039antirelayd. Most services are start from that dir, included apache and exim. Just do a /usr/local/etc/rc.d/039antirelayd stop and then do a start.

-Seth

[mickalo]

Most linux system simple do service antirelayd restart should do it

Mickalo

[sjackson909]

Originally posted by sjackson909
Try /usr/local/etc/rc.d/039antirelayd. Most services are start from that dir, included apache and exim. Just do a /usr/local/etc/rc.d/039antirelayd stop and then do a start.

-Seth

I guess I should have said that was for FreeBSD only.