I can't send emails from my server to an account on my server too using webmails

freshmint

Verified User
Joined
Oct 10, 2005
Messages
113
I have Squirrelmail and Roundcube installed on my server.

When I try to send an email using any of the webmails above to an account hosted on my server, it fails to send. I have tried sending from two accounts on the same domain and two accounts on different domains.

Examples:

[email protected] ---> [email protected]
[email protected] ---> [email protected]

Can anyone duplicate this behavior? Not sure if it's a bug on my part or not, but I didn't play with my exim or imap configurations.

Does anyone know how to fix it?
 
you might want to look at the log file and see what's going on.

/var/log/exim/rejectlog
 
You might want to have a peak at the mainlog as well.

I found this on my mainlog:

Code:
2007-09-07 20:36:35 H=localhost (www.domain.com) [127.0.0.1] incomplete transaction (connection lost) from <[email protected]> for freshmint
@domain.com
2007-09-07 20:36:35 unexpected disconnection while reading SMTP command from localhost (www.domain.com) [127.0.0.1]

Any ideas?
 
I'm glad you found the problem. The use of old and outdated software is of course always a problem.

And depending on blocklists creates a problem when those blocklists fail to work; that's one of the problems on depending on free software.

I'm a firm believer in using port 587 as the submission port for any webmail clients if possible; there's no reason to waste time and resources checking to see if your own server is on a blocklist.

Jeff
 
I'm glad you found the problem. The use of old and outdated software is of course always a problem.

Yeah, didn't thought at first it'd be an outdated problem. Now I'm currently investigating an odd behavior from Dovecot which is failing on authenticating pop accounts on subdomains (example: [email protected], maindomain.com being the domain DA is installed). Lesson learned, I'll update Dovecot first to check if that solves the issue before opening a thread about it.

I'm a firm believer in using port 587 as the submission port for any webmail clients if possible; there's no reason to waste time and resources checking to see if your own server is on a blocklist.

Jeff

Can you tell me more about this? The first solution presented on that thread was to change port to 587, but why? Does Exim skip the relay list check on connections on that port?
 
Port 587 is the authenticated email submission port. email cannot be accepted on port 587 unless the user is authenticated. Any webmail client submitting email on port 587 MUST use authenticated submission.

And yes, our exim.conf file skips all checks on all email successfully submitted on port 587, because in order to submit email on port 587, the user MUST be authenticated.

Jeff
 
Port 587 is the authenticated email submission port. email cannot be accepted on port 587 unless the user is authenticated. Any webmail client submitting email on port 587 MUST use authenticated submission.

And yes, our exim.conf file skips all checks on all email successfully submitted on port 587, because in order to submit email on port 587, the user MUST be authenticated.

Jeff

Thanks Jeff, I'll be using 587 on my webmails too from now on. :D
 
Back
Top