Roundcube Community Forum
Release Support => Pending Issues => Topic started by: atjensen11 on July 17, 2009, 11:35:03 PM
-
I downloaded and installed the most current stable release of Roundcube (0.2.2).
My outgoing (SMTP) server uses DKIM and Domain Keys to sign outgoing email messages. In order to have emails signed, the client needs to use the submission port 587.
My Roundcube install works fine when setting the SMTP port to 25. When I use port 587, I get errors logged in the log.
I also have Squirrelmail installed. It is configured to use SMTP with port 587 and works as intended. Therefore, I verified the SMTP server is configured and signing emails.
Has anyone tried this configuration with Roundcube before?
-
what are the errors?
-
With the config file set to use port 587, I get the following error:
[17-Jul-2009 22:18:15] Invalid response code received from server (535):
[17-Jul-2009 22:18:15 -0500] SMTP Error: SMTP error: Authentication failure: Invalid response code received from server (Code: 535) in /var/www/clients/client0/web17/web/webmail/program/steps/mail/func.inc on line 1296 (POST /?_task=mail&_action=send)
-
Do you have to use a different usename and password to connect to your mail server on port 587 than on 25? Check your mailserver logs, may be there is some indication of why the authentication is failing.
-
Most likely is that 25 doesnt require authentication, while 587 does.
-
I do require authentication and that is why I configured DKIM and DomainKeys to use 587 as well.
Just to reiterate, my system configuration works as expected with all other email clients tested (Windows Live, Outlook, & Squirrelmail). I am now trying to get Roundcube to work as well.
I was tailing the mail.log file when trying to send a message from Roundcube with the SMTP port set to 587. Nothing was logged. I then tailed the syslog file and here is the sanitized result:
Jul 19 18:30:21 server imapd: Connection, ip=[::ffff:192.168.XX.XX]
Jul 19 18:30:21 server imapd: LOGIN, user=user@example.com, ip=[::ffff:192.168.XX.XX], port=[60637], protocol=IMAP
Jul 19 18:30:21 server postfix/smtpd[12406]: connect from server.example.com[192.168.XX.XX]
Jul 19 18:30:21 server postfix/smtpd[12406]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Jul 19 18:30:21 server postfix/smtpd[12406]: warning: server.example.com[192.168.XX.XX]: SASL LOGIN authentication failed: generic failure
Jul 19 18:30:21 server postfix/smtpd[12406]: disconnect from server.example.com[192.168.XX.XX]
Jul 19 18:30:21 server imapd: LOGOUT, user=user@example.com, ip=[::ffff:192.168.XX.XX], headers=0, body=0, rcvd=10, sent=83, time=0
-
From the syslog entry “SASL authentication failure: cannot connect to saslauthd server”. Your server is apparently setup it use credentials from SASL to authenticate SMTP clients (this is SMTP auth, nothing to do with DKIM or domainkeys) and it looks like there is something wrong with your SASL server that is preventing the authentication.
-
I ended up doing a lot of testing with other email clients and eventually found that there was an underlying SASL issue. That issue has been correct and now all other email clients are authenticating on port 587 correctly.
As I mentioned before, the email server applies DKIM signatures to any emails authenticated through this port. Email clients configured to send on port 25 will send mail, but the DKIM signature is missing.
All email clients now work this way except for Roundcube. I have changed the SMTP port to 587 in the configuration file.
When I compose and send an email, it is sent without any error messages. But it does not appear to be working correctly as there is no DKIM signature in the resulting message. It almost appears as though Roundcube just defaults to port 25. The comment text in the configuration file even only lists port 25 and 465 as options.
Lastly, I should note that I have performed a clean installation of the newest stable (0.3) release of Roundcube since my original post.
How can I ensure that Roundcube is using port 587?
-
You should check to see if the problem continue with RoundCube 3.1 and if it does you should start a ticket Roundcube Webmail (http://trac.roundcube.net/)