Outgoing SMTP error from outlook, thunderbird, blackberry clients

7 posts / 0 new
Topic locked
Last post
#1 Thu, 07/09/2009 - 15:17
tonysch

Outgoing SMTP error from outlook, thunderbird, blackberry clients

First I must say... What a buitifull application. :)

I have Virtualmin running on Ubuntu 9.04 server with no problems to until this. I have a few clients that use outlook, thunderbird, and blackberry via IMAP/POP. They can retrieve email with no problem. When they attempt to send an email I see a mail log error...

Jul 9 20:12:35 srv03 postfix/smtpd[12418]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory Jul 9 20:12:35 srv03 postfix/smtpd[12418]: warning: static-96-254-141-18.tampfl.fios.verizon.net[96.254.141.18]: SASL LOGIN authentication failed: generic failure

I have read many posts and tried the adding the postfix user to the sasl group (or vica verca), this did not help.

I was wondering if anyone could point me in the correct direction.

Thanks in advance, Tony

Thu, 07/09/2009 - 15:35
andreychek

Howdy,

Well, Ubuntu 9.04 isn't supported by the installer, only 8.04 is, so there may be a problem with the saslauthd setup.

Is the saslauthd daemon running? Do you see it if you run "ps auxw | grep saslauthd"?

If not, does it start up if you run: /etc/init.d/saslauthd start

-Eric

Thu, 07/09/2009 - 16:27 (Reply to #2)
tonysch

Thanks for your quick response. I know Ubuntu 9.04 is not supported. :) I guess I am just a glutton.

Here are the outputs you requested:

ps auxw | grep saslauthd

root 14315 0.0 0.1 6260 728 pts/0 S+ 21:24 0:00 grep saslauthd

/etc/init.d/saslauthd start
  • Starting SASL Authentication Daemon saslauthd
  • No run directory defined for saslauthd, not starting
Thu, 07/09/2009 - 23:19 (Reply to #3)
andreychek

Yeah, sounds like that's your issue -- saslauthd isn't launching.

That's normally configured by the installer :-) But, you should certainly be able to get it running manually.

I'm not quite sure of why it's failing, but I'd probably start by looking in "/etc/default/saslauthd", and making sure the information in there looks sane.

For example, on my (slightly older) Ubuntu system, I have this line in there:

OPTIONS="-m /var/spool/postfix/var/run/saslauthd -r"

You'd probably need something similar -- and make sure the dir exists.

The perms I have look like this:

ls -ld /var/spool/postfix/var/run/saslauthd drwxr-x--- 2 root sasl 4096 2009-06-27 22:36 /var/spool/postfix/var/run/saslauthd

Fri, 07/10/2009 - 08:22 (Reply to #4)
tonysch

Here are my outputs

cat from saslauthd: PARAMS="-m /var/spool/postfix/var/run/saslauthd -r"

ls -ld /var/spool/postfix/var/run/saslauthd drwxr-xr-x 2 root sasl 4096 Jun 28 22:30 /var/spool/postfix/var/run/saslauthd

Fri, 07/10/2009 - 09:54 (Reply to #5)
andreychek

Yeah, at a glance, that all looks good.

I'm not really familiar with the error you're getting.

I typed this into Google:

No run directory defined for saslauthd, not starting

And the second hit was this link to a similar problem in the Ubuntu forums:

http://ubuntuforums.org/showthread.php?t=493829

They suggest that rather than "PARAMS", that you should have "OPTIONS". So something like this in /etc/default/saslauthd:

OPTIONS="-m /var/spool/postfix/var/run/saslauthd -r"

Tue, 07/14/2009 - 12:51
tonysch

Funny thing.... All of the sudden everything started working properly. :)

Didn't do anything... Just a few reboots.

Oh well!

Thanks for everyone's help, Tony

Topic locked