- dovecot - dovecot.org

[Dovecot] crypt() failure is possible
by Arkadiusz Miskiewicz 21 May '09

21 May '09

dovecot 1.1.15 in src/auth/password-scheme.c contains: static bool crypt_verify(const char *plaintext, const char *user ATTR_UNUSED, const unsigned char *raw_password, size_t size) { const char *password; if (size == 0) { /* the default mycrypt() handler would return match */ return FALSE; } password = t_strndup(raw_password, size); return strcmp(mycrypt(plaintext, password), password) == 0; } but according to man page crypt() can fail and NULL is returned then. On other hand glibc info page is silent about such failure. The thing is that I'm seeing crypt() failure here with new glibc 2.10.1 built with nss backend for crypt(), so it would be good to handle such case. (crypt failure was due to improper nss packaging but it could also happen if somehow nss file becomes corrupted) -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

2 1

Re: [Dovecot] Authenticating with /etc/passwd
by June Qiu 21 May '09

21 May '09

it is as displayed --- On Thu, 5/21/09, Charles Marcus <CMarcus(a)Media-Brokers.com> wrote: > From: Charles Marcus <CMarcus(a)Media-Brokers.com> > Subject: Re: [Dovecot] Authenticating with /etc/passwd > To: "June Qiu" <qljune(a)yahoo.com> > Cc: dovecot(a)dovecot.org > Date: Thursday, May 21, 2009, 6:39 PM > On 5/20/2009, June Qiu (qljune(a)yahoo.com) > wrote: > > dovecot -n: > > > > Warning: fd limit 256 is lower than what Dovecot can > use under full load (more than 768). Either grow the limit > or change login_max_processes_count and max_mail_processes > settings > > # OS: SunOS 5.10 sun4u > > info_log_path: /var/log/dovecot.log > > Is the missing version line a copy/paste error? Or did the > warning > obscure it somehow? > > > -- > > Best regards, > > Charles >

2 1

[Dovecot] Authenticating with /etc/passwd
by June Qiu 21 May '09

21 May '09

I am trying to do authentication with /etc/passwd and something is not working right for me. Pls help! When i try to authenticate via pop3, I get: -ERR Authentication failed. In the logs, I get: May 21 11:14:07 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 secured lip=127.0.0.1 rip=127.0.0.1 lport=110 rport=32774 resp=AGp1bmUAU0lORzNlcnQ= May 21 11:14:07 Info: auth(default): passwd(test1,127.0.0.1): lookup May 21 11:14:07 Info: auth(default): passwd(test1,127.0.0.1): Password mismatch May 21 11:14:07 Info: auth(default): passwd(test1,127.0.0.1): CRYPT(password) != 'x' May 21 11:14:09 Info: auth(default): client out: FAIL 1 user=test1 May 21 11:14:17 Info: pop3-login: Disconnected (auth failed, 1 attempts): user=<test1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot -n: Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: SunOS 5.10 sun4u info_log_path: /var/log/dovecot.log protocols: imap pop3 listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): * ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: IMAP ready. login_processes_count: 2 mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd userdb: driver: passwd args: blocking=yes

3 2

[Dovecot] mkdir no permission
by Anna Obertacke 21 May '09

21 May '09

