- dovecot - dovecot.org

[Dovecot] Help! OT: Blackberry IMAP client suggestions/experience needed
by Stewart Dean 14 Mar '08

14 Mar '08

The CFO of our college, a most formidable man, had decided to go Blackberry and Something Functional Must Be Done. We've had some users who we've not supported (and things got better for them when we switched from UWIMAP to Dovecot). BB, of course, has their half-baked sorta-IMAP-compliant client (and we do NOT want the BB Enterprise Server) that persistently keeps grabbing the mailbox and breaking the mailbox lock, causing no end of grief for the secretaries (plural, more than one) would also work with the mailbox. 1) Does anyone have recommendations and experience with a genuine BB IMAP client? Googling shows up LogicMail.... 2) I have been avoiding the plunge in multiple-access mailbox and just let the early BB adapter users thrash but I suppose it is time to do what I can with DC. We are running 1.0.12 with mbox format. Would some kind person <grovel,grovel> tell me where I should start reading plus any warnings. BB DC experience info would be a big help. Our CFO has a legendary temper and I would like to get as much as possible right the first time out........... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

11 21

[Dovecot] Feature request: dovecot -d option to output only/all 'defaults' of current version
by Charles Marcus 14 Mar '08

14 Mar '08

It would be nice to be able to do 'dovecot -d' that outputs only/all of the 'default' values of the currently running version, regardless of what is explicitly set. Postfix currently has this option, and it is very useful for one thing... to compare settings that have been explicitly set to what would be the default values. I used this recently on a postfix install to remove a whole bunch of values that had been explicitly set, and therefore showed up when postconf -n command was issued - but that would have been the default values anyway had they not been explicitly set - thus providing a much cleaner postconf -n output. Thanks Timo for dovecot!! -- Best regards, Charles

1 0

[Dovecot] Hardlinking with Sieve
by Anders 14 Mar '08

14 Mar '08

I have a simple Sieve rule to protect me from accidentally deleting mail: fileinto :copy "backup"; Should I expect this backup to be hardlinked to the ordinary one? Obviously, that would make the backup be almost for free in terms of storage, but currently I do not see any linking. Using Maildir, by the way, and I have not touched the maildir_copy_with_hardlinks setting. TIA, Anders.

2 1

[Dovecot] A message, when moved by multiple clients with same account and same filters, can be duplicated by filters on destination imap folder.
by Diego Liziero 14 Mar '08

14 Mar '08

I'm still collecting user feedback after moving from uw-imap to dovecot development release 1.1.rc3. What said in the subject seems the obvious result of an improper configuration. Office emails are configured and accessed on multiple clients with the same automatic filters, and sometimes the filtered emails get duplicated on the destination folder. The fact is that this was perfectly working with wu-imap (without any duplication/triplication of emails). I'm looking if there is some workaround to keep this client misuse working with dovecot. Could an email have a sort of "primary key" that forbids it's duplication in the same imap folder? Regards, Diego.

3 2

[Dovecot] LDA log_path
by jalal 13 Mar '08

13 Mar '08

