- dovecot - dovecot.org

[Dovecot] dovecot notifying a database about total number of messages.
by Erland Nylend 17 Aug '07

17 Aug '07

Hello, in addition to our mail system, we have some other systems which needs to know how many messages, and how many unread messages, a user has in his/her inbox (maildir). Currently, we have a mod_perl script which takes a mail address as input, and then traverses the maildir, and outputs the number of unread messages. Our challenge is that the maildirs are located on a SAN, and traversing a maildir is slow. We currently have more than 100 requests pr. second, which we handle with caching, and spreading the load across different servers. I'm looking into the possibility of either using dovecots index files, or having dovecot update a database with total number of messages/number of unread messages. Question: 1) if I'm using perl, is there any way I can read in the information in the index files? Is the data formatted in some standarized way, so that I can parse it, or use a module which read in the data? (if I can read the indexes in wrapper scripts to imap/pop/deliver, then I could probably update a database with the information) 2) how would you proceed, if the aim is to end up with dovecot notifying a database regarding the number of messages, and unread messages? -- Erland Nylend

2 1

[Dovecot] ssh tunneling and maildir
by Joel Becker 17 Aug '07

17 Aug '07

Hello everyone, please keep my CC'd, I'm not on the list. I've been using dovecot happily via an ssh tunnel. My mutt is configured to use IMAP, and the tunnel is as follows in my muttrc: set tunnel="ssh -q mymailhost 'MBOX_LOCKS=fcntl MAIL=/home/jlbec/mail /usr/libexec/dovecot/imap'" It should be pretty obvious that this logs into mymailhost as me (via SSH keyauth) and runs /usr/libexec/dovecot/imap directly as a foreground process. Setting MAIL, it points dovecot imap to my mbox folders. dovecot imap speaks imap over stdin/out, this goes over the ssh to mutt. It works great. Really great. I don't need root access at all, the server isn't running dovecot globally, and I get IMAP through firewalls if I can ssh through a firewall/vpn. I'm using mbox and fcntl, so my MTA has no trouble working in concert. However, this doesn't appear to be documented anywhere. A friend showed it to me, and I don't even remember who that was. I'm now considering changing to maildir folders. I figure dovecot imap might figure out a folder is maildir when stat says S_IFDIR, but without documentation, I can't figure out how to tell dovecot imap to use maildir when I create a folder. I'm also unsure how this will interact with my MTA. For the latter, I'm thinking I just need to configure my MTA to use dovecot's deliver program. For the former, is there some magic environment variable I need to add to my tunnel command line? Thanks Joel -- "The first requisite of a good citizen in this republic of ours is that he shall be able and willing to pull his weight." - Theodore Roosevelt http://www.jlbec.org/ jlbec(a)evilplan.org

4 8

[Dovecot] Recover mailboxes
by Jordi Espasa Clofent 17 Aug '07

17 Aug '07

HI all, Some time ago I've user(a)domain.com in maildir mailbox with their own mails, their folders, subfolders, indexes files.. etc My server was missconfigured and I've rebuilded all SMTP; I've recreated all the mailboxes with same names that before. Of course, the problem is the content of these mailboxes it's not the same. So, the idea is: add all the contento from user(a)domain.com (old) mailbox to user(a)domain.com (new) mailbox. because I have got a complete copy of (old) mailboxes and their content. ¿How can I do it?

1 0

[Dovecot] High CPU utilization on Solaris 10
by Jon Alessandrello 17 Aug '07

17 Aug '07

