- dovecot - dovecot.org

[Dovecot] start dovecot at boot
by jepoy 04 Feb '07

04 Feb '07

hi guys, just recently installed dovecot from source on my centos box.how can i enable it to automatically start upon reboot. tnx -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

4 3

[Dovecot] 1.0rc19 with plugins on AIX 5.2
by Ralf Becker 03 Feb '07

03 Feb '07

Hello, has anyone out there successfully build dovecot on AIX with plugins supported? I'm talking about an dlopen error when a plugin tries to access global symbols, that are defined in the dovecot "parent" binary For example: # MAIL_PLUGINS=zlib /usr/local/libexec/dovecot/imap imap(root): Error: dlopen(/usr/local/lib/dovecot/imap/lib20_zlib_plugin.so) failed: rtld: 0712-001 Symbol i_error was referenced from module /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol i_stream_get_data was referenced from module /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol i_stream_skip was referenced from module /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol i_stream_seek was referenced from module /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol i_stream_close was referenced from module /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol i_panic was referenced from module /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol pool_get_exp_grown_size was referenced from module /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so(), but a runtime definition of the symbol was not found. Additional errors occurred but are not reported. Maybe libtool is the problem, because it does not export global symbols correctly. Or would a newer version of AIX vac fix this? Any ideas? I'm using dovecot 1.0rc19, AIX 5.2-06 and vac 5.0.2 Regards, Ralf -- ______________________________________________________________________ Dipl.-Inform. (FH) Ralf Becker Rechenzentrum (r/ft) der FH Trier (Network|Mail|Web|Firewall) University of applied sciences Administrator Schneidershof, D-54293 Trier Mail: beckerr(a)fh-trier.de Fon: +49 651 8103 499 WWW: http://www.fh-trier.de/~beckerr Fax: +49 651 8103 214 PGP: http://www.fh-trier.de/~beckerr/pgp ICQ: <available> ______________________________________________________________________ Wenn Gott gewollt haette, dass E-Mail in HTML geschrieben wuerden, endeten Gebete traditionell mit </amen>. (Tom Listen)

1 1

Re: [Dovecot] broken attachments with pop3
by Robert Schetterer 03 Feb '07

03 Feb '07

Justin McAleer schrieb: > Robert Schetterer wrote: >> Hi all, >> ive just upgrade to rc21 ( so i dont know perhaps this report failure is >> fixed with this release ) >> i have reports from users that attachments get broken ( with rc19, dont >> know about before ) with some accounts , which where downloaded via a >> pop3 service to a exchange server, but in fact nothing is broken when >> looking with imap to the mailboxes >> Has anyone an idea, i havent any failure logs about that, is there a >> parameter which makes logging verbose to such failures? >> >> > The first thing you should do is pop such messages directly from > Dovecot. Anytime there is a problem with mail, and Exchange is involved, > the first step should always be ruling out Exchange IMHO. > > -- > Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht > und ist - aktuelle Virenscanner vorausgesetzt - sauber. > agree exchange is magic voodoo, but its not exchange , its an independent pop service which delivers to exchange ( like fetchmail ) and the other 1000 mailboxes do not have this problem going the same way, so it must something special with this mailboxes, may any index stuff involved with this? I have no failure doing pop3 with thunderbird to that mailboxes, these mailboxes are the the ones with most traffic on the system After all the exchange systems are not under my control and the failure info from win admins and their users is not very exact *g -- Mit freundlichen Gruessen Best Regards Robert Schetterer https://www.schetterer.org Munich/Bavaria/Germany -- Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht und ist - aktuelle Virenscanner vorausgesetzt - sauber.

1 0

[Dovecot] Automatic Folder Expiry (plugin?)
by Troy Engel 02 Feb '07

02 Feb '07