Hi all I've just transferred a server from one machine to another. The only remaining dovecot problem I have is that the dovecot deliver program isn't writing a log file. I have this in the conf file: protocol lda { ..... mail_plugins = cmusieve mail_plugin_dir = /usr/lib64/dovecot/lda ..... # setup log files: log_path = /var/log/dovecot-deliver.log } but that file doesn't get written. The dovecot.log and dovecot_info.log files do get written and I've tried creating/touching the deliver log, but that doesn't seem to help at all. If I don't create /var/log/dovecot-deliver.log it doesn't get created by dovecot. If I use 'log_path = /tmp/dovecot-deliver.log' the file will get created but will remain empty. Anyone have an idea on how I can track this down? I like to have logs :) dovecot 1.0.12, CentOS 5/64 bit on a Virtuozzo VPS. TIA

1 0

[Dovecot] imap sent-mail folder sometimes dosen't get updated when used by more than a mailer at the same time.
by Diego Liziero 13 Mar '08

13 Mar '08

Hi, I'm collecting users feedback of latest dovecot 1.1.rc3 development release. Some users are complaining that their sent mails sometimes don't get written to imap Sent-mail folder. It seems that all these users were using multiple istances of imap processes to read their mail (thunderbird+horde-imp, evolution+horde-imp or multiple thunderbird istances). No error message is written in dovecot.log, no user feedback in horde-imp/evolution. Only thunderbird says it can't update Sent folder. Has anyone had similar issues? Diego.

6 10

[Dovecot] outlook2003 fails sasl authentication
by Johan Hendriks 13 Mar '08

13 Mar '08

Hello all i have postfix running with dovecot-sasl and mysql as a backend. It all runs good. I run into trouble as where outlook 2003 fails to authenticate when sending e-mail. I have thunderbird outlook2007 and 2003 clients. The tunderbird and 2007 clients are working OK, the outlook2003 client get the relay access denied message. In the postfix log i see it is not initiating sasl they all use pop i use dovecot 1.0.13 this is my posfix part of sasl smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks broken_sasl_auth_clients = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination permit smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth and this is my dovecot sasl part # dovecot SASL socket listen { client { # Assuming the default Postfix $queue_directory setting path = /var/spool/postfix/private/auth mode = 0660 # Assuming the default Postfix user and group user = postfix group = postfix } } Am i doing something wrong? I guess if it is not configured right outlook 2007 and thunderbird will fail also! regards, Johan Hendriks

3 4

[Dovecot] interesting note - not sure just how to take care of this one
by Joseph Norris 12 Mar '08

12 Mar '08

Hello all, the dovecot -> ldap connection is working correctly but I notice something in my maillog that is disturbing: dovecot.conf in the passdb section I have passdb passwd { } then it drops down into the ldap stuff. The user gets validated via this first and if it fails passes on to the ldap stuff. the problem is: in the file the user's unencrypted password is showing up as follows: Mar 12 11:24:41 malaga dovecot: auth(default): pam(jnorris,XXX.XXX.XXX.XXX): pam_authenticate() failed: Authentication failure Mar 12 11:24:41 malaga dovecot: auth(default): passwd(jnorris,XXX.XXX.XXX.XXX): lookup Mar 12 11:24:41 malaga dovecot: auth(default): passwd(jnorris,XXX.XXX.XXX.XXX): Password mismatch Mar 12 11:24:41 malaga dovecot: auth(default): passwd(jnorris,XXX.XXX.XXX.XXX): CRYPT("the uncrypted password in plain text here") != 'x' is there a way to disable this? thanks. -- Cell: 209.201.3410 Desk: 209.228.4576 email: jnorris(a)ucmerced.edu #Joseph Norris (Linux/Apache/Mysql/Perl - what else is there?) print @c=map chr $_+100,(6,17,15,16,-68,-3,10,11, 16,4,1, 14,-68,12,1,14,8, -68,4,-3,-1,7,1,14,-68, -26,11,15,1,12, 4,-68,-22,11,14,14,5,15,-90);

2 1

[Dovecot] IMAP storage - mail_location = maildir:~/Maildir:mbox:~/mail/
by Tim Alberts 12 Mar '08

12 Mar '08

I'm moving to IMAP and trying to understand all the details of where to save email. The system is CentOS running sendmail - procmail which delivers as: DEFAULT=$HOME/Maildir/ I'm trying also to use Usermin as the webmail client. I can get mail to deliver to $HOME/Maildir/ and I can get clients (thunderbird outlook etc) to view them. However Usermin seems stuck with saving 'Drafts' 'Sent' and 'Trash' in $HOME/mail/ as mbox and Dovecot won't find them even when I use the setting: maildir:~/Maildir:mbox:~/mail/ I don't know what exact question to ask to I'll just ask for any thoughts on this? Second question, different topic. Are there problems with running POP3 and IMAP? I've always run POP3 and I'm thinking to move to IMAP for some clients so the Usermin webmail will be better 'synchronized' with the users inbox. *> dovecot --version * 1.0.10 *> dovecot -n * # 1.0.10: /etc/dovecot.conf protocols: imap pop3 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 mail_location: maildir:~/Maildir:mbox:~/mail/ 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/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam args: dovecot userdb: driver: passwd args: blocking=yes

2 4

[Dovecot] deliver fails - passdb doesn't support lookups?
by Kyle Wheeler 12 Mar '08

12 Mar '08

Hello, I'm trying to get `deliver` (the LDA) to function properly. I can get it to work without doing a user lookup, but for my own sense of sanity, I want to know what I'm doing wrong getting user lookups working. (I'm using dovecot 1.0.10). Here's what I have in the "auth default" section: auth default { mechanisms = plain login passdb ldap { args= /var/lib/dovecot/dovecot-ldap.conf } userdb static { args = uid=3728 gid=3728 home=/domains/%Ld/%Ln } user = vpopmail socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vpopmail group = vchkpw } client { path = /var/run/dovecot/auth-client mode = 0660 } } } And yet, when I run deliver, I get no warnings, no errors, and most especially, no email delivered. Here's how I call deliver: cat testemail | setuidgid vpopmail \ /usr/local/libexec/dovecot/deliver \ -d testuser(a)example.com I tried running deliver within strace, and here's what I found. It opens up the authentication socket and writes: VERSION\t1\t0\nUSER\t1\ttestuser(a)example.com\tservice=deliver\n And it gets back: VERSION\t1\t0\nSPID\t10917\nFAIL\t1\n" If I understand the authentication protocol correctly, that means an internal error occurred. The dovecot log file reports this: Error: auth(default): static(testuser(a)example.com): passdb doesn't support lookups, can't verify user's existence passdb? I thought it was the userdb that was important! What's going on here? ~Kyle -- Men, as an organization, are getting more women than any other group working anywhere in the world. Wherever women are, we have men looking into it. -- Jerry Seinfeld

2 2