Thunderbird requires "-" in user name vice "@" to send mail

Help! (Home for newbies)
1

I can log into my account with Thunderbird using dan@example.com but when I try to send mail with that same account it doesn’t work - When I switch the user name to dan-example.com it works.

Here’s the maillog entries

warning: SASL authentication failure: Password verification failed
warning: SASL PLAIN authentication failed: authentication failure
warning: SASL LOGIN authentication failed: authentication failure

What settings do I have wrong?

main.cf:

readme_directory = /usr/share/doc/postfix-2.6.5/README_FILES
virtual_alias_maps = hash:/etc/postfix/virtual
sender_bcc_maps = hash:/etc/postfix/bcc
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
mailbox_command = /usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME
home_mailbox = Maildir/
smtpd_sasl_auth_enable = yes
broken_sasl_auth_clients = yes
smtpd_tls_security_level = may
smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination
data_directory = /var/lib/postfix
smtpd_tls_cert_file = /etc/pki/dovecot/certs/dovecot.pem
smtpd_tls_key_file = /etc/pki/dovecot/private/dovecot.pem

master.cf

smtp inet n - n - - smtpd
submission inet n - n - - smtpd
-o smtpd_tls_security_level=encrypt
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=permit_sasl_authenticated,reject
-o milter_macro_daemon_name=ORIGINATING
smtps inet n - n - - smtpd
-o smtpd_tls_wrappermode=yes
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=permit_sasl_authenticated,reject
-o milter_macro_daemon_name=ORIGINATING

Also, do I need to buy a SSL certificate to remove the security warnings? I have read somewhere that this should be a self signing certificate. Is there a way to fix that issue?

Setting up the email has been very frustrating from day one :frowning:

Thanks

Dan

2

Hi Dan,

Make sure that your saslauthd daemon is running with the -r parameter… -r is necessary in order for usernames containing an @ to be able to authenticate.

-Eric

3

Eric,

Thank you,

That did the trick, what about the certificate question? should it be self signing or do I need to purchase one?

Dan

4

Ah, sorry, I had overlooked your SSL question.

To completely get rid of any SSL-related warning messages, you would indeed want to get a commercial SSL cert. Self signed certs generally cause your the client to generate a warning. That’s the case whether you’re dealing with email, websites, or anything else that deals with SSL.

However, in the case of email – many email clients can also be configured to not display the error after it appears the first time.

Also, make sure that the hostname you’re connecting to matches the domain name that appears in your SSL cert.

-Eric