SMTP not working for some accounts

sbrad

Well-Known Member
Aug 14, 2001
113
0
316
I have a few users (myself included) that aren\'t able to send mail through the server. I checked exim_mainlog, and see:
unexpected disconnection while reading SMTP command from xxx.xxx.xxx.xxx.

I manually added my ip to /etc/localrelayhosts, and it went right through. So it looks like, after mail is checked, that ip isn\'t getting added to the list. Any ideas?
 

sbrad

Well-Known Member
Aug 14, 2001
113
0
316
Hey thanks. I think that did the trick.
I had no idea it was required. I\'ve never had it turned on, and it\'s always worked ok. hmmm
 

feanor

Well-Known Member
Aug 13, 2001
836
0
316
It\'s not required.....
That is like the final saviour step when people can\'t relay, because it sends authentication when they make the actual SMTP connection (via port 25, outgoing, whatever)..... so it doesn\'t even matter if they\'ve logged in correctly via pop3 to the server.

In a perfect world, you don\'t need the SMTP auth, coz the people using the SMTP server are users that have already logged in via pop3 to get mail, and are added to that allow file as you stated.... sometimes things **** up, surprise surprise.

Did you run /scripts/mailperm also?


:D
 

sbrad

Well-Known Member
Aug 14, 2001
113
0
316
[quote:3e327163be] /scripts/mailperm[/quote:3e327163be]
Nopers. What does that do?
Nevermind. I\'ll just run it and trust the magic. ;)
 

feanor

Well-Known Member
Aug 13, 2001
836
0
316
It changes/verifies all mail-sensitive directories everywhere on the machine in question have the write permission bit settings and correct user/group ownership.

FUN for all.
 

sbrad

Well-Known Member
Aug 14, 2001
113
0
316
I ran mailperm, and it seems to have fixed everything, with ONE exception. I still have a user on a Mac that still can\'t send mail through the server. I\'ve even manually added him to /etc/relaydomains, but still no luck. He has the same problem with OLE 5 and Eudora 5.1.
 

WeinBar

Well-Known Member
Aug 13, 2001
79
0
306
It could very well be his ISP. A lot of ISPs will now block out access to port 25 (SMTP server) and require them to use their own mail server for sending.

TO test it, have them try to telnet to that port, i.e.

telnet theirdomainname.com 25

If they get the exim message, then they can use port 25 and it is not a server issue. If the connection is refused, then you know where the problem lies.
 

sbrad

Well-Known Member
Aug 14, 2001
113
0
316
Telnet\'s disabledon the server, and that\'s blocked via ssh.

I don\'t think that\'s the problem, because he was using mail.hisdomain.com with his previous hosting company.
 

WeinBar

Well-Known Member
Aug 13, 2001
79
0
306
Even though telnet is diabled on the server, you should be able to telnet into a different port, just to see if it is active. Even though it worked for his previous company, it may not work now as the ISP may have turned it off.
 

rpmws

Well-Known Member
Aug 14, 2001
1,822
8
318
back woods of NC, USA
[quote:d18283d65a]Telnet\'s disabledon the server, and that\'s blocked via ssh.

I don\'t think that\'s the problem, because he was using mail.hisdomain.com with his previous hosting company. [/quote:d18283d65a]

I have been through all this myself. All my hair is gone way before now so here is my 1c worth.

If SMTP works on that box at all this is more than likey what the problem is.

1.) Your user is on a screw ball ISP like Earthlink / Mindsprung. Telnet doesn\'t matter because you are simply asking them to talk to that port. Try it. If it sits there it\'s a firewall on that ISP. if they get a hello message frok Exim you are good to go. Also if it is a recent transfer make sure \"mail.theirdomain.com\" resolves (FROM THEIR COMPUTER) to your server. A simple \"ping mail.hisdomain.com\" will tell them at the command prompt.

2.) No IP in that \"ok\" file. Tell them to (check mail first) on that account. I have people all the time that have their OLE set to check every 10 hours and they sit there composing 10 emails to send to people and when they try to send they get errors. Then they just sit there and stare at the error. They never bother to check their mail manually .. they think that mail just magically comes in when it wants to.

So make sure they can get a \"hello\" from Exim using that Telnet command and if they can the SMTP auth that Nick suggested will work or just make sure they check mail often and always before they try to send.

Good luck :)
 

Craig

Well-Known Member
Aug 10, 2001
171
0
316
sbrad, been having the same problems on a server myself, amonst a whole load of others. *crys*

However, that stmp auth seemed to fix matters, just have never had to use that before.. weird =]

thanks

C.