Greetings, I'm migrating an existing Courier IMAP installation to Dovecot (1.0rc19 right now) on a new server; there's one feature I'm not sure if Dovecot supports - but it might and I'm missing it, so I'll ask. In Courier there's an option to expire a folder after a given time period; ostensibly it's to keep a Trash folder clean, but we use it to keep the Junk folder (where spam is delivered by Exim) clean. How can I do this in Dovecot? Here's the chunk from Courier for those unfamiliar with it (just part of the verbiage): ##NAME: IMAP_EMPTYTRASH:0 # # The following setting is optional, and causes messages from the given # folder to be automatically deleted after the given number of days. # IMAP_EMPTYTRASH is a comma-separated list of folder:days. # # Important: the purging is controlled by CTIME, not MTIME ... So in our case it's set like so: IMAP_EMPTYTRASH=Junk:14 Thanks for any help/ideas - I'm not sure if we can live without this feature, the amount of spam is horrendous and users never clean out that folder. -te -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

6 11

[Dovecot] Planning a dovecot deployment: issues and questions
by Dan Price 02 Feb '07

02 Feb '07

Hi folks, I am currently evaluating Dovecot for deployment to ~200 software engineers (so, heavy email users); I'm hoping this list could provide wisdom about how best to do the configuration, evaluation and deployment, and what testing folks have done to determine whether dovecot is right for their site. Below I've listed the diffs between the dovecot-example.conf and our config. I've been playing with 1.0rc19 running on Solaris Nevada. We have set it up on our server on an alternate port from the existing IMAPd, which is something ancient, horrible and problematic. We're using sendmail and mail.local as our MTA and MDA, respectively, as these ship with the OS, and we need to test them. I have some users who have volunteered to experiment with the server, and they are starting to do so. I've also seen the "flags" problems others have mentioned on the list, and I do not think I could deploy to production with that bug affecting the users. I also have some issues which I'm not sure have been previously reported: One user (of my 4 test users) is occasionally seeing a bug in which mutt 1.4.2.1 claims to be "[downloading xxx/30724]" headers. Upon getting very near to the 30724 total, the total rises to something like: "[downloading xxx/50132]". And on and on. The actual number of messages in the box is 30724. This is not very reproducible, and we do not yet know if it's a problem with mutt or dovecot. Another, using Apple's Mail.App reported: "Everything was working fine until i quit out of my mail app (Mac mail) and restarted. Then i saw weird things: - messages wouldn't get marked unread - messages from eons ago started showing up in my Drafts folder - Inbox would keep spinning/loading - then eventually Inbox just hung showing me no messages" Any thoughts about how to approach these issues? I don't really have a feel for how to go from user-observed-app-doing-X to imapd-is-doing-Y. The big challenge for our site may be mailbox size: the median mailbox size is 62M, the average is 176M and the largest is 1.1GB. I'd be curious to know what sort of mailbox sizes other sites have experienced, and how widespread the use of the Dovecot MDA is-- is this likely to make a big difference for us, and will we have to migrate our (approximately 25) procmail users to sieve? Having read the recent discussions about "1.0", I think my team would really appreciate knowing how to obtain something that was thoroughly vetted and worked highly reliably. If major changes are coming, I think it'd be great to have a 1.0.x stability focused tree, and a 1.1.x (or 2.x.x) feature tree. Thanks in advance for your comments, -dp ------- ------- ------- ------- ------- ------- ------- ------- ------- [note that IMAPS is off for now, but that's just temporary] $ diff dovecot.conf dovecot-example.conf 21d20 < protocols = imap 42,45d40 < protocol imap { < listen = *:150 < } < 50c45 < disable_plaintext_auth = no --- > #disable_plaintext_auth = yes 89c84 < ssl_disable = yes --- > #ssl_disable = no 214,215d208 < mail_location = mbox:~:INBOX=/var/mail/%u:INDEX=%h/Mail/imapd-indices < 258d250 < mail_extra_groups = mail 290d281 < dotlock_use_excl = yes 296d286 < lock_method = fcntl 441,444d430 < # dp: we'll see. < mbox_read_locks = dotlock fcntl < mbox_write_locks = dotlock fcntl < ------- ------- ------- ------- ------- ------- ------- ------- ------- -- Daniel Price - Solaris Kernel Engineering - dp(a)eng.sun.com - blogs.sun.com/dp

5 7

[Dovecot] 1.0.rc20 released
by Timo Sirainen 02 Feb '07

02 Feb '07