Hallo list-member, Please ignore my bad english. I cant wright bad but i understand well. I reinstalled my server and have big problems with (V 1.1.11) dovecot now. I work with Ubuntu 9.04 Server and want to use pop and imap with easy configuration. I fetch all my Mails on the server and want to look them up by apple Mail. Until yesterday dovecot only worked after I logged in and did something on the server, for example call "mail" oder call "mail.log". After reinstall yesterday it works no more. The new entry in log is "Internal error". Anything else was before yesterday also. My Error Logs: mail.log: May 19 10:00:38 ubuntu dovecot: POP3(annalein): mkdir(/home/annalein/Maildir/cur) failed: Permission denied (euid=1000(annalein) egid=1000(annalein) missing +w perm: /home/ annalein) May 19 10:00:38 ubuntu dovecot: POP3(annalein): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2009-05-19 10:00:38] May 19 10:00:38 ubuntu dovecot: POP3(annalein): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 May 19 10:00:43 ubuntu dovecot: IMAP(annalein): mkdir(/home/annalein/Maildir/cur) failed: Permission denied (euid=1000(annalein) egid=1000(annalein) missing +w perm: /home/ annalein) syslog: May 19 10:22:34 ubuntu dovecot-auth: pam_sm_authenticate: Called May 19 10:22:34 ubuntu dovecot-auth: pam_sm_authenticate: username = [annalein] May 19 10:22:34 ubuntu dovecot-auth: Warning: Using default salt value (undefined in ~/.ecryptfsrc) May 19 10:22:36 ubuntu dovecot-auth: Passphrase key already in keyring; rc = [1] May 19 10:22:36 ubuntu dovecot-auth: ecryptfs_add_passphrase_key_to_keyring: Error adding auth tok with sig [e54db404244691b7] to the keyring; rc = [1] May 19 10:22:36 ubuntu dovecot-auth: Error attempting to add filename encryption key to user session keyring; rc = [1] May 19 10:22:36 ubuntu dovecot-auth: Passphrase key already in keyring; rc = [1] May 19 10:22:36 ubuntu dovecot-auth: ecryptfs_add_passphrase_key_to_keyring: Error adding auth tok with sig [d7f23dd0d7e04b51] to the keyring; rc = [1] May 19 10:22:36 ubuntu dovecot-auth: Error attempting to add passphrase key to user session keyring; rc = [1] May 19 10:22:36 ubuntu dovecot-auth: There is already a key in the user session keyring for the given passphrase. My configuration ist in dovecot-postfix.conf. I can't call it by dovecot -n. But i changed allmost nothing from default- disable_plaintext_auth=no Some points in the file: protocols = imap pop3 imaps pop3s managesieve mail_location = maildir:~/Maildir Please tell what i should show you. Thank you for help. Greetings, Anna Obertacke.

3 5

Re: [Dovecot] Migration questions...
by Richard Hobbs 21 May '09

21 May '09

