On 11/7/2025 4:54 PM, Dave McGuire via dovecot wrote:
On 11/7/25 11:47, Alex via dovecot wrote:
Hi, I'm using dovecot-2.3.21.1 on fedora42. It seems that
increasingly
remote clients are only supporting the full email address as the
login ID
instead of just the username. One such example is Apollo.io, an AI
sales
platform that uses IMAP to connect to a remote server to send and
receive
emails.
The documentation I've found on this appears to be deprecated or
incomplete. Do I want to look for "shared namespace" documentation?
Currently, emails are stored in /var/spool/mail/username. Does
this need
to change to something like /var/spool/[1]domain.com/username?
We've been using full-address logins here for 20yrs or so. We use /
var/mail/<domain>/<uname> for mail storage. No shared namespace stuff.
We use MySQL-based authentication. It's all very easy to set up.
-Dave
Hello,
If you are serving a single domain (or multiple domains that ultimately
deliver to the same mailbox, for example
[[email protected]](mailto:[email protected]) and
[[email protected]](mailto:[email protected]) both going to myuser),
you don’t need to store mailboxes under /var/spool/<domain>/myuser. You
can simply keep them in /var/spool/mail/myuser.
This depends entirely on how you configure Postfix and Dovecot regarding
domain and user mapping.
I have been using two different setups — one on my home PC with a few
users across several domains, and another integrated with Active
Directory as the user repository. Both accept mail for multiple domains
without including the domain name in the mailbox path.
A standard Dovecot and Postfix configuration will accept both "user" and
"user@domain" as valid logins if configured correctly.
As a reference, here’s an example configuration using LDAP to query
Active Directory:
/etc/dovecot/dovecot-ldap.conf.ext
user_attrs =
sAMAccountName=uid,sAMAccountName=home=/home/ad-users/%{ldap:sAMAccountName},sAMAccountName=username,primaryGroupID=gid
user_filter =
(&(objectClass=person)(|(sAMAccountName=%n)(sAMAccountName=%u)(proxyAddresses=SMTP:%u)(proxyAddresses=smtp:%u)(userPrincipalName=%u)(mail=%u)))
/etc/postfix/ad_aliases.cf
bind = yes
bind_dn = <ad-postfix-ldap-user>
bind_pw = <bind_dn-password>
server_host = ldaps://myadserver.domain
search_base = DC=domain,DC=com
query_filter =
(&(objectClass=person)(|(mail=%s)(samAccountName=%u)(proxyAddresses=*:%s)))
result_attribute = samAccountName
terminal_result_attribute = otherMailbox
domain = hash:/etc/postfix/local_domains
/etc/postfix/main.cf
virtual_alias_maps = ldap:/etc/postfix/ad_aliases.cf
There’s a bit more to it, but this should put you on the right track.
Whether you are using "local" (Linux) users or "remote" users (via
MySQL, LDAP, or AD), you don’t need to change the mailbox storage path
to support "user@domain" logins in Postfix and Dovecot — both have
supported this for decades.
Regards,
--
Anto'nio Henrique A. Proenca de Oliveira
"Although we can never go back, like an old sweet
song with a strong refrain, memories remain" - (Someone)
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
$Id: .signature,v 1.5 2008/03/13 11:22:00 tat Exp tat $
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
