Random Questions

Discussion in 'General' started by dclardy, Sep 2, 2009.

  1. dclardy

    dclardy Member

    SMTP Server not sending emails

    I just installed this on my server, and I am extremely happy with everything so far except I can't send emails.

    I am unable to send emails from the email accounts that I have setup. What is the correct SMTP setup for these. The email account is [email protected]. I can send emails to that account and receive them, but I can't send them from that account unless I use squirrel mail.
     
    Last edited: Sep 2, 2009
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You have to enable smtp-auth in your email client. The username and password are the same then the pop3 password.
     
  3. dclardy

    dclardy Member

    How do I go about that? I am new to linux. I have the Perfect Server Ubuntu version with ISPConfig 3.0.
     
  4. falko

    falko Super Moderator Howtoforge Staff

    There must be something like "Server requires authentication" in your email client. Please activate this option.
     
  5. dclardy

    dclardy Member

    This is the error that I get in Thunderbird.

    [​IMG]
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Please take a look in the mail log on the server and post the error messages that you get there when you try to authenticate with smtp-auth. Also make sure that you did not enable ssl in thunderbird.
     
  7. dclardy

    dclardy Member

    These are from the mail-warn log:

    Code:
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: SASL authentication failure: Password verification failed
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: h3.204.39.162.static.ip.windstream.net[162.39.204.3]: SASL PLAIN authentication failed: generic failure
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: h3.204.39.162.static.ip.windstream.net[162.39.204.3]: SASL LOGIN authentication failed: generic failure
    Sep 3 09:37:48 server postfix/smtpd[20859]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Sep 3 09:37:48 server postfix/smtpd[20859]: warning: SASL authentication failure: Password verification failed
    Sep 3 09:37:48 server postfix/smtpd[20859]: warning: h3.204.39.162.static.ip.windstream.net[162.39.204.3]: SASL PLAIN authentication failed: generic failure
    Sep 3 09:37:49 server postfix/smtpd[20859]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Sep 3 09:37:49 server postfix/smtpd[20859]: warning: h3.204.39.162.static.ip.windstream.net[162.39.204.3]: SASL LOGIN authentication failed: generic failure
    This is from the mail-log:

    Code:
    Sep 3 09:35:01 server postfix/smtpd[20802]: connect from localhost.localdomain[127.0.0.1]
    Sep 3 09:35:01 server postfix/smtpd[20802]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
    Sep 3 09:35:01 server postfix/smtpd[20802]: disconnect from localhost.localdomain[127.0.0.1]
    Sep 3 09:37:37 server postfix/smtpd[20859]: connect from h3.204.39.162.static.ip.windstream.net[162.39.204.3]
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: SASL authentication failure: Password verification failed
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: h3.204.39.162.static.ip.windstream.net[162.39.204.3]: SASL PLAIN authentication failed: generic failure
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Sep 3 09:37:44 server postfix/smtpd[20859]: warning: h3.204.39.162.static.ip.windstream.net[162.39.204.3]: SASL LOGIN authentication failed: generic failure
    Sep 3 09:37:48 server postfix/smtpd[20859]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Sep 3 09:37:48 server postfix/smtpd[20859]: warning: SASL authentication failure: Password verification failed
    Sep 3 09:37:48 server postfix/smtpd[20859]: warning: h3.204.39.162.static.ip.windstream.net[162.39.204.3]: SASL PLAIN authentication failed: generic failure
    Sep 3 09:37:49 server postfix/smtpd[20859]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Sep 3 09:37:49 server postfix/smtpd[20859]: warning: h3.204.39.162.static.ip.windstream.net[162.39.204.3]: SASL LOGIN authentication failed: generic failure
    Sep 3 09:37:50 server postfix/smtpd[20859]: disconnect from h3.204.39.162.static.ip.windstream.net[162.39.204.3]
     
  8. dclardy

    dclardy Member

    It looks like the SASLAuth files did not load properly. Is there anyway to reinstall them at this point?

    Do these files make up that server?

    libsas12-2 libsas12-modules libsas12-modules-sql sas12-bin

    When I tried to install these using Falko's how-to directions, they could not be found. I thought that I saw them being installed in the initial load of Ubuntu.

    I also had the same issue with getmail14. How can I put these items on the server? Do I need to do a wipe and then reinstall? My personal site is the only that is currently on the server. It is not a big deal to me to do that.

    Is there another operating system that you Linux Gods would recommend? I am new to the whole system, but Ubuntu is a name that I had heard before so I went with it.

    Thanks for help and suggestions.
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    This explains of course your problems. The setup can not work if not all files from all steps are installed and all these files have to be installed before ispconfig is installed. If you will install them after ispconfig, they might overwrite the ispconfig setup.

    The recommended OS for ISPConfig is debian.
     
  10. dclardy

    dclardy Member

    Thanks for the recommendation. I will switch over to Debian tonight. No issue really.

    The reason the files were not installed is because they were not in the repository. To me that does not make any sense, but I just kept going. Completly my fault on that.

    Thanks.
     

Share This Page