Hello again, people, I have been reading all of the emails sent back and forth recently, and reading many web pages, and I have a new draft of my migration plan. If anyone has the time and generosity to read through this latest plan for me and let me know if you spot any potential problems with it, i'd really appreciate it. FYI, we're moving from a Debian 3.1/exim/uw-imapd/qpopper/mbox setup to a Debian 5.0/exim/dovecot/maildir setup, and the final version of this document can hopefully become a useful guide for lots of people in future too, if I get it right :-) Anyway... here's the plan... 1. Install Debian with exim, spamassassin, mysqld (for Horde/IMP) and mailman. Use ReiserFS for the indexes and data. XFS would be second choice for filesystem, and this is something of a religious argument, but Dovecot's own page states that ReiserFS is a better choice, and loads of pages on the Internet say that one or the other is better - there's no clear winner, really, so ReiserFS (the FS we already know and trust) wins the battle. 2. Run an online update. 3. Setup IPMI and monitor it from Nagios. 4. Install HotSaNIC to monitor historical system stats. 5. Install and configure Dell OpenManage Server Administrator (or whatever it's called) to monitor hardware, and make sure we will be emailed if a hard drive fails. 6. Rsync homedirs and inboxes onto new server, ready for initial exim configuration. 7. Configure exim as per existing mail server and test that mailing lists and normal email works. You should now have the existing mail delivery solution on the brand new hardware. 8. Configure Spamassassin as per current configuration and test. 9. Configure mailman as per current configuration and test. 10. Once mail delivery is sorted, add "deb http://www.backports.org/debian lenny-backports main contrib non-free" into "/etc/apt/sources.list" and run "aptitude update && aptitude install debian-backports-keyring && aptitude update". 11. Install dovecot (at the time of writing, this was version 1.1.13-2). 12. Run the conversion utility (use "mb2md.py" from http://wiki.dovecot.org/Migration/MailFormat because "convert-tool" doesn't preserve msg UIDs) to convert all existing "mbox" mailboxes into "maildir" mailboxes, for use with Dovecot. 13. Setup exim to use Dovecot's delivery agent ("deliver") so the indexes are updated on mail delivery instead of when the mailbox is requested and also to use the new maildir format. 14. Setup dovecot for IMAP and POP3 and test. *****THIS IS WHERE THE REPEATABLE SECTION BEGINS***** 15. Stop exim and dovecot services. 16. Rsync homedirs and inboxes onto new server again. 17. Run the conversion utility (use "mb2md.py" from http://wiki.dovecot.org/Migration/MailFormat because "convert-tool" doesn't preserve msg UIDs) to convert all existing "mbox" mailboxes into "maildir" mailboxes. 18. Start exim and dovecot services and test SMTP, Spamassassin, mailman, IMAP and POP3. *****THIS IS WHERE THE REPEATABLE SECTION ENDS***** 19. Once everything is working perfectly, send an email to the entire company instructing them what to do after the outage and arrange an outage and do the following steps as soon as the outage begins: a. Unplug DMZ switch from firewall to make delivered mail wait at the sender. b. Stop exim, IMAP, POP3 and dovecot services on both mail servers. c. Rsync homedirs and inboxes onto new server again. d. Run the conversion utility (use "mb2md.py" from http://wiki.dovecot.org/Migration/MailFormat because "convert-tool" doesn't preserve msg UIDs) to convert all existing "mbox" mailboxes into "maildir" mailboxes. e. Start exim and dovecot services and test SMTP, Spamassassin, mailman, IMAP and POP3. f. Reconfigure my own mail client to point to the new mail server (192.168.2.3). g. Reconfigure firewall to think the mail server is now on 192.168.2.3 instead of 192.168.2.2. h. Prepare an email in webmail somewhere in the world, ready to send to a user on our mail server. i. Plug DMZ switch back into firewall and begin monitoring exim logs to check that mail is being delivered. j. Send the email from webmail and check that is goes through exim perfectly and is sitting in the users Inbox. NOTE: We now have a working mail delivery solution! k. Start dovecot IMAP and POP3 and test both. l. Once exim and dovecot are both working against live mailboxes, tell everyone the outage is over. 20. Install and configure Horde & IMP to access email via IMAP. 21. Reconfigure backup script to make sure new server is backed up. 22. Modify Nagios config to monitor new server. 23. DONE! Thanks in advance, everyone! :-) Richard. Brandon Lamb wrote: > On Fri, May 15, 2009 at 5:02 AM, Richard Hobbs > <richard.hobbs(a)crl.toshiba.co.uk> wrote: >> Seth Mattinen wrote: >>> Richard Hobbs wrote: >>>> Seth Mattinen wrote: >>>>> Phillip Macey wrote: >>>>>> On 14/05/2009 5:11 PM, Steffen Kaiser wrote: >>>>>>> On Wed, 13 May 2009, Richard Hobbs wrote: >>>>>>>> The main complaint we have from users is that their IMAP Inbox, with >>>>>>>> 5000 emails in it takes ages to appear, and no amount of coaxing will >>>>>>>> convince them to split their inbox into multiple folders. >>>>>>> Oh, we serve Maildir via Dovecot IMAP and 5000 messages per folder are >>>>>>> a wimp. Problems start if the user: >>>>>> We are having some performancec issues on our server at the moment - all >>>>>> I can put it down to is the large size of some maildirs. Eg. `ls -ld >>>>>> Maildir/cur` might show a directory >20Mb in size for some of our users >>>>>> (20-30k emails). >>>>>> (Performance issues == everything is running ok then all of a sudden >>>>>> load avg goes through the roof, system cpu time goes crazy. Reading mail >>>>>> grinds to a halt. Then everything recovers just as suddenly and the load >>>>>> avg gradually returns to normal levels) >>>>> Are you using ext3 by chance? Vanilla ext3 without directory indexing >>>>> (or whatever it's called) *hates* directories with a lot of files - like >>>>> maildir. Personally, I use XFS, which doesn't suffer from this problem >>>>> since it uses b-trees instead of a table(!) like ext3 does. >>>> This raises another question for me actually... >>>> >>>> We will have one volume for indexes and another volume for data (using >>>> maildir). We will be using the latest stable Debian Linux distro. >>>> >>>> Any opinions on the best filesystem to use? We would normally go >>>> ReiserFS for large volumes, and ext3 for small volumes because of the >>>> unlimited inodes in reiserfs, but i understand that support for that is >>>> beginning to disappear given that Hans Reiser got into a bit of trouble >>>> a few years ago. >>>> >>>> Anyway... that would leave ext3, but is there a better choice i could >>>> make in this instance? We do want performance, of course, but also >>>> complete reliability and resilience when it comes to system crashes >>>> etc... we do *not* want data corruption, and ext3 we know has a very >>>> good journalling and data recovery methods. Well... they're very mature, >>>> anyway. >>>> >>> I used to use ext3, ran into its horrible performance even with >>> directory indexing enabled, went to XFS and never looked back. All of my >>> systems are Debian stable. Reiser3 is part of the kernel so I wouldn't >>> worry about that; Namesys considered it complete and stopped work on it >>> long before the whole murder thing. Both Reiser3 and XFS have worse >>> reputations than ext3, however, I've seen ext3 filesystems hosed beyond >>> repair, too. All my XFS filesystems have battery-backed cache >>> controllers, so it hasn't happened to me yet, hopefully never. ;) One >>> catch with XFS (such as with LVM) to keep in mind is you can't ever >>> shrink it, only grow. >> Trouble is... i've been googling this as well, just now, and loads of >> people say XFS has the better performance, but loads of other people say >> ReiserFS has the better performance. >> >> We have battery backed up RAID controllers too, in this new system, and >> the systems are UPSd, so on that basis i'm still none the wiser! lol >> >> I appreciate your experience with XFS is a positive one, but even the >> dovecot web site says XFS might now be a good choice... >> >> http://wiki.dovecot.org/MailboxFormat/Maildir >> >> What a tough decision! I know it probably won't make too much difference >> in my situation, but i want this to be a very long-term solution, so >> want to do it right first time! >> >> Any other opinions on XFS vs Reiserfs with Dovecot maildir? >> >> Thanks again! >> >> Richard. >> >> >>> ext3 is mature but IMHO completely unsuitable for a busy mail server or >>> any situation where you'll have a bajillion of files in one directory. >>> The exact point at which ext3 will screw you over obviously depends on >>> many factors. But when it happens it'll probably be painful to reformat >>> to something better. >>> >>> ~Seth >>> >>> ______________________________________________________________________ >>> This email has been scanned by the MessageLabs Email Security System. >>> For more information please visit http://www.messagelabs.com/email >>> ______________________________________________________________________ >>> >>> >> -- >> Richard Hobbs (IT Specialist) >> Toshiba Research Europe Ltd. - Cambridge Research Laboratory >> Email: richard.hobbs(a)crl.toshiba.co.uk >> Web: http://www.toshiba-europe.com/research/ >> Tel: +44 1223 436999 Mobile: +44 7811 803377 > > We have been using XFS on our raids for the last few years. We have > fairly new hardware, and using maildir. Delivering over nfs using > exim+dovecot deliver. pop3/imap is near instant load on our webmail. > We have about 16,000 email accounts with ~175 imap+pop3 connections > open all the time. 20 drive sata2 raid 10. amd quad core 9850 with 8 > gigs ram. load sits about 0.30 - 0.45 all day/night. Last I checked > backups were 30-45 minutes, 413 gigs. 6,403,942 files. > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > -- Richard Hobbs (IT Specialist) Toshiba Research Europe Ltd. - Cambridge Research Laboratory Email: richard.hobbs(a)crl.toshiba.co.uk Web: http://www.toshiba-europe.com/research/ Tel: +44 1223 436999 Mobile: +44 7811 803377

2 2

Re: [Dovecot] pop3 gives a permission denied error on chdir
by Kenneth Gonsalves 21 May '09

21 May '09

On Wednesday 20 May 2009 01:20:37 you wrote: > On Tue, 2009-05-19 at 13:35 +0530, Kenneth Gonsalves wrote: > > May 19 09:16:10 greenchilly dovecot: chdir(/home/vmail/example.com/john) > > failed with uid 5000: Permission denied > > .. > > > I have looked at the archives and see that the problem has been reported > > before, but cannot find any solution. Dovecot as LDA has no problem > > accessing and writing mails to the directory as UID 5000. I suspect that > > it is trying to access some other directory and the error message is > > misleading. The directory /home/vmail/example.com/john is owned by user > > vmail with UID 5000. Any clues? > > And all the directories before that are also available for that user? yes > Are you using NFS? Are you using SELinux or something? no > Anyway that > chdir() syscall really failed with that error message. The reason for > that is less clear then.. v1.1+ would give a much nicer error message > here telling exactly what is wrong.. I have installed version 1.1.13, here is the mail log: May 20 10:33:54 greenchilly dovecot: auth(default): new auth connection: pid=1181 May 20 10:34:07 greenchilly dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=pop3^Isecured^Ilip=127.0.0.1^Irip=127.0.0.1^Ilport=110^Irport=42418^Iresp=<hidden> May 20 10:34:07 greenchilly dovecot: auth-worker(default): pam(john(a)example.com,127.0.0.1): lookup service=dovecot May 20 10:34:07 greenchilly dovecot: auth-worker(default): pam(john(a)example.com,127.0.0.1): #1/1 style=1 msg=Password: May 20 10:34:10 greenchilly dovecot: auth-worker(default): pam(john(a)example.com,127.0.0.1): unknown user May 20 10:34:10 greenchilly dovecot: auth(default): sql(john(a)example.com,127.0.0.1): query: SELECT email as user, passwd as password FROM view_users WHERE email='john(a)example.com'; May 20 10:34:10 greenchilly dovecot: auth(default): client out: OK^I1^Iuser=john(a)example.com May 20 10:34:10 greenchilly dovecot: auth(default): master in: REQUEST^I3^I1166^I1 May 20 10:34:10 greenchilly dovecot: auth(default): passwd(john(a)example.com,127.0.0.1): lookup May 20 10:34:10 greenchilly dovecot: auth(default): passwd(john(a)example.com,127.0.0.1): unknown user May 20 10:34:10 greenchilly dovecot: auth(default): master out: USER^I3^Ijohn@example.com^Iuid=5000^Igid=5000^Ihome=/home/vmail/example.com/john May 20 10:34:10 greenchilly dovecot: Fatal: chdir(/home/vmail/example.com/john) failed with uid 5000: Permission denied May 20 10:34:10 greenchilly dovecot: child 1182 (pop3) returned error 89 (Fatal failure) May 20 10:34:10 greenchilly dovecot: pop3-login: Login: user=<john(a)example.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured and here is the session info: lawgon@greenchilly:~$ telnet localhost pop3 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. +OK Dovecot ready. user john(a)example.com +OK pass summersun +OK Logged in. Connection closed by foreign host. -- regards Kenneth Gonsalves Associate NRC-FOSS http://nrcfosshelpline.in/web/

3 7

Re: [Dovecot] Authenticating with /etc/passwd
by June Qiu 21 May '09

21 May '09

Solved. Thanks, Timo! --- On Thu, 5/21/09, Timo Sirainen <tss(a)iki.fi> wrote: > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] Authenticating with /etc/passwd > To: "June Qiu" <qljune(a)yahoo.com> > Cc: dovecot(a)dovecot.org > Date: Thursday, May 21, 2009, 11:31 AM > On Wed, 2009-05-20 at 20:16 -0700, > June Qiu wrote: > > I am trying to do authentication with /etc/passwd and > something is not working right for me. Pls help! > .. > > May 21 11:14:07 Info: auth(default): > passwd(test1,127.0.0.1): CRYPT(password) != 'x' > > /etc/passwd doesn't have passwords nowadays. They're in > /etc/shadow. > Either user passdb shadow or passdb pam. > >

