similar to: Sieve: Conversion script for procmail recipes.

Hello, I'm trying to move from procmail to dovecot sieve. I found the translation script at http://www.dovecot.org/tools/procmail2sieve.pl It works well except the following use cases: * ^From:.*myemail at mydomain.com.* | formail -I"X-Priority: 2 (high)" -I"X-mydomain-com-seen: yes" | $SENDMAIL -oi \ myemail at mydomain2.com \ myemail at mydomain3.com :0c *

I've trying to get dovecot-auth to talk to exim and have been running debugging on both sides. I've added the line: i_info("auth_client_input: client disconnected: %s", strerror(errno)); just after the "case -1" in the first switch statement in: auth-client-connection.c: auth_client_input() and get this in the logs: dovecot: Feb 27 13:35:09 Info: auth(default):

So as to make sure that Dovecot Sieve's vacation system works Exim has to be forced to generate a "Reply-To:" header in the message (which it doesn't do by default). The current example for using the Dovecot LDA with Exim doesn't do this. Here is a replacement example for the local_delivery transport:- local_delivery: driver = pipe command =

Dovecot 2.1.16 fails to compile giving the following error under Solaris 10. Previously I had no problem compiling 2.1.12. The start of the config.log file contains: It was created by Dovecot configure 2.1.16, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure ## --------- ## ## Platform. ## ## --------- ## hostname = luna uname -m = i86pc uname -r =

Hi, I have a fedora15 system with dovecot-v2.0.15, dovecot-pigeonhole and and amavisd-new and would like to implement it on my system using postfix. I've read the basic wiki documentation, but I really can't figure out the proper starting point in my case. I've enabled "protocol lda" in 15-lda.conf and added "sieve" to the list of mail_plugins. I'm trying to

Thank you. This may be helpful. > On Nov 10, 2015, at 13:01, Benny Pedersen <me at junc.eu> wrote: > > > https://www.google.dk/search?q=procmailrc+to+sieve > > > have fun -- Vicki cfcl.com/vlb twitter.com/vlb

Please ignore my previous question.. as it turns out it's a bug/feature of fprintf(3C) and sockets under Solaris. Exim was using fprintf to output the AUTH string and for some unknown reason it was hanging, possibly because the input buffer on the file stream wasn't empty or something. After modifying the Exim's dovecot authentication plug-in to use write(2) instead of

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

hi all I am trying to filter emails to a user (weather) based on the subject: :0 *^Subject:.*Weather | /usr/bin/formail | /path/to/executable *^Subject:.*Tornado | /usr/bin/formail | /path/to/executable All it does is deliver the email to the weather inbox. For testing I tried. echo 1 | mail -s "Tornado" weather Enabling verbose and log file gives me: From root at

I run a pair of dovecot servers for personal small domains with several layers of backup in place ... - The two dovecot servers replicate to each via a Tinc vpn mesh. That gives email resiliency. - All mail is replicated via offlineimap to a 3rd server over that Tinc vpn. It's on the mesh, it has space, so why not ? - All mail is replicated as well as via mbsync to a zfs dataset on my

> 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

Hi! In the process of making mysystem work again, having just done a reinstall of 6.3 x86_64. I have a considerable collection of procmail recipes for filtering mail in various ways, and since the upgrade none of 'em is working. procmail passes every mail thru spambayes, which gives back a rating on spamminess. this happens, so it's not as if procmail is simply punting. that is

Currently I use procmail to filter mails according to specific tokens and trigger certain actions. For that I feed mails which match certain criteria to a pipe which then post processes the mail right when it arrives. >From what I found I could use a workaround with sieve by storing mails somewhere and then work on those at certain intervals. But this is an awkward solution which causes delays

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

I have a 6.5 machine that had everything set up and working correctly (fetchmail, sendmail w/ starttls, procmail, spamassassin) but the MB cratered. I bought a new machine, and installed Centos 6.6 and all is not well. I used the config from the previous incarnation (via backups) for fetchmail (works fine), sendmail (works fine for sending via relay and tls), but procmail now refuses to pick up

Anyone know of one? Is that O'Reilly book good? I need to get my fetchmail setup with some good filtering in procmail pronto and I can't remember how to set it up and compose the recipes properly. I'm willing to just buy a book at this point to make the spam and unwanted emails go away. Any advice or direction is appreciated. Of course I'll Google, but I was hoping someone

Hello, I am running dovecot-1.0-0_34 on Centos 4.4 In dovecot.conf I have: default_mail_env = maildir:/var/spool/mail/vhosts/%n/%d the content of that folder is: drwxrwxr-x 3 vmail vmail 4096 Dec 30 05:23 .. drwx------ 5 vmail vmail 4096 Sep 12 13:55 .Drafts drwx------ 5 vmail vmail 4096 Dec 29 18:26 .Sent drwx------ 5 vmail vmail 4096 Dec 30 03:37 .Trash drwx------ 5 vmail

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

Vicki Brown skrev den 2015-11-10 21:01: >> dovecot supports sieve, so why the need for procmail ? > Because I already HAVE procmail recipes and know proemial. +1 > The point is to make what I have, work. https://www.google.dk/search?q=procmailrc+to+sieve and you can imho learn more with roundcube, that will help you make the power out of sieve, but i know it if one have learned

I tried to edit http://wiki2.dovecot.org/procmail but got stuck on the TextCha. Approaching this list instead seems to be a time-tested secondary approach, and I wasn't completely comfortable making these changes without discussion anyway. So here goes. The SENDMAIL= assignment is not only irrelevant, but actually wrong. The note down in the update section about Ubuntu explains the problem