- dovecot - dovecot.org

[Dovecot] save failed to INBOX
by Erland Nylend 19 Jun '07

19 Jun '07

Hello, I'm seeing som error messages in the mail log, like this: Jun 12 12:50:44 <mail.info> smtp2 deliver(user1(a)domain.tld): msgid=<10784847.1181644475592.foo.bar@foo99>: save failed to INBOX Jun 12 12:50:44 <mail.info> smtp2 deliver(user1(a)domain.tld): msgid=<30757588.1181644556388.foo.bar@foo99>: saved mail to INBOX It seems that when two or more messages are being delivered at the same time, only one delivery succeeds. Both the maildirs and the indexes are stored on a SAN .. I'll try to read the source, to find out whether this is a locking problem. I would think that if a deliver -process finds that a maildir is locked, then it should wait, and retry? -- Erland Nylend

3 41

[Dovecot] Odd error from deliver
by Ralf Hildebrandt 19 Jun '07

19 Jun '07

I found these errors in my log today: Jun 18 01:02:11 postamt deliver(cpxxxsch): msgid=<FSL%200706180000356580.6412(a)JISCMAIL.AC.UK>: save failed to INBOX: Unknown error Jun 18 01:02:11 postamt deliver(cpxxxsch): msgid=<FSL%200706180000356580.6412(a)JISCMAIL.AC.UK>: Rejected: Unknown error Jun 18 15:37:22 postamt deliver(roxxxmy): msgid=<E1I0HPz-0002OZ-00(a)p15110889.pureserver.info>: save failed to INBOX: Unknown error Jun 18 15:37:22 postamt deliver(roxxxmy): msgid=<E1I0HPz-0002OZ-00(a)p15110889.pureserver.info>: Rejected: Unknown error This is deliver from dovecot-1.0.1 What exactly IS "Unknown error"? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Ballmer should step down in favour of Mr T, because he pity the fool who don't got high-end video cards and 4GB RAM for Vista Aero!

3 12

[Dovecot] parameters to deliver
by Bruce Bodger 19 Jun '07

19 Jun '07

Read this in the dovecot sieve wiki: "The envelope sender is taken from a Return-Path: header in the message. The envelope recipient is taken from -d option passed to deliver." Is "-d" still a valid deliver switch? When I configure postfix's main.cf like so... mailbox_command = /usr/local/libexec/dovecot/deliver -d -e ..it sqwaks with, "Jun 18 18:44:50 G518X2 deliver(-e): net_connect(/ usr/local/var/run/dovecot/auth-master) failed: No such file or directory" when configured like so... mailbox_command = /usr/local/libexec/ dovecot/deliver -e -d ${recipient} ..it burps with, "Jun 18 18:56:40 G518X2 postfix/local[19766]: 3BBC16C96E0: to=<me(a)mydomain.com>, relay=local, delay=0, status=bounced (command line usage error. Command output: Fatal: Missing destination argument )" It doesn't like... mailbox_command = /usr/local/libexec/dovecot/ deliver -e -d "$recipient" either! Is -d required any longer... and if so, how, please. B. Bodger

3 4

[Dovecot] Problem with deliver
by David Favor 19 Jun '07

19 Jun '07

Per the wiki page: http://wiki.dovecot.org/LDA Doing the following should create a Maildir directory structure in an arbitrary directory, deposit a message and create/update any dovecot indexes: mkdir /common/foo export HOME=/common/foo export PATH=/usr/libexec/dovecot:$PATH cat 1180102308.88215.4145.davidfavor.com:2,RS | deliver -f doda(a)foobar.com This gives an error "(-d user) not given" and when '-d user' given an exit code of 75 is silently returned. Let me know the correct way to test how the deliver program works. Thanks. - David -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 1

[Dovecot] Outlook 2003 - Disappearing favorite folders
by Phillip T. George 18 Jun '07

18 Jun '07

Hello all, I'm having an issue with Outlook 2003, where favorite folders seem to disappear. Specifically, they are subfolders of the Inbox. The Inbox favorite folder stays there without a problem. Any clues as to what the problem may be? With the previous IMAP server (courier I believe) this wasn't a problem...so it leads me to believe that Dovecot might be the problem. I'm working with Dovecot 1.0.rc28 Thanks, Phillip

5 10

[Dovecot] v1.0.1 released
by Timo Sirainen 17 Jun '07

17 Jun '07

