Re: [Dovecot] v1.1.alpha4 released / about dbox
Timo Sirainen wrote: But since there's still a chance that index files could break (although v1.1 tries harder than v1.0 to fix problems), it would be nice if the flags/keywords were written to metadata block once in a while. So if the index files are lost, flag changes wouldn't be completely lost. Metadata updates of course use disk I/O so they shouldn't be done too often. I was thinking that the metadata could be updated: - if IMAP connection has been idling for 4 hours (not changing flags) - when closing mailbox and there are changes older than 4h - immediately if there are changes older than 24h (whenever mailbox is being synced, e.g. SELECT/NOOP/STATUS) Or something like that. Those rules can of course be changed, but I'm not sure if I should bother making them configurable from dovecot.conf. There are already too many settings. what about a maintanance srcipt/daemon which can be run from cron and every sysadm can decided when and how often he'd like to update metadatas? -- Levente Si vis pacem para bellum!
Re: [Dovecot] v1.1.alpha4 released / about dbox
It appears configure.in is still set to 1.1.alpha3 instead of alpha4. Great work on the dbox implementation. - David -- Love feeling your best ever, all day, every day? Email [EMAIL PROTECTED] for the easy way.
[Dovecot] trouble with deliver in 1.0.4
Ok, here's one for the idiot file. I just installed dovecot-1.0.4 on my
personal system for testing, a system which has to be the simplest
dovecot configuration possible. deliver is barking about something with
which version 1.0.3 has no problem. I looked over the wiki, googled,
and see nothing wrong.
The error:
deliver(jjb): Sep 07 21:39:40 Fatal: Failed to create storage for 'jjb'
with mail
'mbox:/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB/:INBOX=/var/mail/jjb'
In dovecot.conf:
userdb passwd {
# [blocking=yes] - By default the lookups are done in the main
dovecot-auth
# process. This setting causes the lookups to be done in auth worker
# processes. Useful with remote NSS lookups that may block.
# NOTE: Be sure to use this setting with nss_ldap or users might get
# logged in as each others!
#args =
args = blocking=yes
}
and
mail_location = mbox:~/:INBOX=/var/mail/%u
Clues generously accepted,
Jack
Re: [Dovecot] Dovecot + Sieve - and passdb/userdb
Nils Vogels wrote:
Daniel L. Miller wrote on 7-9-2007 2:24:
userdb static {
args = uid=5000 gid=8 home=/var/mail/%d/%n mail=/var/mail/%d/%n
allow_all_users=yes
}
plugin {
sieve = sieve
}
Deliver + sieve is working great. By setting the sieve variable to
sieve, a non-hidden file, it doesn't appear in the folder list. I
made a similar change to pysieved to use a non-hidden folder - in
combination with avelsieve and squirrelmail I now have a
user-maintainable server-side filter solution. Awesome!
Is there a hidden gotcha I'm missing here? It's doing exactly what
I want!
Everything that would for some reason go into the users homedir, you
would be able to reach via Imap.
If I were you, I'd make home and mail point to a different directory,
which could be as simple as home=/var/mail/%d/%n
mail=/var/mail/%d/%n/Maildir. This way, dovecot will only look for mail
in the $HOME/Maildir, but still can do administrative stuff in $HOME.
Grts,
Nils
What administrative stuff? These directories are used exclusively for
mail - if any user actually has a local account their home folders are
located under /home - but I don't want that mixed with mail service at
all.
--
Daniel
Re: [Dovecot] trouble with deliver in 1.0.4
On Sun, 2007-09-09 at 03:37 +0300, Timo Sirainen wrote: On Sat, 2007-09-08 at 14:38 -0700, Jack Bailey wrote: Ok, here's one for the idiot file. I just installed dovecot-1.0.4 on my personal system for testing, a system which has to be the simplest dovecot configuration possible. deliver is barking about something with which version 1.0.3 has no problem. I looked over the wiki, googled, and see nothing wrong. Set auth_debug=yes and mail_debug=yes and show me the logs when running deliver? Oh, I tested it a bit badly. Looks like no-one had tested my last changes, at least with home coming from userdb. Fixed: http://hg.dovecot.org/dovecot-1.0/rev/798963ca1f6f And I guess I'll release 1.0.5 as well. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] BUG REPORT - Stops logging after sleep
On Sat, 2007-09-08 at 12:36 -0400, Bill Cole wrote: The only way a program could know of the failure would be to trace the syslog configuration and look for whether messages are appearing, then take action (probably calling closelog() and openlog()) as needed. I already sent a patch that did closelog() when reopening logs, but that didn't help. I forgot openlog(), but that shouldn't be needed.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] alert function, V2
On Thu, 2007-09-06 at 09:55 -0400, Stewart Dean wrote: What's needed is an in-your-face unavoidable alert, and the UWIMAP alert functionality provides this. This could be done pretty easily with a plugin overriding mail_storage.sync_init(), checking if we want to do an alert and if we do, call mail_storage_callbacks.notify_ok() with the alert text. I'm not planning on implmenting this myself anytime soon though.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] auth_default_realm for different listeners
On Wed, 2007-09-05 at 15:00 -0400, John Morrissey wrote: We provide POP3 service for several realms, each of which has a substantial number of users logging in with no realm (bare username). We would like to use Dovecot, but I haven't been able to findout how to vary auth_default_realm for each listener. Unfortunately Dovecot doesn't directly support this. With v2.0 the configuration file will hopefully be flexible enough to allow it. You can do this in your passdb though. For example with checkpassword or SQL passdb you're able to check if there's @ in username and if not add it based on the local IP address. http://wiki.dovecot.org/PasswordDatabase/ExtraFields/User http://wiki.dovecot.org/PasswordDatabase/CheckPassword http://wiki.dovecot.org/Variables signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Timeout while waiting for lock for transaction log file
On Wed, 2007-09-05 at 15:24 +0200, Peter Eriksson wrote: I have a user that gets client timeout errors when he tries to delete/clean up his massive Spam folder (many thousands of mail messages). He uses Thunderbird and has it configured to use Move to Trash when he deletes messages. I find the following in Dovecot's log file when it happens: Aug 28 10:38:22 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(bpn): Timeout while waiting for lock for transaction log file /home/bpn/Maildir/.Trash/dovecot.index.log This happens if mailbox synchronization has been running for 2 minutes by one process and another process is also trying to sync the mailbox. Synchronization is also done when committing copied/saved mails, like: - lock log file - rename() all new files to destination mailbox's new/ or cur/ - unlock I guess the rename() stage takes a long time with that user. I hadn't really thought before that this could be a problem. Any suggestions on what I can tuned/fix in Dovecot to solve this issue? You could grow the hardcoded timeouts. If you're using dotlocks, src/lib-index/mail-transaction-log.c: #define LOG_DOTLOCK_TIMEOUT 60 #define LOG_DOTLOCK_STALE_TIMEOUT 60 Otherwise src/lib-index/mail-index-private.h: #define MAIL_INDEX_LOCK_SECS 120 It's a bit stupid that these are using different defines with different values. I'll go fix that for v1.1. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] passing quota to deliver via command line
On Tue, 2007-09-04 at 08:24 -0700, WJCarpenter wrote: Is there any way to pass things like quota= for the quota plugin to the deliver LDA via the command line or as an environment variable or whatever? I've got all the info I need in my MTA to avoid a userdb lookup in the LDA, but I still have to do the userdb query to get the per-user quota number (the default quota works fine, of course). You can pass it in QUOTA environment, which behaves exactly as quota= setting. With v1.1 you'll need to give -k parameter so that it doesn't clean the environment (added just now). signature.asc Description: This is a digitally signed message part
Re: [Dovecot] recipient delimiter results in sieve errors
On Mon, 2007-09-03 at 05:53 +0400, Gregory Mokhin wrote: deliver([EMAIL PROTECTED]): Info: sieve runtime error: Keep: Generic Error deliver([EMAIL PROTECTED]): Error: sieve_execute_bytecode(/home/vmail/.dovecot.sievec) failed deliver([EMAIL PROTECTED]): Info: msgid=[EMAIL PROTECTED]: saved mail to INBOX I guess it depends on what your Sieve code looks like? Or does it give the same error even if your script is only keep;? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Today's dovecot-1.1.alpha3 checkins fail to build
On Sat, 2007-09-01 at 08:44 -0500, David Favor wrote: net1#uname -a Linux net1.coolsurf.com 2.6.22.4-65.fc7 #1 SMP \ Tue Aug 21 21:50:50 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux make[5]: Entering directory `/build/work/dovecot-1.1.alpha3/src/lib-storage/index/dbox' gcc -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src/lib -I../../../../src/lib-mail -I../../../../src/lib-imap -I../../../../src/lib-index -I../../../../src/lib-storage -I../../../../src/lib-storage/index -pipe -O2 -I/common/pkgs/sqlite-3.4.2.1/include -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -MT dbox-file.o -MD -MP -MF .deps/dbox-file.Tpo -c -o dbox-file.o dbox-file.c mv -f .deps/dbox-file.Tpo .deps/dbox-file.Po make[5]: *** No rule to make target `dbox-keywords.o', needed by `libstorage_dbox.a'. Stop. Your Makefiles are out of date. Run autogen.sh and configure again. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] pipe() failed: Too many open files
On Fri, 2007-08-31 at 22:50 +0100, peter wrote: I am getting random disconnects from my imap session, dificulties to revconnect, very sluggish behaviour when changing between mail folders also frequent and rapidly repititive messages on te client mailserver x.x.x.x is not a imap4 server I am running dovecot 1.0.rc2 from ports on OpenBSD 4.0 on a PIII, 500MHz 512MB That's a really old version. You should be running v1.0.0 or later. Aug 31 20:51:57 apache dovecot: pipe() failed: Too many open files If the port used --with-ioloop=kqueue, that's the problem. kqueue is a bit buggy with OpenBSD. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] pipe() failed: Too many open files
On Sun, 09 Sep 2007 04:51:06 +0300 Timo Sirainen [EMAIL PROTECTED] wrote: Aug 31 20:51:57 apache dovecot: pipe() failed: Too many open files If the port used --with-ioloop=kqueue, that's the problem. kqueue is a bit buggy with OpenBSD. This has been fixed as of 4.2 and -current.
Re: [Dovecot] Dovecot + Sieve - and passdb/userdb
On Fri, Sep 07, 2007 at 12:26:28PM -0700, Daniel L. Miller (DLM) wrote: DLM Nils Vogels wrote: DLM Everything that would for some reason go into the users homedir, you DLM would be able to reach via Imap. DLM DLM If I were you, I'd make home and mail point to a different directory, DLM which could be as simple as home=/var/mail/%d/%n DLM mail=/var/mail/%d/%n/Maildir. This way, dovecot will only look for mail DLM in the $HOME/Maildir, but still can do administrative stuff in $HOME. DLM DLM What administrative stuff? These directories are used exclusively for mail - if any user actually has a local DLM account their home folders are located under /home - but I don't want that mixed with mail service at all. Administrative stuff such as sieve filters, possible error logs, textfiles that are used by other plugins such as vacation (lda-dupes), etc, etc. This way you won't be able to see those in your subscribe list, which is a good thing since they aren't mailboxes/dirs :) Gr, Nils -- Simple guidelines to happiness: Work like you don't need the money, love like your heart has never been broken and dance like no one can see you. pgpbWPK3RPLFs.pgp Description: PGP signature
Re: [Dovecot] How can i complie and install the dict modules
On Fri, 2007-08-31 at 11:35 +0200, Oliver Eales wrote: Hello, I want to migrate from courier-imap to dovecot and now i am trying out dovecot1.1.alpha3 But i have problems getting the expire plugin to work. You're probably the first one trying to do that. :) At startup i get the message: Unknown dict module: db As far as i understood i have to compile the backend manually an copy it into tho appropirate place. But how can i do this ? I think the easiest way would be for you to at least first make it work via dict proxy. So: 1) Make sure config.h has BUILD_DB defined. That means it's actually building with the berkeley db support. 2) See Dictionary proxy server in http://wiki.dovecot.org/Quota/Dict and change your config to use something similar. If that works and you want to drop dict proxy, then you'll need to play some with Makefiles to get this to work. I can try to figure out then if there's a way to make configure do this automatically with some option. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] processing Dovecot maildirs with shell scripts
On Thu, 2007-08-30 at 23:52 +0200, M. Fioretti wrote: Dovecot only sees the INBOX* folders. Under these constraints I'm safe, am I not? Also, since all the file names are created by procmail (there is nobody else injecting email from the outside) I can count on them being always unique, right? Right. mv, rm and ln are always safe. Just don't ever write to new mail files in new/ or cur/ directory, because then Dovecot might read partially written files. That means that cp file new/ isn't safe, but ln file new/ is. Er.. sorry, what do you mean exactly here? where is file where I link to new? Whatever file. :) What is the complete, exact sequence of Unix commands to safely go from: aux_maildir_1/new/some_file to, say, INBOX.one/new/some_file If you want to move, then it's simply mv aux_maildir_1/new/some_file INBOX.one/new/some_file The important thing is that you don't use cp. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] LDA bouncing mails after upgrade -- again
On Fri, 2007-08-31 at 13:29 +0200, Milan Holzäpfel wrote: You replied that it was a bug, and that it had been fixed in URL:http://dovecot.org/list/dovecot-cvs/2007-March/008346.html. .. | Aug 28 09:38:03 host.example.org deliver([EMAIL PROTECTED]): Module is for different version 1.0.3: /usr/lib/dovecot/lda/lib10_quota_plugin.so | Aug 28 09:38:03 host.example.org postfix/pipe[18356]: ID: to=[EMAIL PROTECTED], relay=dovecot, delay=0.4, delays=0.13/0.09/0/0.18, dsn=5.3.0, status=bounced (Command died with status 89: /usr/libexec/dovecot/postfix-deliver/deliver) Thanks, now really fixed: http://hg.dovecot.org/dovecot-1.0/rev/cb3679cd91a1 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Server Timed Out: Outlook Express
On Fri, 2007-08-31 at 12:57 -0600, Jackie Hunt wrote: Hi all, We just started running Dovecot this fall here on campus v 1.0. I've started getting some trouble reports from users. An Outlook Express users reported seeing the Server has not responded in 60 seconds messages. Waiting longer doesn't help, he has to stop/start Outlook Express to get connected again. Also have a Thunderbird user who is seeing that type of behavior first thing in the morning after being logged in all night. He has to stop/restart Thunderbird. These kind of problems are difficult to figure out without looking at what command the client last sent and what Dovecot replied with. If it's easy to reproduce, rawlog output would be helpful (http://dovecot.org/bugreport.html) I've looked at the Dovecot log, and don't see any errors. I do see lots of Disconnected, Disconnected in IDLE and Disconnected: Logged Out. These last two seem normal, if I just see Disconnected is that a flag that we're losing connections abnormally? If Outlook said Server hasn't responded in 60 secs, at some point later it just disconnects and it shows up as Disconnected in log. I know version 1.0.3 is out. I've looked at the changes, and the only one I can see that might be related to what we are seeing is the IDLE commmand fix. Was hoping for some advice on whether upgrading might resolve these issue. I don't think IDLE fixes help with that hasn't responded warning. signature.asc Description: This is a digitally signed message part
[Dovecot] Don't let deliver create index files
For various reasons I want to use deliver with Postfix and Courier-IMAP, and it seems to work fine except for one thing: deliver creates some dovecot.* index files that Courier never uses (and I assume deliver doesn't need them) Is there a way to prevent that? Thanks, Martin
Re: [Dovecot] Don't let deliver create index files
On 2007-09-09 04:34:43 +0200, Martin Strand wrote: For various reasons I want to use deliver with Postfix and Courier-IMAP, and it seems to work fine except for one thing: deliver creates some dovecot.* index files that Courier never uses (and I assume deliver doesn't need them) Is there a way to prevent that? why would you want to use deliver from dovecot but courier as imap server? wouldnt maildrop be the more natural choice for a courier user? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] Using NID_x500UniqueIdentifier as ssl_username_from_cert
On Thu, 2007-08-30 at 15:08 +0200, S. Wefel wrote: please have a look at the attached patch for dovecot-1.0.3 These patch modifies ssl_proxy_get_peer_name() to use the NID_x500UniqueIdentifier as username instead of NID_commonName. I won't add new features to v1.0 (and especially not break existing setups :), but I implemented this to v1.1 now: http://hg.dovecot.org/dovecot/rev/7ad61f00ee55 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Don't let deliver create index files
On Sun, 2007-09-09 at 04:34 +0200, Martin Strand wrote: For various reasons I want to use deliver with Postfix and Courier-IMAP, and it seems to work fine except for one thing: deliver creates some dovecot.* index files that Courier never uses (and I assume deliver doesn't need them) Is there a way to prevent that? http://wiki.dovecot.org/MailLocation - Index files - :INDEX=MEMORY. But it still creates and updates dovecot-uidlist file. I wouldn't use Dovecot's deliver if you're not using Dovecot for IMAP/POP. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot + Sieve - and passdb/userdb
On Fri, 2007-09-07 at 12:26 -0700, Daniel L. Miller wrote: If I were you, I'd make home and mail point to a different directory, which could be as simple as home=/var/mail/%d/%n mail=/var/mail/%d/%n/Maildir. This way, dovecot will only look for mail in the $HOME/Maildir, but still can do administrative stuff in $HOME. What administrative stuff? Currently sieve scripts, in future possibly some other files. Don't think home as a traditional user's home directory, but rather as a directory where Dovecot can safely create whatever files it wants without having them show up as mailboxes to user. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] too many files opened
On Wed, 2007-08-29 at 10:06 +0800, Joshua, C.S. Chen wrote: Hi folks, My institute's mail server was upgraded to RHEL5 with dovecot 1.0-2.1rc5 recently. And it uses PAM authentication which points to LDAP server. Now from time to time it gets Error like rc5 is pretty old. There are v1.0.x packages for RHEL5. dovecot: Aug 29 09:23:59 Error: auth(default): pam(joshua,192.168.177.52): pipe() failed: Too many open files Look at dovecot-auth process's list of open files: ls -l /proc/`pidof dovecot-auth`/fd/ How many are there and what are opened most of the time? auth default: passdb: driver: pam userdb: driver: passwd Are you using also nss_ldap? See http://wiki.dovecot.org/AuthDatabase/Passwd. With rc5 you can't fix it properly, and that could also be the cause of your problems. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] postfix + dovecot lda,
On Wed, 2007-08-29 at 16:53 +0100, Michael Moritz wrote:
I'm trying to replace procmail with deliver but I'm having problems with the
group part of things. I keep getting:
Aug 29 16:44:19 dingbat deliver(mimo):
open(/var/mail/.temp.dingbat.3969.d1689935a308e0dd) failed: Permission denied
Aug 29 16:44:19 dingbat deliver(mimo): file_lock_dotlock() failed with mbox
file /var/mail/mimo: Permission denied
My primary group is mimo and I think it's trying to use that. I changed it to
mail and things work. But I do not want all my users to have a primary group
mail.
Is there a way I can force deliver to use group mail as group and ignore the
per user gid?
Do you run deliver as root? If so, for now you could do this:
protocol lda {
restrict_setextragroups = mail
}
I'll fix mail_extra_groups to work with deliver for v1.0.5.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] shared mailbox subfolder permissions
On Sat, 2007-08-18 at 13:16 +0200, David Leuschner wrote: when I create a subfolder in a public mailbox the dovecot-shared file is copied for the newly created subfolder and all mails get the owner, group and permissions from the file. Unfortunately the cur, new and tmp folders only get the permissions from the file but owner and group are set according to the creator. This effectivly makes the folder private to the creator. Is this the intended behavior? Is it a bug that has already been fixed in a later version? I am using 1.0.rc29. This should fix it: http://hg.dovecot.org/dovecot-1.0/rev/8c98ecd43a35 Also I think you can work around this by setting setgid bit for the root Maildir. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] PAM child process timed out, killing it.
On Mon, 2007-09-03 at 11:21 +0300, Mart Pirita wrote: Aug 30 05:57:09 stan dovecot: auth(default): pam(user1,172.18.1.25): PAM child process 1266 timed out, killing it Your PAM modules are getting stuck. Probably has nothing to do with Dovecot itself. What userdb do you use? You could try adding blocking=yes to passdb pam's args or if you're using userdb passwd add blocking=yes to its args. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot problem
On Mon, 2007-09-03 at 10:18 -0300, Raphael Bittencourt S. Costa wrote: Helo all, Yesterday dovecot began droping connections and there is nothing conclusive in the log file, just the messagens below: Sep 2 11:43:57 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.152.100.77, lip=10.0.3.1 Have you set auth_verbose=yes or auth_debug=yes? Maybe it has something to do with that. What passdb are you using? signature.asc Description: This is a digitally signed message part
[Dovecot] v1.0.5 released
http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz.sig v1.0.4 was a bit bad release. - deliver: v1.0.4 broke home directory handling - maildir: Creating mailboxes didn't use dovecot-shared's group for cur/new/tmp directories. signature.asc Description: This is a digitally signed message part