Some people had this problem when giving some superoptimization flags with Sun Studio. Did you do that? -Timo No I did not use any optimization. And Dave, I took what you said and just tried both dovecot-1.0.2 dovecot-1.0.rc29 and have the same exact results :(

3 2

[Dovecot] index and control files not being created
by Luis Pablo Michelena Scaffo 16 Aug '07

16 Aug '07

Hello, I'm configurating dovecot 1.0.3 on debian etch. While trying to set public folders, y decided to have the index and control files on the users homes. those homes are mounted by nfs, with disabled access to root. In that scenario, I'm getting the errors i transcribe next: Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:17 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Aug 16 11:21:26 server dovecot: IMAP(user): Disconnected: Logged out Aug 16 11:21:27 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlis t) failed: Operation not permitted Aug 16 11:21:27 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/mailfile, /inbox/shared/.folder/cur/mailfile :2,S) failed: Operation not permitted Then I touched those files and the errors faded away. Beside that, I was testing the setup, and while trying to delete some files on the shared folder, I got another error: Aug 16 16:38:04 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/1183976419.755_0.server:2,Sa, /inbox/shared/.folder/cur/1183976419.755_0.server:2,STa) failed: Operation not permitted Aug 16 16:38:11 server dovecot: IMAP(user): fchown(/home/user/Maildir/shared-settings/control/.folder/dovecot-uidlist) failed: Operation not permitted Aug 16 16:38:11 server dovecot: IMAP(user): rename(/inbox/shared/.folder/cur/1183976419.755_0.server:2,Sa, /inbox/shared/.folder/cur/1183976419.755_0.server:2,STa) failed: Operation not permitted Which seems odd, because I though that as a flag, the deleted flag should be marked on the index files and not directly on the shared folder (where the user hasn't any permission other than reading), ant the same goes to the "read" flag Am I wrong? Is there any workaround to make dovecot behave the way I'd liked? The config follows: login_executable: /usr/lib/dovecot/imap-login mail_extra_groups: mail mail_location: maildir:/home/%u/Maildir:INBOX=/inbox/mdir/%u mmap_disable: yes namespace: type: private separator: / location: maildir:~/Maildir:INBOX=/inbox/mdir/%u inbox: yes namespace: type: public separator: / prefix: Shared folders/ location: maildir:/inbox/shared:INDEX=/home/%u/Maildir/shared-settings/index:CONTROL=/home/%u/Maildir/shared-settings/control auth default: passdb: driver: passwd args: blocking=yes passdb: driver: shadow userdb: driver: passwd Cheers, Luis

1 0

[Dovecot] ANY password option
by Master Abi 16 Aug '07

16 Aug '07

Hi We sometimes migrate mailboxes over to one of our mail servers which has a very handy feature called 'ANY password'. This will allow access to a mailbox using the given username and disregard checking for the password. This is a useful feature for many reasons. Is there a possibility Dovecot could have such a a feature or is there a workaround already. Thanks Master

3 3

Re: [Dovecot] use of deliver from procmail advisable?
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 AM, dovecot-request(a)dovecot.org wrote: > Message: 7 > Date: Wed, 15 Aug 2007 00:58:40 +0200 > From: martin f krafft <madduck(a)madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot(a)dovecot.org > Message-ID: <20070814225840.GA23721(a)piper.oerlikon.madduck.net> > Content-Type: text/plain; charset="us-ascii" > > also sprach Charles Marcus <CMarcus(a)Media-Brokers.com> > [2007.08.14.2028 +0200]: >>> Well, the whole point of sieve, I believe, is to make it >>> something that an >>> admin would want to let arbitrary users modify on their own >>> recognizance, >>> and the ability to specify arbitrary programs to run would be >>> just *asking* >>> to be hacked. >> >> Wouldn't a decent, secure alternative to procmail be sieve+amavisd- >> new? > > Except it's not really possible to make amavisd-new do per-user spam > filtering. And it's even more of a performance hog. > > -- > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck > > "all language designers are arrogant. goes with the territory..." > -- larry wall > > spamtraps: madduck.bogus(a)madduck.net >

3 2

[Dovecot] Moving a mail between folders and post-processing ?
by Jerry Nicholls 16 Aug '07

16 Aug '07

Hi, Within Dovecot is there a way of spotting a change to a folder and running a post-processing script on the email that was moved ? I'm specifically after a way of seeing either an email entering or leaving a folder - preferably running a different post-process script depending on the direction. Essentially if an email enters or is moved out of a 'spam' folder I'd like to mark it as 'spam'/'ham' in the Bayesian filters respectively. Is there any such mechanism, or should I start looking at how to write a plugin to achieve this ? If it's the plugin route is there any good documentation on the plugin APIs etc ? Thanks, Jerry. -- Jerry Nicholls E: Jerry.Nicholls(a)zeninternet.co.uk Core Systems & Networks Manager W: http://www.zen.co.uk/ Zen Internet Ltd. T: 0845 058 9000 F: 0845 058 9005

3 2

Re: [Dovecot] deliver assertion failure
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 PM, dovecot-request(a)dovecot.org wrote: > > > Message: 7 > Date: Thu, 16 Aug 2007 08:59:25 +1200 > From: Jasper Bryant-Greene <jbg(a)indy.net.nz> > Subject: [Dovecot] deliver assertion failure > To: dovecot(a)dovecot.org > Message-ID: <20070815205925.GA2808(a)port1.indy.net.nz> > Content-Type: text/plain; charset=us-ascii > > Deliver from latest 1.1 HG with sieve also from latest 1.1 HG is dying > with an assertion failure when it delivers to my mailbox. Other > mailboxes on the same system are unaffected, but I can read my mailbox > fine through IMAP. > > Dovecot and sieve were compiled with -march=nocona -pipe -ggdb > > I've commented out my entire sieve script and the problem still > occurs. > > file index-mail-headers.c: line 590 (index_mail_get_raw_headers): > assertion failed: (ret != -1) > - Last output repeated twice - > > Raw backtrace: > /usr/libexec/dovecot/deliver(i_syslog_panic_handler+0x2b) > [0x493125] > -> /usr/libexec/dovecot/deliver(i_fatal+0) [0x492b17] > -> /usr/libexec/dovecot/deliver [0x44f7cf] > -> /usr/libexec/dovecot/deliver(index_mail_get_first_header+0x30) > [0x44fb9b] > -> /usr/libexec/dovecot/deliver(mail_get_first_header+0x3a) > [0x47ca3d] > -> /usr/libexec/dovecot/deliver(deliver_get_return_address+0x21) > [0x41453b] > -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run > +0x14b) [0x2b3687f194a1] > -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x2b3687f169ba] > -> /usr/libexec/dovecot/deliver(main+0x8dc) [0x415c4d] > -> /lib/libc.so.6(__libc_start_main+0xe3) [0x2b3687cf6533] > -> /usr/libexec/dovecot/deliver [0x4137a9] > > Jasper > > > ------------------------------ > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > End of dovecot Digest, Vol 52, Issue 56 > *************************************** I am getting the same error, the mail is still being delivered, but the system is generating an error message sent to the original sender The mail system <EMAIL ADDRESS HIDDEN>: Command died with signal 11: "/usr/local/libexec/dovecot/deliver" Reporting-MTA: dns; HIDDEN X-Postfix-Queue-ID: 7F344239D31 X-Postfix-Sender: rfc822; EMAIL ADDRESS HIDDEN Arrival-Date: Wed, 15 Aug 2007 15:53:32 -0400 (EDT) Final-Recipient: rfc822; EMAIL ADDRESS HIDDEN Action: failed Status: 5.3.0 Diagnostic-Code: x-unix; internal software error the mail logs show: to=<EMAIL ADDRESS HIDDEN>, relay=dovecot, delay=1.5, delays=0.01/0.02/0/1.5, dsn=5.3.0, status=bounced (Command died with signal 11: "/usr/local/libexec/dovecot/deliver") This did not happenr in v1.1 alpha 2, but is now appearing in 1.1 alpha 1.3 after a day or so of using the new version. Jerry Yeager

1 0

Re: [Dovecot] use of deliver from procmail advisable?
by Jerry Yeager 16 Aug '07

16 Aug '07

On Aug 15, 2007, at 5:00 PM, dovecot-request(a)dovecot.org wrote: > ------------------------------ > > Message: 3 > Date: Wed, 15 Aug 2007 18:08:58 +0200 > From: martin f krafft <madduck(a)madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot(a)dovecot.org > Message-ID: <20070815160858.GA22429(a)piper.oerlikon.madduck.net> > Content-Type: text/plain; charset="utf-8" > > also sprach Jerry Yeager <jerry(a)scene-naturally.dyndns.org> > [2007.08.15.1758 +0200]: >> a) Postfix milter to run ClamAv, eh something like this (for Linux >> fans) >> b) then use the regular Postfix <--> SpamAssassin <--> LDA (with >> sieve) >> setup (message routing via Postfix master.cf) so that individual >> users can >> set their own SA rules and vacation stuff. > > This is exactly how I used to have it but then the need for > a vacation autoresponse to the From: address (as opposed to > Return-Path) arose and I had to switch to procmail: > > http://dovecot.org/list/dovecot/2007-August/024766.html > > Before that, I was using spamc with --pipe-to, but always had a bad > feeling about that, since the manpage says: > > Note that there is a very slight chance mail will be lost here, > because if the fork-and-exec fails there?s no place to put the > mail message. > > and my message to SA-users on this was never answered[0]. > > 0. http://marc.info/?l=spamassassin-users&m=115185095923772&w=2 > > Now I am using procmail and at least now that failure will cause > postfix to defer a message. > > -- > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck > > half a bee, philosophically, must ipso facto half not be. > but half the bee has got to be, vis-a-vis its entity. you see? > but can a bee be said to be or not to be an entire bee, > when half the bee is not a bee, due to some ancient injury? > -- monty python > > spamtraps: madduck.bogus(a)madduck.net >

1 0