http://dovecot.org/releases/dovecot-1.0.1.tar.gz http://dovecot.org/releases/dovecot-1.0.1.tar.gz.sig Lots of small fixes. * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked). The expansion could have caused problems if paths contained any '%' characters. + Print Dovecot version number with dovecot -n and -a + deliver: Added -e parameter to write rejection error to stderr and exit with EX_NOPERM instead of sending the rejection by executing sendmail. + dovecot --log-error logs now a warning, an error and a fatal - Trying to start Dovecot while it's already running doesn't anymore wipe out login_dir and break the running Dovecot. - maildir: Fixed "UID larger than next_uid" errors which happened sometimes when dovecot-uidlist file didn't exist but index files did (usually because mailbox didn't have any messages when it was selected for the first time) - maildir: We violated maildir spec a bit by not having keyword characters sorted in the filename. - maildir: If we don't have write access to cur/ directory, treat the mailbox as read-only. This fixes some internal error problems with trying to use read-only maildirs. - maildir: Deleting a symlinked maildir failed with internal error. - mbox: pop3_uidl_format=%m wasn't working right - mbox: If non-filesystem quota was enabled, we could have failed with "Unexpectedly lost From-line" errors while saving new messages - mysql auth: %c didn't work. Patch by Andrey Panin - APPEND / SEARCH: If internaldate was outside valid value for time_t, we returned BAD error for APPEND and SEARCH never matched. With 64bit systems this shouldn't have happened. With 32bit systems the valid range is usually for years 1902..2037. - COPY: We sent "Hang in there.." too early sometimes and checked it too often (didn't break anything, but was slower than needed). - deliver: Postfix's sendmail binary wasn't working with mail_debug=yes - Don't corrupt ssl-parameters.dat files when running multiple Dovecot instances. - Cache compression caused dovecot.index.cache to be completely deleted with big endian CPUs if 64bit file offsets were used (default) - Fixed "(index_mail_parse_header): assertion failed" crash

5 6

Re: [Dovecot] index
by Timo Sirainen 17 Jun '07

17 Jun '07

(Ccing again the list in case someone else has similar problems) On Sun, 2007-06-17 at 20:14 +0200, Lucas -LandM- wrote: > Hi Timo, > > I patched the source and same result. We think the problem is because > everytime user access to his mailbox, dovecot do the index again. And it > consume near the 80% in iowait because, as strace shows, read all mails. The problem isn't that Dovecot indexes it. The problem is that Dovecot ISN'T indexing it. Dovecot commits changes to cache file only after a FETCH command finished successfully. So if the client is disconnected in the middle of doing the FETCH, all of the work that Dovecot did so far gets lost on Dovecot's side. And apparently your client also starts everything from the beginning, even though it already knew some of the messages' sizes.. So the previous patch I sent was supposed to prevent this because originally Dovecot was the one that disconnected the client. It logged "Disconnected for inactivity in reading our output" as the disconnect reason. This shouldn't happen anymore after you patched it, so why did the client still get disconnected? Anyway, here's another patch that makes Dovecot not forget all of its work if the client gets disconnected in the middle of FETCH: http://hg.dovecot.org/dovecot-1.0/rev/e1cd11c5e00a If the client is still disconnecting, it probably takes a couple of tries to get everything read and cached, but after that it should all work nicely. Here's a similar patch for POP3: http://hg.dovecot.org/dovecot-1.0/rev/86766f448e50

1 0

[Dovecot] subdir disappeared
by Luigi Rosa 17 Jun '07

17 Jun '07

I have an installation that sometimes acts strangely: Jun 12 11:28:00 mail dovecot: imap-login: Login: user=<nadia>, method=PLAIN, rip=10.10.10.103, lip=10.10.10.254 Jun 12 11:53:59 mail dovecot: IMAP(nadia): inotify_add_watch(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 11:53:59 mail dovecot: IMAP(nadia): stat(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 11:56:14 mail last message repeated 5 times Jun 12 11:58:14 mail last message repeated 2 times Jun 12 12:00:14 mail last message repeated 2 times Jun 12 12:02:14 mail last message repeated 2 times Jun 12 12:02:14 mail dovecot: IMAP(nadia): stat(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 12:03:23 mail dovecot: IMAP(nadia): Disconnected: Logged out ..... Jun 13 12:08:01 mail dovecot: IMAP(nadia): unlink(/var/spool/mail/nadia/cur/:2,ST) failed: Is a directory Needless to say that no modification has been made to the server for many days and the user did not complain until that time. Could it be Dovecot? Is there a way to trace this error? The MTS is Postfix and in that period the user did not receive any mail The system is a Fedora 6 2.6.20-1.2952.fc6 #1 SMP Wed May 16 17:59:13 EDT 2007 i686 i686 i386 GNU/Linux Ciao, luigi -- / +--[Luigi Rosa]-- \ You cannot achieve the impossible without attempting the absurd.

2 4

[Dovecot] 60 seconds problem
by Waheed Rahuman 17 Jun '07

17 Jun '07

I am using Dovecot-1.0-0_27.rc10.e14. And when try to login with outlook there is an error saying "You server did not respond do u want to try again in 60 seconds" Any solutions please help regards Waheed

2 1

Re: [Dovecot] Per user based protocol access and pause after failed login?
by Mart Pirita 17 Jun '07

17 Jun '07

Tere. > %c expands to "secured" or empty. So you could use eg. > passdb pam { > args = %s%c > } > > and create imap, imapsecured, pop3, pop3secured > > More better, so for example user1 can access only imaps, using Yous suggestion, I have to list all users, except user1 in imap, pop3, pop3secured. But it should works also in other way, that by default all users are allowed to use all protocols and then I exclude user1 from imap, pop3, pop3secured. So I tried: passdb pam { args = %s%c } /etc/pam.d/ includes imap, imapsecured, pop3, pop3secured files which includes: auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth and only imapsecured has this line: auth required pam_listfile.so item=user sense=deny file=/etc/imapsusers onerr=succeed and /etc/imapsusers includes user1 But now even pop user can't login:(. -- Mart

2 1