August 2011 - dovecot

[Dovecot] mbox originally needed 0 bytes, now needs maxint bytes
by Mike Brown 16 Aug '11

16 Aug '11

I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE, amd64. I've long been getting the following in my logs, seemingly at random (so, only sometimes), when I access or move mail into mboxes: Aug 16 00:43:58 myhost dovecot: IMAP(mike): mbox /home/mike/mail/feedback: seq=88 uid=91 uid_broken=0 originally needed 0 bytes, now needs 18446744073709551615 bytes Whatever I'm trying to do always succeeds, but apparently dovecot is confused about something. That number (2^64-1) suggests it has to do with the amd64 architecture. Did a compile option get overlooked? Let me know if there's anything I need to do to get rid of these warnings. Thanks, Mike

1 1

[Dovecot] mbox originally needed 0 bytes, now needs maxint bytes
by Mike Brown 16 Aug '11

16 Aug '11

I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE, amd64. I've long been getting the following kind of messages in my logs, on random occasions when I access or move mail into mboxes: Aug 16 00:43:58 myhost dovecot: IMAP(mike): mbox /home/mike/mail/feedback: seq=88 uid=91 uid_broken=0 originally needed 0 bytes, now needs 18446744073709551615 bytes Whatever I'm trying to do always succeeds, but apparently dovecot is confused about something. That number (2^64-1) suggests it has to do with the amd64 architecture. Did a compile option get overlooked? Thanks for whatever you can suggest. Let me know if you need more info.

1 0

Re: [Dovecot] imap-login aborted login
by Daminto Lie 16 Aug '11

16 Aug '11

Thanks for your reply. Now I can see more info after turning on all those debugs Here it is 2011-08-16 16:16:53 dovecot: Warning: Killed with signal 15 (by pid=7250 uid=0 code=kill) 2011-08-16 16:16:53 dovecot: Info: Dovecot v1.2.9 starting up (core dumps disabled) 2011-08-16 16:16:54 auth(default): Info: new auth connection: pid=7259 2011-08-16 16:16:54 auth(default): Info: new auth connection: pid=7264 2011-08-16 16:16:54 auth(default): Info: new auth connection: pid=7263 2011-08-16 16:16:54 auth(default): Info: new auth connection: pid=7261 2011-08-16 16:16:54 auth(default): Info: new auth connection: pid=7262 2011-08-16 16:16:54 auth(default): Info: new auth connection: pid=7260 2011-08-16 16:18:14 auth(default): Info: client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=32973 resp=AGRsaWUAZGxpZTMyMDU= 2011-08-16 16:18:14 auth-worker(default): Info: pam(msmith,127.0.0.1): lookup service=dovecot 2011-08-16 16:18:14 auth-worker(default): Info: pam(msmith,127.0.0.1): #1/1 style=1 msg=Password: 2011-08-16 16:18:15 auth(default): Info: new auth connection: pid=7271 2011-08-16 16:18:16 auth-worker(default): Info: pam(msmith,127.0.0.1): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: xxx) 2011-08-16 16:18:18 auth(default): Info: client out: FAIL 1 user=msmith 2011-08-16 16:18:23 imap-login: Info: Aborted login (auth failed, 1 attempts): user=<msmith>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Here is my dovecot.conf (Note: I have removed all the comments) ## Dovecot configuration file protocols = imap imaps pop3 pop3s listen = * disable_plaintext_auth = no log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log log_timestamp = "%Y-%m-%d %H:%M:%S " login_user = postfix login_greeting = Dovecot IMAP server! mail_location = maildir:~/Maildir mail_privileged_group = mail mail_debug = yes verbose_proctitle = yes protocol imap { login_executable = /usr/lib/dovecot/imap-login mail_executable = /usr/lib/dovecot/imap imap_client_workarounds = outlook-idle delay-newmail netscape-eoh tb-extra-mailbox-sep } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol managesieve { } protocol lda { postmaster_address = hostname = ubuntuserver sendmail_path = /usr/lib/sendmail rejection_subject = Rejected: %s rejection_reason = Your message to <%t> was automatically rejected:%n%r auth_socket_path = /var/run/dovecot/auth-master } auth_username_format = %Lu auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = mail group = mail } client { path = /var/spool/postfix/private/auth-client mode = 0660 user = postfix group = postfix } } !include_try /etc/dovecot/auth.d/*.auth } dict { } plugin { } # Config files can also be included. deliver doesn't support them currently. #!include /etc/dovecot/conf.d/*.conf # Optional configurations, don't give an error if it's not found: !include_try /etc/dovecot/conf.d/*.conf #!include_try /etc/dovecot/extra.conf I think the issue is with PAM authentication. How do I configure the PAM authentication? Any help would be much appreciated. Thank you ________________________________ From: CopalFreak <copalfreak(a)gmail.com> To: Daminto Lie <dlie76(a)yahoo.com.au> Sent: Tuesday, 16 August 2011 3:39 PM Subject: Re: [Dovecot] imap-login aborted login You might try turning on the various DEBUG modes in Dovecot. In your dovecot.conf file : Something like this : ------------------------------------- auth_debug = yes auth_debug_passwords = yes auth_verbose - yes verbose_proctitle = yes mail_debug = yes log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot-deliver.log ------------------------------------- After edit, restart dovecot. Then tail your log (tail -f /var/log/dovecot-deliver.log) while attempting to check mail. You should see a bit more info that might help. (be sure to turn it all back off. it will sometimes log the passwords and when using plaintext, thats bad.) Hope this helps, -=*CopalFreak*=- On 8/16/2011 12:19 AM, Daminto Lie wrote: > Hi, > > I have been trying to set up Apache2, Postfix, Dovecot, openLDAP and squirrelmail on my Ubuntu Server 10.04 machine. The idea is to make use of the LDAP to authenticate users to login to squirrelmail to send/receive emails. > > I have been using the link - https://help.ubuntu.com/community/Postfix/DovecotLDAP, as a guide to get it all set up. I have checked the status for postfix and dovecot, and they both are up and running by using telnet. I have even installed openldapadmin to check and see if I've got the ldap working. I could login to openldapadmin and saw myself there with uid=msmith. > > I have also installed squirrelmail as my webmail. After all that installed, I went to localhost/squirrelmail on the firefox browser. It would not log me in. > > Later I found in the /var/log/dovecot-deliver.log file, I saw the following messages > dovecot: Info: Dovecot v1.2.9 starting up (core dumps disabled) > imap-login: Info: Aborted login (auth failed, 1 attempts): user=<msmith>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured > imap-login: Info: Aborted login (auth failed, 1 attempts): > user=<msmith(a)mycompany.com.au>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured > > imap-login: Info: Aborted login (auth failed, 1 attempts): > user=<mike.smith(a)mycompany.com.au>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured > > I tried to login with three different usernames but none worked as shown above in the log file. I wonder if it is to do with method=PLAIN and secured. > > Any help would be greatly appreciated. > > Thank you >