1 0

[Dovecot] compile error with patched dovecot-1.2.rc4
by Carlos Xavier 21 May '09

21 May '09

Hi, I just downloaded the dovecot-1.2.rc4.tar.gz to do some tests. I coud compile it and generate the package with no trouble on my Slackware 12.2.0 Then as I wanted to try the patchs available at http://hg.dovecot.org/dovecot-1.2/# I downloaded them and applied at once. When I tried to compile once again I got this error: cmd-thread.o: In function `cmd_thread': cmd-thread.c:(.text+0x219): undefined reference to `mail_thread_type_parse' ../../src/lib-storage/libstorage.a(mail-search-build.o): In function `search_arg_build': mail-search-build.c:(.text+0x10b9): undefined reference to `mail_thread_type_parse' collect2: ld returned 1 exit status make[3]: *** [imap] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot-1.2.rc4/src/imap' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot-1.2.rc4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot-1.2.rc4' make: *** [all] Error 2 I removed the patched folder and untarred it again, but at this time I decided to apply one patch at time just to see witch one gave me the trouble. When the first set of patch ( http://hg.dovecot.org/dovecot-1.2/rev/d42a8623a008 ) was applied I got the same error. Just to confirm it was this set of patch, I applied all the other set of patchs leaving that one not applied and the compilation went out with no trouble. As im not a expert so I am sending this report to the list in order to get it fixed. Best Regards, Carlos Xavier.

