Tickets :: [#12652] SMTP to localhost with no authentication

6.0.0-beta1

7/20/25

Summary	SMTP to localhost with no authentication
Queue	Horde Base
Queue Version	5.1.4
Type	Bug
State	Not A Bug
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	jmatos (at) math (dot) ist (dot) utl (dot) pt
Created	09/03/2013 (4338 days ago)
Due
Updated	10/22/2013 (4289 days ago)
Assigned	09/03/2013 (4338 days ago)
Resolved	09/04/2013 (4337 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/22/2013 03:15:52 AM	Michael Slusarz	Comment #13	Reply to this comment
[Show Quoted Text - 14 lines][Hide Quoted Text] [AUTH Command - method: DIGEST-MD5; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure C: AUTH CRAM-MD5 S: 334 [...base64 data omitted...] [AUTH Command - method: CRAM-MD5; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure C: AUTH LOGIN S: 334 [...base64 data omitted...] C: [...base64 data omitted...] S: 334 [...base64 data omitted...] [AUTH Command - method: LOGIN; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure [AUTH Command - method: PLAIN; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure Exactly what the log tells you: your authentication is incorrect. This has nothing to do with this ticket. Please use the mailing list to ask for support. http://www.horde.org/mail/ contains a list of all available mailing lists.

10/21/2013 01:13:38 PM	r (at) hq (dot) sk	Comment #12	Reply to this comment
Same problem here. horde/conf.php: $conf['mailer']['params']['host'] = 'localhost'; $conf['mailer']['params']['port'] = 25; $conf['mailer']['params']['localhost'] = 'localhost'; $conf['mailer']['params']['auth'] = false; $conf['mailer']['type'] = 'smtp'; imp/backends.php: $servers['imap'] = array( 'disabled' => false, [..imap config omited...] 'smtp' => array( 'debug' => '/tmp/horde_smpt.log') ); /tmp/horde_smpt.log: ------------------------------ Mon, 21 Oct 2013 15:07:12 +0200 S: 220 gw2.example.com ESMTP C: EHLO gw2 S: 250-gw2.example.com S: 250-PIPELINING S: 250-SIZE 104857600 S: 250-VRFY S: 250-ETRN S: 250-STARTTLS S: 250-AUTH DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN S: 250-AUTH=DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN S: 250-ENHANCEDSTATUSCODES S: 250-8BITMIME S: 250 DSN C: STARTTLS S: 220 2.0.0 Ready to start TLS C: EHLO gw2 S: 250-gw2.example.com S: 250-PIPELINING S: 250-SIZE 104857600 S: 250-VRFY S: 250-ETRN S: 250-AUTH DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN S: 250-AUTH=DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN S: 250-ENHANCEDSTATUSCODES S: 250-8BITMIME S: 250 DSN C: AUTH DIGEST-MD5 S: 334 [...base64 data omitted...] [AUTH Command - method: DIGEST-MD5; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure C: AUTH CRAM-MD5 S: 334 [...base64 data omitted...] [AUTH Command - method: CRAM-MD5; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure C: AUTH LOGIN S: 334 [...base64 data omitted...] C: [...base64 data omitted...] S: 334 [...base64 data omitted...] [AUTH Command - method: LOGIN; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure [AUTH Command - method: PLAIN; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure C: QUIT S: 221 2.0.0 Bye S: 220 gw2.example.com ESMTP C: EHLO gw2 S: 250-gw2.example.com S: 250-PIPELINING S: 250-SIZE 104857600 S: 250-VRFY S: 250-ETRN S: 250-STARTTLS S: 250-AUTH DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN S: 250-AUTH=DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN S: 250-ENHANCEDSTATUSCODES S: 250-8BITMIME S: 250 DSN C: STARTTLS S: 220 2.0.0 Ready to start TLS C: EHLO gw2 S: 250-gw2.example.com S: 250-PIPELINING S: 250-SIZE 104857600 S: 250-VRFY S: 250-ETRN S: 250-AUTH DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN S: 250-AUTH=DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN S: 250-ENHANCEDSTATUSCODES S: 250-8BITMIME S: 250 DSN C: AUTH DIGEST-MD5 S: 334 [...base64 data omitted...] [AUTH Command - method: DIGEST-MD5; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure C: AUTH CRAM-MD5 S: 334 [...base64 data omitted...] [AUTH Command - method: CRAM-MD5; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure C: AUTH LOGIN S: 334 [...base64 data omitted...] C: [...base64 data omitted...] S: 334 UGFzc3dvcmQ6 [AUTH Command - method: LOGIN; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure [AUTH Command - method: PLAIN; username: username] S: 535 5.7.8 Error: authentication failed: authentication failure C: QUIT S: 221 2.0.0 Bye

09/04/2013 06:21:27 PM	Michael Slusarz	Comment #11	Reply to this comment
2013-09-04 19:04:30 plain_server authenticator failed for localhost (cubo) [127.0.0.1]: 535 Incorrect authentication data (set_id=jmatos) This is why a smtp log is needed. 'debug' => 'filename' in SMTP config in imp/config/backends.local.php

09/04/2013 06:19:31 PM	jmatos (at) math (dot) ist (dot) utl (dot) pt	Comment #10	Reply to this comment
That's the problem then. Port 25 is no longer the default. Mail should be submitted to port 587 instead. You need to explicitly request port 25 in the SMTP configuration. It seems that exim4 does not like some of the data it is receiving from horde with No authentication chosen: 2013-09-04 19:04:30 plain_server authenticator failed for localhost (cubo) [127.0.0.1]: 535 Incorrect authentication data (set_id=jmatos)

09/04/2013 05:20:59 PM	jmatos (at) math (dot) ist (dot) utl (dot) pt	Comment #9	Reply to this comment
That's the problem then. Port 25 is no longer the default. Mail should be submitted to port 587 instead. You need to explicitly request port 25 in the SMTP configuration. That does not seem to work. Notice also that "The port to connect to [25]" still appears in the horde configuration web interface. I also attempted to use port 587, supplying login and password and always got the same error.

09/04/2013 05:09:55 PM	Michael Slusarz	Comment #8 State ⇒ Not A Bug	Reply to this comment
That's the problem then. Port 25 is no longer the default. Mail should be submitted to port 587 instead. You need to explicitly request port 25 in the SMTP configuration.

09/04/2013 05:07:10 PM	Michael Slusarz	Comment #7	Reply to this comment
ORDE: authentication[imp] Server denied authentication. [pid 25461 on line 1064 of "path/to/horde/imp/lib/Compose.php"] The issue is likely that your Horde SMTP configuration either has no 'port' value or an 'empty' port value, so that you are connecting to port 587 (which is the correct, preferred port but requires authentication to be configured). Most likely before you were connecting to port 25 (deprecated, doesn't require authentication). But if this is the case, this means that you didn't upgrade your Horde config.

09/04/2013 05:04:54 PM	jmatos (at) math (dot) ist (dot) utl (dot) pt	Comment #6	Reply to this comment
I have been able to bypass the problem in either of the following two ways: You didn't answer my question of either: 1.) Have you upgraded ALL packages to their latest versions (i.e. not only Horde_Smtp but Horde_Core) Yes. pear upgrade horde -a -B -c today 2) You haven't provded an SMTP log. My priority was getting a working configuration with current packages. That has been achieved with /usr/lib/sendmail -oi instead of using SMTP. I'm guessing you haven't defined a port number in your configuration Right. It always worked with the default port 25. file, and you are using old Horde packages. Wrong.

09/04/2013 05:03:10 PM	filip (at) itf (dot) fys (dot) kuleuven (dot) be	Comment #5	Reply to this comment
I'm actually having the same problem as the poster. I'm using the horde webmail edition and when I updated to 5.1.2 I got the same problems with sending mails through an external smtp server which requires no login. I get the the following error message: ORDE: authentication[imp] Server denied authentication. [pid 25461 on line 1064 of "path/to/horde/imp/lib/Compose.php"] As far as I'm aware all of the packages have been updated to their latest version through the pear update command. I'm also running debian 6.0.8 if that matters and the work around of using the sendmail command seems to do the trick. But I am interested in find out what is wrong and switching back to the smtp server directly. [Show Quoted Text - 10 lines][Hide Quoted Text] I have been able to bypass the problem in either of the following two ways: You didn't answer my question of either: 1.) Have you upgraded ALL packages to their latest versions (i.e. not only Horde_Smtp but Horde_Core) 2) You haven't provded an SMTP log. I'm guessing you haven't defined a port number in your configuration file, and you are using old Horde packages.

09/04/2013 04:43:42 PM	Michael Slusarz	Comment #4	Reply to this comment
I have been able to bypass the problem in either of the following two ways: You didn't answer my question of either: 1.) Have you upgraded ALL packages to their latest versions (i.e. not only Horde_Smtp but Horde_Core) 2) You haven't provded an SMTP log. I'm guessing you haven't defined a port number in your configuration file, and you are using old Horde packages.

09/04/2013 04:08:36 PM	jmatos (at) math (dot) ist (dot) utl (dot) pt	Comment #3	Reply to this comment
I have been able to bypass the problem in either of the following two ways: 1. Downgrading to Jul 16 versions (including Horde_SMTP-1.1.0). 2. Using for the mailer configuration /usr/lib/sendmail -oi instead of SMTP and the current stable horde versions. Our setup is debian squeeze (6.0.7) with exim4. The horde log shows 2013-09-04T16:18:09+01:00 ERR: HORDE [imp] Server denied authentication. [pid 19639 on line 1064 of "/var/www/horde5/imp/lib/Compose.php"]

09/03/2013 07:14:46 PM	Michael Slusarz	Comment #2 Assigned to Michael Slusarz State ⇒ Feedback Priority ⇒ 1. Low	Reply to this comment
Can't reproduce. You can try upgrading to Horde_Smtp 1.2.1, but nothing in there should have caused an issue. At a minimum, would need a debug log from SMTP communication.

09/03/2013 11:33:45 AM	jmatos (at) math (dot) ist (dot) utl (dot) pt	Comment #1 Patch ⇒ No State ⇒ Unconfirmed Milestone ⇒ Queue ⇒ Horde Base Summary ⇒ SMTP to localhost with no authentication Type ⇒ Bug Priority ⇒ 3. High	Reply to this comment
SMTP to localhost with no authentication fails with "Server denied authentication". In the previous stable horde version it was relatively easy to downgrade Horde_SMTP to 1.1.0 and everything would work. That is no longer possible.