Good point.
But when I try to add a user with the "user@domain" format using the
useradd command I get error...
useradd: invalid user name 'u...@domain.com'
Here is output you requested:
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 Scientific Linux release
6.5 (Carbon)
auth_debug = yes
auth_debug_passwords = yes
auth_verbose = yes
auth_verbose_passwords = plain
mail_access_groups = mail
mail_debug = yes
mail_location = maildir:~/Maildir
mbox_write_locks = fcntl
namespace {
hidden = no
inbox = yes
list = yes
location =
prefix =
separator = .
subscriptions = yes
type = private
}
passdb {
driver = pam
}
protocols = imap
ssl_ca = </etc/pki/dovecot/certs/intermediate.crt
ssl_cert = </etc/pki/dovecot/certs/avalon20140929.crt
ssl_key = </etc/pki/dovecot/private/avalon20140929.key
userdb {
driver = passwd
}
verbose_ssl = yes
protocol imap {
imap_id_log = *
}
On 10/2/2014 3:19 PM, Reindl Harald wrote:
Am 02.10.2014 um 22:13 schrieb Cliff Hayes:
I am trying to configure a new IMAP based mail server.
I thought I had everything correct.
I have dovecot logging turned up and see that dovecot is processing the entire
email address as the username like
this...
Oct 2 14:52:20 servername dovecot: auth: Debug:
pam(testu...@domain.com,1.2.3.4): lookup service=dovecot
... and of course pam is reporting that as an invalid user.
Moments ago when all was mbox, authentication worked fine.
I can see Thunderbird has the username correct (no domain).
What is tacking on the domain and how do I fix?
output of "dovecot -n" would be in general a good start
* how looks your user database
* if you don't use domain as part of the username what do you do
in case you get a second domain and names collide
* these days the full qualified mail address as username is common
and in caes of virtual users you can feed all from the same
source instead hanlde the localpart special for login-names
