Re: [Dovecot] Dovecot+PostfixAdmin+PostgreSQL on FreeBSD 7
Timo Sirainen wrote: The rc.d/dovecot script is broken then. I don't run FreeBSD so I don't really know why. I'd suggest trying to figure out what it does differently than simply running dovecot does. I running Dovecot 1.1.3 on FreeBSD-7.0-p5 with Exim without any problem. All from ports. Just for information what it is not a FreeBSD related problem. -- Best regards, Proskurin Kirill
Re: [Dovecot] dovecot 1.2: SEGV in acl plugin when selecting a shared mailbox
Timo Sirainen [EMAIL PROTECTED] writes: On Thu, 2008-10-23 at 13:25 +0200, Sascha Wilde wrote: Hi Timo, there is a bug in the acl plugin (in head, _without_ our acl changes), which causes an segfault on selecting a shared folder. * OK [CAPABILITY ...] Dovecot ready. x login [EMAIL PROTECTED] secret x OK [CAPABILITY ...] Logged in y select users/[EMAIL PROTECTED]/INBOX/bla - Peer has closed the GNUTLS connection Fixed: http://hg.dovecot.org/dovecot-1.2/rev/8553bb4c53ad Confirmed. Many thanks once again... :) cheers sascha -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner pgpk59UvuxfVr.pgp Description: PGP signature
[Dovecot] service imaps.
In dovecot.conf protocol imaps is set to port 10943. ssl_listen = *:10943 The standard port for imaps is 993. So why it is set to 10943?
Re: [Dovecot] regarding dovecot.index.cache
Timo Sirainen wrote: On Mon, 2008-10-20 at 12:05 +0530, Dhaval Thakar wrote: Error: Corrupted header in file /home/vpopmail/domains/arch.xyz.com/A/mailadmin/Maildir/dovecot-uidlist (version = 3) I think you're using an old deliver from Dovecot v1.0.x. There's no such error message as this in v1.1.4. thank you sir, with your proper direction I have dovecot deliver working for my mail server this problem got solved once I uninstalled install dovecot-1.1.5 (before reinstallation I remove deliver manually, I think I had not uninstalled older 1.0 while upgrading to ver 1.1) this is working fine with my existing system.
Re: [Dovecot] Possible header parsing problem
Timo Sirainen wrote: But I'm not sure if I should convert the following TAB to a space. UW-IMAP seems to do that, but RFC just says that the CRLF should be dropped. As pointed out in https://bugzilla.mozilla.org/show_bug.cgi?id=240924#c7, this could lead to strange behaviour. So I'd vote for replacing the folding tab to a space.
Re: [Dovecot] Possible header parsing problem
On Oct 24, 2008, at 12:35 PM, Jakob Hirsch wrote: Timo Sirainen wrote: But I'm not sure if I should convert the following TAB to a space. UW-IMAP seems to do that, but RFC just says that the CRLF should be dropped. As pointed out in https://bugzilla.mozilla.org/show_bug.cgi? id=240924#c7, this could lead to strange behaviour. So I'd vote for replacing the folding tab to a space. Actually Dovecot already replaces all tabs to spaces when sending ENVELOPE, BODY and BODYSTRUCTURE replies. The only issue here is about the internal parsing where I think it's better to be strict. PGP.sig Description: This is a digitally signed message part
[Dovecot] dovecot deliver mail bounce problem
Hi list, I am using dovecot deliver for the local mail delivery with qmail. this is working fine. but when mail is sent to invalid user, it gets bounced back with error I'm not going to try again; this message has been in the queue too long. rather no mailbox here by that name I could find proper solution, kindly guide to resolve it. /var/log/maillog Oct 24 23:03:27 backup dovecot: auth(default): master in: USER 1 [EMAIL PROTECTED] service=deliver Oct 24 23:03:27 backup dovecot: auth(default): vpopmail([EMAIL PROTECTED]): lookup user=d domain=arch.xyz.com Oct 24 23:03:27 backup dovecot: auth(default): vpopmail([EMAIL PROTECTED]): unknown user Oct 24 23:03:27 backup dovecot: auth(default): prefetch([EMAIL PROTECTED]): passdb didn't return userdb entries, trying the next userdb Oct 24 23:03:27 backup dovecot: auth(default): master out: NOTFOUND 1 no logs in /var/log/dovecot-deliver.log following is the configuration .qmail-default |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -n -e -d [EMAIL PROTECTED] dovecot -n # 1.1.5: /etc/dovecot/dovecot.conf protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: mail ready. mail_plugins: quota imap_quota trash imap_client_workarounds: delay-newmail outlook-idle namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: checkpassword args: /home/vpopmail/bin/vchkpw userdb: driver: vpopmail userdb: driver: prefetch socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vpopmail group: vchkpw plugin: quota: maildir quota_rule: Trash:ignore
Re: [Dovecot] Possible header parsing problem
Timo Sirainen wrote: lead to strange behaviour. So I'd vote for replacing the folding tab to a space. Actually Dovecot already replaces all tabs to spaces when sending ENVELOPE, BODY and BODYSTRUCTURE replies. The only issue here is about the internal parsing where I think it's better to be strict. Oh, ok, then I got that wrong. I only wonder why I still see tabs in the Subject field in TB's message list (and in other lines in message source). Using v1.2.alpha3.
Re: [Dovecot] Possible header parsing problem
On Fri, 2008-10-24 at 14:37 +0200, Jakob Hirsch wrote: Timo Sirainen wrote: lead to strange behaviour. So I'd vote for replacing the folding tab to a space. Actually Dovecot already replaces all tabs to spaces when sending ENVELOPE, BODY and BODYSTRUCTURE replies. The only issue here is about the internal parsing where I think it's better to be strict. Oh, ok, then I got that wrong. I only wonder why I still see tabs in the Subject field in TB's message list (and in other lines in message source). Using v1.2.alpha3. Because TB most likely doesn't use ENVELOPE but parses the headers itself. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] New generic userdb lookup api (was: New userdb backend for checkpassword like programs)
Timo Sirainen [EMAIL PROTECTED] writes: Hmm. auth-client.c is about performing authentication as a client. What you're doing is about doing a userdb lookup and connecting to dovecot-auth as a master. So different file, but I'm not really sure about the name. Perhaps auth-master.c and auth_master_init/deinit() auth_master_user_lookup() function? Ok, I used auth-master.* -- the new code is in changeset f5ce17153a3d in my kolab-branch at http://hg.intevation.org/kolab/dovecot-1.2_kolab-branch/ and I made deliver use it in 94b00e377a25. I had no time for thorough testing, but in my test-setup it seems to work like before, so at least I didn't break it completely... ;-) Now I have to go back and finally implement the %%h feature for shared name spaces. cheers sascha -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner pgp2KZnfTlYwn.pgp Description: PGP signature
[Dovecot] Maildir connection issues
I recently am attempting a mbox to Maildir conversion, initially for a single email address, and then for everyone. To further this diagnostic here is the dovecot -n: dovecot -n # 1.1.4: /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: SpamZapper Email ready. mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: username_format: %Lu passdb: driver: passwd-file args: /home/dovecot.passwd passdb: driver: pam userdb: driver: passwd ns6.ABS-CompTech.com root [/root] ll /home/dovecot.passwd -rw-r--r-- 1 418 418 95 Oct 22 22:18 /home/dovecot.passwd The problem I am having is that the user health cannot get new email messages. Suggestions? -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ABS Computer Technology, Inc. http://www.ABS-CompTech.com - Email, Internet and Security Consultants SPAMZapper http://www.Spam-Zapper.com - No-JunkMail.com http://www.No-JunkMail.com - *True Spam Elimination*.
Re: [Dovecot] dovecot deliver mail bounce problem
Dhaval Thakar a écrit : Hi list, I am using dovecot deliver for the local mail delivery with qmail. this is working fine. but when mail is sent to invalid user, it gets bounced back with error I'm not going to try again; this message has been in the queue too long. rather no mailbox here by that name if there is no mailbox here by that name, then you should reject at smtp time (in your MTA: postfix, sendmail, whatever). do not bounce after accepting mail. Search for backscatter to learn more. I could find proper solution, kindly guide to resolve it. /var/log/maillog Oct 24 23:03:27 backup dovecot: auth(default): master in: USER 1 [EMAIL PROTECTED] service=deliver Oct 24 23:03:27 backup dovecot: auth(default): vpopmail([EMAIL PROTECTED]): lookup user=d domain=arch.xyz.com Oct 24 23:03:27 backup dovecot: auth(default): vpopmail([EMAIL PROTECTED]): unknown user Oct 24 23:03:27 backup dovecot: auth(default): prefetch([EMAIL PROTECTED]): passdb didn't return userdb entries, trying the next userdb Oct 24 23:03:27 backup dovecot: auth(default): master out: NOTFOUND 1 no logs in /var/log/dovecot-deliver.log following is the configuration .qmail-default |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -n -e -d [EMAIL PROTECTED] dovecot -n # 1.1.5: /etc/dovecot/dovecot.conf protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: mail ready. mail_plugins: quota imap_quota trash imap_client_workarounds: delay-newmail outlook-idle namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: checkpassword args: /home/vpopmail/bin/vchkpw userdb: driver: vpopmail userdb: driver: prefetch socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vpopmail group: vchkpw plugin: quota: maildir quota_rule: Trash:ignore
Re: [Dovecot] Maildir connection issues
Albert E. Whale a écrit : I recently am attempting a mbox to Maildir conversion, initially for a single email address, and then for everyone. To further this diagnostic here is the dovecot -n: dovecot -n # 1.1.4: /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: SpamZapper Email ready. mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u so you're still using mbox. mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: username_format: %Lu passdb: driver: passwd-file args: /home/dovecot.passwd passdb: driver: pam userdb: driver: passwd ns6.ABS-CompTech.com root [/root] ll /home/dovecot.passwd -rw-r--r-- 1 418 418 95 Oct 22 22:18 /home/dovecot.passwd The problem I am having is that the user health cannot get new email messages. Suggestions?
Re: [Dovecot] New generic userdb lookup api
On Fri, 2008-10-24 at 16:19 +0200, Sascha Wilde wrote: Timo Sirainen [EMAIL PROTECTED] writes: Hmm. auth-client.c is about performing authentication as a client. What you're doing is about doing a userdb lookup and connecting to dovecot-auth as a master. So different file, but I'm not really sure about the name. Perhaps auth-master.c and auth_master_init/deinit() auth_master_user_lookup() function? Ok, I used auth-master.* -- the new code is in changeset f5ce17153a3d in my kolab-branch at http://hg.intevation.org/kolab/dovecot-1.2_kolab-branch/ and I made deliver use it in 94b00e377a25. I had no time for thorough testing, but in my test-setup it seems to work like before, so at least I didn't break it completely... ;-) A couple of things: 1. It disconnects after each lookup. Not good if multiple lookups are done. Then again it probably shouldn't keep the connection alive forever since the imap connections can run for ages and most of the necessary lookups are probably done close to each others. Maybe timeout after 1 minute of idling? 2. conn-to is for auth request timeout. It should be removed after io_loop_run() so if 1. is fixed it won't leak timeouts. (The same conn-to could actually be used for the two timeouts - one value when looking up, another value when idling.) 3. Would be nice to get rid of the getenv()s :) The MAIL_CHROOT handling could be moved to deliver (use it if reply-chroot == NULL). The debug could be a parameter to auth_master_init(). 4. You're leaking memory. Cleanest fix would be to add pool_t pool parameter to auth_master_user_lookup() and allocate memory only from it (also p_array_init(reply-extra_fields) would be cleaner to do inside the lookup code than require it to be done externally). signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Maildir connection issues
mouss wrote: Albert E. Whale a écrit : I recently am attempting a mbox to Maildir conversion, initially for a single email address, and then for everyone. To further this diagnostic here is the dovecot -n: dovecot -n # 1.1.4: /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: SpamZapper Email ready. mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u so you're still using mbox. I was under the impression that you could migrate individual mailboxes and set up the information via the dovecot.passwd file, i.e. health:$1$MCtvt/Tz$FmKqU/cbWlBhKnhc5W.Ko.:1152:1152:/home/health:userdb_mail=maildir:~/Maildir Is this not valid? How do I set up individual Mailboxes for Maildir until I have them converted? -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ABS Computer Technology, Inc. http://www.ABS-CompTech.com - Email, Internet and Security Consultants SPAMZapper http://www.Spam-Zapper.com - No-JunkMail.com http://www.No-JunkMail.com - *True Spam Elimination*.
Re: [Dovecot] Maildir connection issues
On Oct 24, 2008, at 8:40 PM, Albert E. Whale wrote: I was under the impression that you could migrate individual mailboxes and set up the information via the dovecot.passwd file, i.e. health:$1$MCtvt/Tz$FmKqU/cbWlBhKnhc5W.Ko.:1152:1152:/home/ health:userdb_mail=maildir:~/Maildir Is this not valid? That looks ok, but: passdb: driver: passwd-file args: /home/dovecot.passwd passdb: driver: pam userdb: driver: passwd You're using passwd-file only as passdb. That means it uses only the username and password field of the file. You'll need to use it as a userdb also. But can the users read their mail anyway? You said that they can't get new mails. Are you using Dovecot's deliver as MDA? PGP.sig Description: This is a digitally signed message part
[Dovecot] Bug in QRESYNC SELECT/EXAMINE behavior
RFC 5162 [3.1] states that a QRESYNC should return all changes in a SELECT/EXAMINE since the given modseq. In the following case, it looks like there is an off-by-1 error somewhere: C: A64 SELECT TestMailboxTest (QRESYNC (1224531494 6 1,3:5)) [MMS: MODSEQ given is 6] S: * OK [CLOSED] S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) S: * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. S: * 4 EXISTS S: * 0 RECENT S: * OK [UNSEEN 1] First unseen. S: * OK [UIDVALIDITY 1224531494] UIDs valid S: * OK [UIDNEXT 6] Predicted next UID S: * OK [HIGHESTMODSEQ 6] [MMS: HIGHESTMODSEQ is 6 - the same as our cache, so there should be no need for an update] S: * 2 FETCH (MODSEQ (6) UID 3 FLAGS (\Deleted)) [MMS: ...but we get this FETCH that contains the MODSEQ ID of 6, which we have already told the server we are aware of] S: A64 OK [READ-WRITE] Select completed. In other words, I don't think that 2 FETCH ... should be in the server response - it is duplicative information as to what is already cached on the client. michael
Re: [Dovecot] Bug in QRESYNC SELECT/EXAMINE behavior
On Oct 24, 2008, at 9:58 PM, Michael M. Slusarz wrote: RFC 5162 [3.1] states that a QRESYNC should return all changes in a SELECT/EXAMINE since the given modseq. In the following case, it looks like there is an off-by-1 error somewhere: Thanks, fixed: http://hg.dovecot.org/dovecot-1.2/rev/66a792567e59 I guess I confused it with CONDSTORE's UNCHANGEDSINCE behavior. PGP.sig Description: This is a digitally signed message part
[Dovecot] dovecot:mail storage creation failed with mail location:mbox:/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_USERDB/mail:INBOX=/var/spool/mail/[EMAIL PROTECTED]
Hello I am working in a project and during my work an error has appeared in the use of the dovecot e mail server Squirrelmail an error occured:ERROR:Connection dropped by IMAP server and in the log mail we find: mail storage creation failed with mail location:mbox:/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_USERDB/mail:INBOX=/var/spool/mail/[EMAIL PROTECTED] child 5757(imap) returned error 89 can you give me a help i am waiting your response impatiently thanks
Re: [Dovecot] Maildir connection issues
Timo Sirainen wrote: On Oct 24, 2008, at 8:40 PM, Albert E. Whale wrote: I was under the impression that you could migrate individual mailboxes and set up the information via the dovecot.passwd file, i.e. health:$1$MCtvt/Tz$FmKqU/cbWlBhKnhc5W.Ko.:1152:1152:/home/health:userdb_mail=maildir:~/Maildir Is this not valid? That looks ok, but: passdb: driver: passwd-file args: /home/dovecot.passwd passdb: driver: pam userdb: driver: passwd You're using passwd-file only as passdb. That means it uses only the username and password field of the file. You'll need to use it as a userdb also. But can the users read their mail anyway? You said that they can't get new mails. Are you using Dovecot's deliver as MDA? ok, being that I've never done this before, how do I fix this? The users cannot find the Email in the Maildir because the setting is not read. Clues? -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ABS Computer Technology, Inc. http://www.ABS-CompTech.com - Email, Internet and Security Consultants SPAMZapper http://www.Spam-Zapper.com - No-JunkMail.com http://www.No-JunkMail.com - *True Spam Elimination*.
[Dovecot] FTS index generation
Hi folks. I'm experimenting with the Squat plugin. I can execute search commands via direct interaction with IMAP, but I never see the expected dovecot.index.search index file appear in the spool. I'm concerned that I've misconfigured something that is preventing the creation of those indices. Is there a facility to have the squat plugin generate debugging messages so I can see what it's doing? Thanks, -Dave -- Dave McGuire Ahh, you voted for Bush? Port Charlotte, FL Happy now?
