October 2006 - dovecot

[Dovecot] IMAP Dovecot with ISPConfig and shared folders?
by Perry 31 Oct '06

31 Oct '06

Fedora 5, postfix, dovecot, ISPConfig server all running well, (don't want to break it) LOL. But, I do not have IMAP shared folders. These instructions on dovecot tell of how to setup namespace to be able to get shared folders. http://wiki.dovecot.org/SharedFolders But given everything is relative in ISPConfig, not sure if this is possible or if I could really mess things up. What tells dovecot to look in the various different web# folders for email? Am I better off using Symlinking??? Thanks much for all comments and direction. ____________________________________________________________________________________ Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates (http://voice.yahoo.com)

1 0

Re: [Dovecot] Redundant shared mail store?
by Joshua Goodall 31 Oct '06

31 Oct '06

Jasper Bryant-Greene wrote: > Hi guys > > I'm about to embark on a project replacing a legacy single mail server > running proprietary software with a cluster of Dovecot servers. We > clearly need a shared mail store for these servers, but we are not happy > with simply using a server running NFS as this becomes a single point of > failure. > > What have other people used? AFAICT our options are: > > * A shared block device (Fibre Channel, iSCSI, ATAoE etc) running > GFS > or similar to allow multiple servers to access it concurrently > > * Two or more NFS units, either with built-in support for > replication > of FS changes and failover, or with scripts for achieving this > functionality > > I prefer option 1, although it's expensive. What have other people used? > Do we have other options? I recommend a pair of NetApp filers (e.g. 2 x 3020c) exporting NFS from shared disk shelves in their high-availability mode. This is a hybrid of the two options, except a) it's a fully supported and stable NetApp configuration, b) they're sharing disk storage, c) you're not hog-tied to GFS, d) it's the best NFS implementation in the world (you can even trust the fcntl locking), e) it's really fast, f) NetApp's onboard snapshots and other funky software bits will make you wonder how you lived without them, g) the HA actually works. I have a six-digit userbase with mailboxes in this configuration. JG

4 3

[Dovecot] auth both system and virtual users
by Gerry Reno 31 Oct '06

31 Oct '06

I've setup dovecot to auth both system and virtual users but it is refusing to work. It keeps saying user is not found. Is there something more that I need to set? dovecot.conf: ============================================================================ = default_mail_env = maildir:/var/mail/%1.1u/%u/Maildir mail_extra_groups = mail protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster(a)example.com } auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot.deny deny = yes } passdb passwd-file { args = /etc/imap.passwd } passdb pam { } userdb passwd { } user = root } dict { } plugin { } ============================================================================ = maillog: ============================================================================ = Oct 30 20:12:00 grp-01-10-01 dovecot: Killed with signal 15 Oct 30 20:12:03 grp-01-10-01 dovecot: Dovecot v1.0.rc7 starting up Oct 30 20:12:04 grp-01-10-01 dovecot: auth(default): passwd-file /etc/dovecot.de ny: Read 0 users Oct 30 20:12:04 grp-01-10-01 dovecot: auth(default): passwd-file /etc/imap.passw d: Read 1 users Oct 30 20:12:24 grp-01-10-01 dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=::ffff:127.0.0.1 rip=::ffff:127.0.0.1 resp=AHR1c2VyAHBhc3M= Oct 30 20:12:24 grp-01-10-01 dovecot: auth(default): passwd-file(tuser,::ffff:12 7.0.0.1): unknown user Oct 30 20:12:24 grp-01-10-01 dovecot: auth(default): client out: OK 1 user=tuser Oct 30 20:12:24 grp-01-10-01 dovecot: auth(default): master in: REQUEST 1 30764 1 Oct 30 20:12:24 grp-01-10-01 dovecot: auth(default): passwd(tuser,::ffff:127.0.0 .1): unknown user Oct 30 20:12:24 grp-01-10-01 dovecot: auth(default): userdb(tuser,::ffff:127.0.0 .1): user not found from userdb Oct 30 20:12:24 grp-01-10-01 dovecot: auth(default): master out: NOTFOUND 1 Oct 30 20:12:24 grp-01-10-01 dovecot: imap-login: Internal login failure: user=< tuser>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured ~ ============================================================================ =

1 3

[Dovecot] Problem report
by leslie.polzer＠gmx.net 31 Oct '06

31 Oct '06

Hello guys, Dovecot is a great IMAP server, I really like it :) I recently found an annoying problem, however: To sync my mail, I use OfflineIMAP, which usually works very smoothly. A spam mail with the year set to 2038 produced the error message "Invalid internal date" when OfflineIMAP tried to upload it to the server. Only deleting the messag helped. The usual data: Dovecot 0.99.14-1sarge0 on Debian Sarge x86. It would be nice to remove this date-smartness (?)... Kind regards, Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/

2 1

[Dovecot] Continuing problems with zombied dovecot-auth procs; mail-cache-fields.c IMAP procs crashing
by JB Zimmerman 31 Oct '06

31 Oct '06