2 2

[Dovecot] Problem with pam/krb5 auth on AIX 5.3
by Jonathan Siegle 20 May '09

20 May '09

I'm using pam to authenticate users against my krb5 realm. Here is the problem scenario: User test2 attempts to login and their password is not expired so dovecot says: 0 login test2 myfavoritepassword 0 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in 1 logout * BYE Logging out 1 OK Logout completed. User test1 attempts to login, but their password is expired. So dovecot says: 0 login test1 myfavoritepassword 0 NO d expired User test2 attempts to login and their password is not expired. But dovecot still says: 0 login test2 myfavoritepassword 0 NO d expired If I kill the pid with name "dovecot-auth -w", user test2 can login just fine unless I login with the user test1 before trying user test2. So it seems like something is getting cached. I'm running imap-login out of inetd, in case that matters. In my dovecot.conf, I don't have any caching/authentication variables activated. I don't see anything obvious to type in passdb pam{ } to type. For debug, I've enable pam for telnet and tested that without error. Also, the logs show that test2 This is dovecot revision 9062:694714d59cd9 . Looking at the logs, I see user test2 authenticate correctly in all instances. thanks, Jonathan

2 2

[Dovecot] %d does not expand to domain
by Giuliano Gavazzi 20 May '09

20 May '09

Hello, dovecot-1.1.7 on FreeBSD 7.1. Usernames have dot in them (like uname.example for a user in example.com) in dovecot.conf I have: mail_location: maildir:/userhomes/maildirs/%d/%n/Maildir and for authentication: username_format: %Ln In the client, tried with CONE and Mail.app, I put the username as: uname.example(a)example.com So, the authentication works fine, as it extracts the uname.example from the uname.example(a)example.com supplied. The mail_location does not: Apr 27 17:21:26 drum dovecot: imap-login: Login: user=<uname.example>, method=PLAIN, rip=88.149.183.86, lip=88.149.202.106, TLS Apr 27 17:21:26 drum dovecot: IMAP(name.example): Effective uid=1301, gid=1301, userhomes=/userhomes/example.com/uname Apr 27 17:21:26 drum dovecot: IMAP(uname.example): Namespace: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes Apr 27 17:21:26 drum dovecot: IMAP(uname.example): maildir: data=/ userhomes/maildirs//uname.example/Maildir Apr 27 17:21:26 drum dovecot: IMAP(uname.example): maildir++: root=/ userhomes/maildirs//uname.example/Maildir, index=, control=, inbox=/ userhomes/maildirs//uname.example/Maildir it looks like the %d expands to the empty string. Could this be due to the "." in the username? Thanks Giuliano

3 12