Hi! I have a server with a few thousand mailboxes (for a few hundred domains) on it. The usernames are following several naming conventions: username_domain domain_username username_domain.tld username-domain domain.username The reason for this chaos is that the accounts were set up on different mailservers, some imail, some linux, some with virtualmin and some manually and through aquisitons etc it has all ended up in one server. Now we are setting up atmail to replace imp. The loginprocess of atmail is a bit different in that you just type in your mail address and atmail tries a few combinations of loginnames to login. However, some of the combinations over atmail cant login to. Some of them works fine when using this line in dovecot.conf auth_username_translation = @_ Is there any facility to let dovecot do username mapping? If I eg have a file: usermapping that looks like this: user at domain1.com domain1_user user at domain2.com user_domain2 user at domain3.com domain3.user And yes, I know that the best way is to start again and use virtual domains and get all into one naming standard, but unfortunately, that is not going to happen. The other alternative is of course to hack into the source code of atmail, but I am not that confident in PHP. Any ideas? -- Regards Roald Amundsen
On Sat, 2008-11-29 at 21:49 +0100, Roald Amundsen wrote:> Is there any facility to let dovecot do username mapping? > > If I eg have a file: usermapping that looks like this: > > user at domain1.com domain1_user > user at domain2.com user_domain2 > user at domain3.com domain3.userYes, but can you change your passdb? You can use any passdb that allows specifying user=user at domain extra field (http://wiki.dovecot.org/PasswordDatabase/ExtraFields). For example with passwd-file (http://wiki.dovecot.org/AuthDatabase/PasswdFile): domain1_user:{plain}pass:1000:1000::/home/domain1.com/user::user=user at domain1.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20081130/a8a5ecde/attachment-0002.bin>
Timo Sirainen wrote:> On Sat, 2008-11-29 at 21:49 +0100, Roald Amundsen wrote: >> Is there any facility to let dovecot do username mapping? >> >> If I eg have a file: usermapping that looks like this: >> >> user at domain1.com domain1_user >> user at domain2.com user_domain2 >> user at domain3.com domain3.user > > Yes, but can you change your passdb? You can use any passdb that allows > specifying user=user at domain extra field > (http://wiki.dovecot.org/PasswordDatabase/ExtraFields). For example with > passwd-file (http://wiki.dovecot.org/AuthDatabase/PasswdFile): > > domain1_user:{plain}pass:1000:1000::/home/domain1.com/user::user=user at domain1.com >Thanks, this seems to be what I am looking for. However, I am not sure if I am reading the links right. I am supposed to make a custom passwd-file, and point dovecot to this? I can use a script to parse genericstable or even virtusertable and add this information at the end of the dovecot-passwd-file? And I can still use /etc/passwd as a fallback in case something goes wrong? As long as I keep userdb passwd in dovecot.conf? Well, I think I should be reading some more documentation and look at the example configs on the wiki. Thanks for the help! -- Roald Amundsen
Possibly Parallel Threads
- Login with firstname.lastname instead of loginname
- Using filegroup for access control within a share
- Login with firstname.lastname instead of loginname - WORKING
- Using filegroup for access control within a share
- Using filegroup for access control within a share