Cannot Connect To E-Mail

[toml]

then what do the first two lines mean?



I get:



[root@alfa ~]# sh checkdomainuid.sh
checkdomainuid.sh: line 2: use: command not found
checkdomainuid.sh: line 3: use: command not found
checkdomainuid.sh: line 5: my: command not found
checkdomainuid.sh: line 6: my: command not found
checkdomainuid.sh: line 8: syntax error near unexpected token `DOMFILE,"<$domain file"'
checkdomainuid.sh: line 8: `open(DOMFILE,"<$domainfile") || die "error opening $ domainfile. $!\n";'

Those are output due to the passdb entries in the dovecot.conf, it tries shadow then the virtual passwd-file.

When ever you see a script that starts with a '#!' (shebang) that means that what follows is the interpreter for that script. In this case it is a perl script. You can do 'chmod +x checkdomainuid.sh ; ./checkdomainuid.sh' or execute like this 'perl checkdomainuid.sh', either one should work.

 

[jonium]

I did chmod +x checkdomainuid.sh and then the output of ./checkdomainuid.sh is nothing

 

[toml]

I did chmod +x checkdomainuid.sh and then the output of ./checkdomainuid.sh is nothing

That just means that all your userids match the domainowners user id. That is good.

If your only problem is that you have entries in the log file that say unknown user where the usernname looks like an email address ([email protected]), and it is prefixed with passdb or shadow, then those are safe to ignore, those usernames would/should be found in the passwd-file (aka /etc/virtual/$domain/passwd).

The disconnects you see are also normal, imap clients will just reconnect.

 

[jonium]

the problem is that I'm not receiving some emails sent by http forms using SMTP Mail

 

[toml]

the problem is that I'm not receiving some emails sent by http forms using SMTP Mail

Is it a sending (SMTP) or a receiving (POP3/IMAP) problem? You need to look in your exim logs to make sure it was sent properly. If it was sent properly then you need to look in your POP3/IMAP might come into play. Of course if it was configured to send the email using a different SMTP server, then you are on your own to figure out why it didn't get delivered. In either case you need to make sure that the SMTP server accepted the email, then you need to make sure that SMTP server delivered the email to final destination. Then you can start looking at the POP3/IMAP server for issues.

 

[jonium]

here is the exim mainlog:

2011-05-25 00:36:46 H=localhost (www.*****.net) [127.0.0.1] F=<staff@*****.net> rejected RCPT <recipient@.*****.com>: authentication required
2011-05-25 00:36:46 H=localhost (www.*****.net) [127.0.0.1] incomplete transaction (connection lost) from <staff@.*****.net>
2011-05-25 00:36:46 unexpected disconnection while reading SMTP command from localhost (www.*****.net) [127.0.0.1] (error: Connection reset by peer)


please notice that recipient@.*****.com is an external email, not managed on the same server

 

[toml]

here is the exim mainlog:

2011-05-25 00:36:46 H=localhost (www.*****.net) [127.0.0.1] F=<staff@*****.net> rejected RCPT <recipient@.*****.com>: authentication required
2011-05-25 00:36:46 H=localhost (www.*****.net) [127.0.0.1] incomplete transaction (connection lost) from <staff@.*****.net>
2011-05-25 00:36:46 unexpected disconnection while reading SMTP command from localhost (www.*****.net) [127.0.0.1] (error: Connection reset by peer)


please notice that recipient@.*****.com is an external email, not managed on the same server

That means you need to authenticate (send username/password) when using SMTP. If it was using sendmail from the command line and it was all local, it should work.

 

[moo]

This is a fairly old threat, but I ran into a simular TLS handshaking problem yesterday.

My conclusion is that it has to do with old mail clients using TLS Version 1. In my case it was a Mac OS 10.9.5 using the native Mac Mail Client.

Turns out the new dovecot build writes the following into the /etc/dovecot/conf/ssl.conf file:

ssl_min_protocol = TLSv1.1

Older clients will work again when the line is changed back to:

ssl_min_protocol = TLSv1

Don't forget to restart dovecot:

service dovecot restart

Of course, this line will be changed every time dovecot is build.
Question is whether you still want to use TLS Version 1. In my opinion is better to stop supporting it and forcing clients using older software to stop using TLS.

Hope this helps.