http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz http://dovecot.org/releases/dovecot-1.0.rc20.tar.gz.sig So, rc19 was somewhat broken. How about this version? + dovecot: Added --log-error command line option to log an error, so the error log is easily found. + Added mail_log_max_lines_per_sec setting. Change it to avoid log throttling with mail_log plugin. - Changing message flags was more or less broken in rc19 - ACL plugin still didn't work without separate control directory - Some mbox handling fixes, including fixing an infinite loop - Some index file handling fixes - maildir quota: Fixed a file descriptor leak - If auth_cache was enabled and userdb returned "user unknown" (typically only deliver can do that), dovecot-auth crashed. - mail_log plugin didn't work with pop3

4 4

[Dovecot] Strange Error in RC19
by Jay Chandler 02 Feb '07

02 Feb '07

Drops IMAP connection when a particular user's "Sent" folder is opened. Does this mean that the sent folder is potentially corrupted? Feb 2 10:14:57 MyBox dovecot: IMAP(WhinyUserDuJour): file mbox-sync-rewrite.c: line 404 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / chandler(a)chapman.edu Today's Excuse: those damn raccoons!

1 1

[Dovecot] namespace subscription problem
by Nate Sanders 02 Feb '07

02 Feb '07

Greetings, I am trying to setup a private namespace in dovecot and running in to some troubles. Here is my setup: > default_mail_env = maildir:~/Maildir > > # default namespace > namespace private { > separator = . > prefix = > inbox = yes > } > namespace private { > separator = . > prefix = maillog. > location = maildir:/var/maildir/maillog/Maildir/ > #inbox = yes > hidden = no > } So far it's working to a degree. When I load my imap folder and go to Subscribe, I can see the master "maillog" folder, and expand it to see all the subfolders. The problem is, I cannot subscribe to the master "maillog" folder. Only it's sub folders. When I check dovecot.info it says this: > dovecot: 2007-01-31 13:27:42 Info: imap(nate): Namespace: > type=private, prefix=maillog., sep=., inbox=no, hidden=no, > subscriptions=no I see there "subscriptions=no". Is it possible to change this to yes? Would changing this to yes allow me to subscribe to the actual namespace folder? I tried adding "subscriptions=yes" and "subscription=yes" to dovecot.conf but both entries resulted in failed starts and errors. How is it possible allow subscriptions directly to this namespace? Thanks. -- Nate Sanders nate(a)ima.umn.edu Associate Systems Manager (612) 624 - 4353 Institute for Mathematics and its Applications

2 2

[Dovecot] periodic problems with dovecot-1.0rc19 (No authentication sockets found)
by Mikhail Teterin 02 Feb '07

02 Feb '07

Hi, Timo! On the new server running 1.0rc19 people stop being able to login every once in a while. The log messages on the server side are: Jan 30 12:18:50 bonkers dovecot: pop3-login: No authentication sockets found Jan 30 12:18:50 bonkers dovecot: pop3-login: No authentication sockets found Jan 30 12:18:59 bonkers dovecot: pop3-login: No authentication sockets found Jan 30 12:19:01 bonkers dovecot: imap-login: No authentication sockets found Jan 30 12:19:06 bonkers dovecot: pop3-login: No authentication sockets found Restarting dovecot helps for a while, but then the problem reappears... The config-file was copied from an older server running 1.0.r15, where we never saw this problem... The old server ran FreeBSD-4.10/i386. The new one runs FreeBSD-6.2/amd64. Thanks for any hints! Yours, -mi

3 2

[Dovecot] Over quota message
by Antonio Casado Rodríguez 02 Feb '07

02 Feb '07

Hi all, I'm working with Dovecot-1.0.rc19 + dovecot-lda + postfix + quota-maildir plugin When a new email arrives and it's over quota, the client receives this: -------------------------------- The mail system <vvv(a)ual.es>: Command died with status 89: "/usr/local/libexec/dovecot/deliver" -------------------------------- Reporting-MTA: dns; vvv.ual.es X-Postfix-Queue-ID: 3AA3F280AB X-Postfix-Sender: rfc822; zzz(a)ual.es Arrival-Date: Fri, 26 Jan 2007 15:00:17 +0100 (CET) Final-Recipient: rfc822; vvv(a)ual.es Original-Recipient: rfc822;vvv(a)ual.es Action: failed Status: 5.3.0 Diagnostic-Code: x-unix; unknown mail system error 89 -------------------------------- cannot be received another type of clear message like: the user to exceeded the quota?

1 1