Folks- Hans Morten Kind was kind enough to confirm the issue I'm having with large mailboxes and the mail-cache-fields.c file (line 26: unreached error in logs when the imap process crashes out on large Maildirs). Has anyone implemented a fix for this that is both tested and applicable without making manual code changes myself, since I don't trust myself slashing about in source files? Ideally, has this problem been noted for fixing in a newer version? Failing that, if I downgrade to the 0.99 version shipped with RHEL4, has anyone found that to be more reliable? I used the 1.0rc10 in order to gain access to the 'namespace' conf directives so that upgrading from our current Courier Maildir installations would be as seamless as possible, but at the moment, I'm looking at having to roll back to Courier in order to fix this (and the next) problem. Also, we have found that using 1.0rc10 on RHEL4, using pam-ldap for account info and pam-krb for auth, has resulted in the eventual inaccessability of mail due to many zombied and unresponsive dovecot-auth processes. Restarting dovecot the first few times it becomes unresponsive will fix the problem, presumably by instantiating new auth procs, but eventually this no longer works since the restart doesn't actually kill off the zombied auth procs and the socket stops responding. Has anyone run into this problem? Thanks, J.B. Zimmerman RHEL4AS, fully updated, using the AT rpms: dovecot-1.0-0_27.rc10.el4.at --

1 0

[Dovecot] [Patch] vpopmail plaintext passwords
by Remi Gacogne 31 Oct '06

31 Oct '06

Hello, This patch enables APOP and CRAM-MD5 when using vpopmail auth. Remi Gacogne Aqua Ray SARL

2 2

[Dovecot] Multiple certificates
by Phill Edwards 31 Oct '06

31 Oct '06

I have dovecot version 1.0 relese 0.beta8.2.fc5 installed on my FC5 linux box. It acts as an IMAP server to my home LAN. I connect to it from the home PCs over SSL and have installed a certificate in the domain imap.edwards.home to enable this. However, I also use a web site called www.xs2mail.com which retrieves the email from my IMAP server (which has a public DNS entry called XXX.homelinux.com) and displays them in a web interface. I used to run uw-imap and this all worked fine. But since I went to Dovecot I can't use that site any more because it gives me this message: Login failure: Certificate failure for XXX.homelinux.com: self signed certificate: /C=AU/ST=NSW/L=Sydney/O=Edwards/OU=IMAP server/CN=imap.edwards.home/emailAddress=philledwards(a)gmail.com I assume it's getting upset because the certificate is for imap.edwards.home but the domain it's connecting to is XXX.homelinux.com. Is there a way to resolve this? I read something about using virtual servers but all I could find is this in a post somewhere - I don't know which file it goes, where in that file etc: <snip> 1.0-tests support "virtual servers", where this is possible: server foo { listen = 1.2.3.4 ssl_cert_file = /etc/ssl/certs/foo.cer } server bar { listen = 1.2.3.5 ssl_cert_file = /etc/ssl/certs/bar.cer } </snip> Can anyone help me figure this out? (PS - I can't just set up my own IMAP web interface because I can't run anything on port 80 with my ISP and I can't get out of our company firewall on anything other than port 80). Thanks in advance, Phill

3 5

[Dovecot] www.dovecot.org misconfigured?
by Steven F Siirila 30 Oct '06

30 Oct '06

I am having difficulting getting to www.dovecot.org and wiki.dovecot.org. My browser tells me it can't find them. Anyone know what's up? -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

5 5

[Dovecot] dovecot auth + postifx: how to disable PLAIN and LOGIN without TLS?
by Lev Serebryakov 29 Oct '06

29 Oct '06

Hello dovecot, I want to have all authorization in one place and don't use Cyrus-SASL. I cobfigure postfix 2.3.3 to use dovecot-SASL. I have next lines in main.cf: smtpd_sasl_security_options = noplaintext,noanonymous smtpd_sasl_tls_security_options = noanonymous But PLAIN and LOGIN are advertised by postfix :( Is it bug of postfix or dovecot-auth? I don't want to disable these mechanisms in auth {} stanza of dovecot.conf, because they are Ok over SSL/TLS. It works for dovecot-pop3 and dovecot-imap, but not for postfix :( postfix 2.3.3, dovecot 1.0rc10. -- Best regards, Lev mailto:lev@serebryakov.spb.ru

3 4

[Dovecot] LSUB and namespaces - how to get rid of multible prefixes
by Henrik Ostergaard Madsen 28 Oct '06

28 Oct '06

I'm using dovecot 1.0.rc7 and Squirrelmain 1.4.8 using IMAP on a Debian 3.1 Testing system, and I'm having a problem. When Squirrelmail (or other IMAP clients) submits an LSUB "" "*%", dovecot responds with: Request: A004 LSUB "" "*%" Response: * LSUB () "/" "INBOX.Sent" * LSUB () "/" "INBOX.Trash" * LSUB () "/" "INBOX.Drafts" * LSUB () "/" "mail/Sent" * LSUB () "/" "mail/Trash" * LSUB () "/" "mail/Drafts" * LSUB () "/" ".mail/Sent" * LSUB () "/" ".mail/Trash" * LSUB () "/" ".mail/Drafts" * LSUB () "/" "Sent" * LSUB () "/" "Trash" * LSUB () "/" "Drafts" * LSUB () "/" "INBOXSent" * LSUB () "/" "INBOXTrash" * LSUB () "/" "INBOXDrafts" * LSUB () "/" "./INBOX.Sent" * LSUB () "/" "./INBOX.Trash" * LSUB () "/" "./INBOX.Drafts" * LSUB () "/" "Test" Lsub completed. This is in spite of that only INBOX.Sent, INBOX.Trash, INBOX.Drafts and Test actually exists. I have tried with no explicit namespaces, only one with no prefix or with prefix "/", and with that again and all the above prefixes marked as hidden, but with absolutely no change in the LSUB repons. Due to this, Squirrelmail shows up a whole bunch of folders, but only the correct ones (without prefixes) works.. This has been the same with a few prior versions of dovecot 1.0 , but not with dovecot 0.99. It is the same for Squirrelmail 1.4.7, but I do not think the client matters.. Is there a setting or way to deal with this - or is it a bug? Regards, Henrik

2 2