1 0

[Dovecot] imap-login aborted login
by Daminto Lie 16 Aug '11

16 Aug '11

Hi, I have been trying to set up Apache2, Postfix, Dovecot, openLDAP and squirrelmail on my Ubuntu Server 10.04 machine. The idea is to make use of the LDAP to authenticate users to login to squirrelmail to send/receive emails. I have been using the link - https://help.ubuntu.com/community/Postfix/DovecotLDAP, as a guide to get it all set up. I have checked the status for postfix and dovecot, and they both are up and running by using telnet. I have even installed openldapadmin to check and see if I've got the ldap working. I could login to openldapadmin and saw myself there with uid=msmith. I have also installed squirrelmail as my webmail. After all that installed, I went to localhost/squirrelmail on the firefox browser. It would not log me in. Later I found in the /var/log/dovecot-deliver.log file, I saw the following messages dovecot: Info: Dovecot v1.2.9 starting up (core dumps disabled) imap-login: Info: Aborted login (auth failed, 1 attempts): user=<msmith>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured imap-login: Info: Aborted login (auth failed, 1 attempts): user=<msmith(a)mycompany.com.au>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured imap-login: Info: Aborted login (auth failed, 1 attempts): user=<mike.smith(a)mycompany.com.au>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured I tried to login with three different usernames but none worked as shown above in the log file. I wonder if it is to do with method=PLAIN and secured. Any help would be greatly appreciated. Thank you

1 0

[Dovecot] Last login script
by Munroe Sollog 15 Aug '11

15 Aug '11

I am trying to implement a last login script, however I seem to be having lots of issues. We started with sqlite but we were having locking issues, so we moved to postgresql which seems to have alleviated database specific issues, but now people are complaining about randomly not being able to log in. I don't see any real errors in the logs (dovecot or postgresql) to explain their complaints though, all I am really getting is "Connection closed" here is the log line of a failed attempt (with debug output): http://pastebin.com/5RFgVa8V and here is what we are running as the 'mail executable': http://pastebin.com/L0ibyqSQ Any help would be greatly appreciated, thanks. Munroe Sollog Digirati Consulting sollog(a)digiraticonsulting.com (610) 332-7234 x805

1 0

[Dovecot] LMTP over STDIN/STDOUT (non root user)
by Andrzej Adam Filip 15 Aug '11

15 Aug '11

Is it possible to get LMTP session over STDIN/STDOUT (for non root user)? I have configured dovecot to allow "server less" access to my mailbox using IMAP over STDIN/STDOUT. I would like to complete the setup by making fetchmail deliver fetched messages via LMTP over STDIN/STDOUT. -- [pl>en: Andrew] Andrzej Adam Filip : anfi(a)onet.eu There is only one way to kill capitalism -- by taxes, taxes, and more taxes. -- Karl Marx

3 6

[Dovecot] [PATCH] net_connect_*(): Wait for fd to complete connect(2) when fd is non-blocking
by SATOH Fumiyasu 15 Aug '11

15 Aug '11

