similar to: docecot and procmail?

Hello all, I've a working dovecot installation on my machine, using exim3, virtual users and maildirs. I would like to add procmailrc rules for these (virtual) users, but i've not succeeded with that. The authentication is done with a passwd-file looking like this : testuser:password:uid:gid::/home/mail/testuser::chroot:maildir:/home/mail/testuser/Maildir/ i've put .procmailrc files

Does anyone have advice or pointers on good documentation on how to convert a system from using the Mbox format to using Maildir? I recently upgraded to Fedora Core 2 from Fedora Core 1 and discovered that UW-IMAP was gone. So I switched over to using Dovecot. So far so good. But I would like to convert my system to start using the Maildir format. How easy is this to accomplish? Can I keep

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren at togami.com

I'm running Dovecot 1.1 RC1. I believe I've done all the due diligence for making things working correctly over nfs. But I run into locking issues if I run over nfs. procmail is doing the delivery over nfs. uw-imap was ruining over nfs. dovecot is fine if its on the nfs server (i.e. it has local access to the disk, no nfs) I run into lock deadlocks if I run dovecot over nfs Users

Is there an announcements mailing list for samba? If not, could one please be created? I want to know when new releases are made, and when security holes are found, maybe even infrequent benchmark results, but unfortunately I don't have time to keep up with this list. My mailbox has been overflowing on a weekly basis, and it's got to stop, so I really need to decrease the volume coming

Hello, is dotlock supposed to work with NFS? I noticed that the default-locking method causes problems even with nfslockd started. Regards Marten

Hi list, I understand that dovecot's deliver does a little more than deliver: it also updates the dovecot metadata stored with each Maildir. Thus, if I use deliver as opposed to procmail's internal Maildir delivery, it seems that the IMAP server later has less work to do since the metadata is can use are up to date. Doing this, however, incurs an extra process for each mail delivered. I

There are three applications that have their mitts on files on my mail server, which is running AIXV5.3 and UWIMAP and mbox format. The mail folders and INBOXES are native to that machine, but also are NFS exported to a login server and a mailing list server. All three machines are running the lockd daemon. Everybody wants to lock differently 1) procmail (delivering for sendmail), which

I have been trying to set up procmail but I am running into some issues with using deliver. I am running Debian Etch with Dovecot 1.1.8 compiled from the Debian Experimental source package. ##### Start .procmailrc ##### # System-wide settings for procmail SHELL="/bin/bash" SENDMAIL="/usr/sbin/sendmail -oi -t" LOGFILE="/var/log/procmail.log"

I'm using procmail as the local delivery agent for Maildir style mailboxes. I discovered that I was able to send mail to other users but was unable to send mail to myself. Examples from verbose procmail log: **** Successful message to another user **** procmail: [24589] Fri Jun 2 15:03:34 2006 procmail: Assigning

> dovecot supports sieve, so why the need for procmail ? Because I already HAVE procmail recipes and know proemial. The point is to make what I have, work. > On Nov 9, 2015, at 22:49, Benny Pedersen <me at junc.eu> wrote: > > On November 10, 2015 6:36:00 AM Vicki Brown <vlb at cfcl.com> wrote: > >> Can anyone help? > > dovecot supports sieve, so why

I am using Mac OS X Server. OS X Server uses postfix with dovecot set as mail_transport. I want to add procmail to the mix. I cannot use the (typical) mailbox_command = procmail -a "$EXTENSION" because mailbox_transport = dovecot overrides any mailbox_command parameter and it is NOT Possible to change, remove, or otherwise vary the mailbox_transport on OS X server. I'm

Hi all, I'm seeing a random issue with my procmail filters (only on email from this list) where once every so often, it will fail to filter a message. I am sorting by the to/cc email address, and this rule works on 99.9% of posts, however every now and again, I see something like this happen: From centos-bounces at centos.org Sat Jan 5 01:57:28 2008 Subject: Re: [CentOS]

I'm trying to use procmail and I'm having trouble getting it to set some headers. I have one mailing list that sets ?Newsgroups: in the header and I want to remove it. I have the following test recipe: :0 * ^Subject:.*\<testing * ^(Mime-Version:|Content-) | formail -IMime-Version: -IContent- If I understand it correctly, it should remove the Mime-Verion and Content headers. The

Hello List, i switched mailformat from mbox to maildir. Now i have a little problem with procmail/formail and headermanipulation of mails. Here an example: 0 * ^From.*gmx.de | (formail -t -I"procmail: gmx.de") >> /var/spool/mail/xxxxxx So, i can add some different headerlines for later evaluation and the result is attached to inbox. Now i have the problem that i don't know

Hey folks, here's a question. I want to enable procmail for the users so that they can have their incoming messages sorted info various folders and such regardless of MUA access or web access. I know I can set procmail to deliver to a maildir, but wouldn't that screw up dovecot's indexes? If it would, what can I do to ensure that the indexes stay correct? Thanks! -- Dan Egli On my

Hi, Is there a configuration element that would allow me to change the dot-lock name for the user's /var/mail inbox when it is locked? dovecot (correctly) acquires <username>.lock, but I'm having a problem with procmail where some obscure code path is preventing procmail's acquisition of a lock when it's that default name in /var/mail. The issue is not permissions

Hi there, i'm trying to get dovecot, procmail, postfix & SpamAssassin working together http://www.linuxquestions.org/questions/showthread.php?t=441062 But i'm not having a lot of luck, a question about dovecot, what kind of mail box am i using? mbox? if so does anyone know if procmail can use mbox? /etc/dovecot.conf protocols = imap pop3 imap_listen = [::] pop3_listen = [::]

My procmail log keep filling with the following error procmail: Program failure (75) of "/usr/libexec/dovecot/deliver" Can't open log file /var/log/dovecot.log: Permission denied ls -l /usr/libexec/dovecot/deliver -rwxr-xr-x. 1 root root 964760 avr 20 03:55 /usr/libexec/dovecot/deliver ls -l /var/log/dovecot.log -rw-------. 1 root root 34689 jun 20 15:26 /var/log/dovecot.log what

Hi to all out there, i know this is not the right mailinglist for this issue, but i?m hoping to get maybe here an answer to my problem. i have succesfully migrated 12.000 mailboxes on a debaian with washington imap to maildir on sles10 with dovecot. although i had some post-converting work to do, i can say that almost everything went fine. but there is one problem with my LDA. When postfix is