Hi, Dovecot ignores EINPROGRESS on connect(2) for non-blocking fd. This is wrong. After that, read(2) to fd (or write(2) to fd) fails with ENOTCONN if the connection of fd is not completed. The attached patch fixes this problem. -- -- Name: SATOH Fumiyasu (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- Personal Home: http://www.SFO.jp/blog/

2 4

[Dovecot] Blocking auth services
by Peter Mogensen 15 Aug '11

15 Aug '11

Hi, I'm writing an passdb/userdb plugin to authenticate against an external daemon listening on a UNIX socket. The connection to the daemon is 1 request at a time and thus blocking (unlike passdb-ldap), but the daemon is preforking, so it can handle more connections at a time. I read from the Wiki: http://wiki2.dovecot.org/Design/AuthProcess * "The authentication may begin new authentication requests even before the existing ones are finished. ", and * "If the passdb uses connections to external services, it's preferred that they use non-blocking connections. Dovecot does this whenever possible (PostgreSQL and LDAP for example). If it's not possible, set blocking = TRUE. " ... which tells me to set the module as blocking and let more auth worker processes do the work - creating 1 daemon process for each auth worker process, I guess. But I also have the option, to let the passdb/userdb plugin maintain a pools of used/idle connections to the daemon and just pick a idle connection and moving it to the used pool on each auth_request. Which would save me the auth worker processes. Is there a preferred dovecot way? /Peter

2 2

[Dovecot] Parallel auth
by Bernhard Schmidt 15 Aug '11

15 Aug '11

Hello, we run a Dovecot 2.0.13 instance purely as SASL backend for Postfix, authenticating against a local passwd-file and our central LDAP database. # dovecot -n # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.36-0.5-default x86_64 SUSE Linux Enterprise Server 11 # (x86_64) auth_mechanisms = plain login auth_verbose = yes passdb { args = /etc/dovecot/dovecot-passwd driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap-simauth.conf.ext driver = ldap } protocols = none service auth { unix_listener /var/spool/postfix-postout/private/auth { group = postfix mode = 0660 user = postfix } } ssl = no There is only a single user in the passwd-file for monitoring. We monitor authentication delays for both this local user and one user from LDAP. Due to a firmware bug, our six-figures NAS causes extremely high LDAP delays (in the range of 20-60 seconds, instead of the usual 50ms) once an hour. The weird thing is, I also see these delays in the graph for the local user. Which got me thinking * are authentication requests handled serially by dovecot/auth? * any way to solve this situation for the local user (not to be blocked by the delayed LDAP query)? * any way to solve this situation for LDAP users? We could possibly do some loadbalancing if the auth-daemon opened several LDAP connections Thanks, Bernhard

2 1

[Dovecot] migration from courier to dovecot
by Michael 15 Aug '11

15 Aug '11

hi all I have a problem with the conversion of files containing UIDL Courier to dovecot uidl , dovecot version is 1.2.15 , format in dovecot is pop3_uidl_format = %08Xu%08Xv i try any other from available list without success courierpop3dsizelist format /2 920 1290084761 1296206202.H818256P31717.domain.tld,S=57135:2,S 57679 87:1290084761 1296239411.H289216P22896.domain.tld,S=1660:2,S 1694 88:1290084761 1296480156.H578502P4335.domain.tld,S=26610:2,S 26995 89:1290084761 1296552510.H517452P28309.domain.tld,S=2894:2,S 2980 90:1290084761 1296740128.H139710P22101.domain.tld,S=4983:2,S 5121 91:1290084761 1296807457.H887067P13955.domain.tld,S=7841:2,S 8038 92:1290084761 1296807652.H904999P14102.domain.tld,S=114839:2,S 116421 93:1290084761 courierimapuiddb 1 1290084574 847 53 1296206202.H818256P31717.domain.tld,S=57135 54 1296239411.H289216P22896.domain.tld,S=1660 55 1296480156.H578502P4335.domain.tld,S=26610 56 1296552510.H517452P28309.domain.tld,S=2894 57 1296740128.H139710P22101.domain.tld,S=4983 58 1296807457.H887067P13955.domain.tld,S=7841 59 1296807652.H904999P14102.domain.tld,S=114839 and after using a script to convert from http://www.dovecot.org/tools/courier-dovecot-migrate.pl got this file dovecot-uidlist 3 V1290084574 N862 53 PUID87-1290084761 W57679 :1296206202.H818256P31717.domain.tld,S=57135:2,S 54 PUID88-1290084761 W1694 :1296239411.H289216P22896.domain.tld,S=1660:2,S 55 PUID89-1290084761 W26995 :1296480156.H578502P4335.domain.tld,S=26610:2,S 56 PUID90-1290084761 W2980 :1296552510.H517452P28309.domain.tld,S=2894:2,S 57 PUID91-1290084761 W5121 :1296740128.H139710P22101.domain.tld,S=4983:2,S 58 PUID92-1290084761 W8038 :1296807457.H887067P13955.domain.tld,S=7841:2,S 59 PUID93-1290084761W116421:1296807652.H904999P14102.domain.tld,S=114839:2,S Unfortunately, messages are downloaded to the client again and with over 300 account its problematic if someone would be willing and able to help I will be grateful , i don't have any idea what next can do with it ;( if any other information would be helpful please let me know

2 5