[Dovecot] integrating procmail
Hello, list members!
I'm new to dovecot, and haven't needed to maintain an email server instance for quite some time.
I recently got a fairly simple postfix + dovecot installation functional as needed, however I now need to get procmail filtering incoming mail, and after reading various docs and wikis, I find that I'm still having a tough time feeling confident on how best to approach it in the simplest manner. (this is for a small installation.... 10 email accounts, max).
Below, I've provide the relevant snippets of my current functional configuration; how best to integrate procmail into the mix?
/etc/postfix/main.cf: ... alias_maps = hash:/etc/mail/aliases local_recipient_maps = hash:/etc/postfix/vmailbox, $alias_maps virtual_transport = dovecot virtual_mailbox_domains = $mydomain virtual_mailbox_base = /var/vmail/ virtual_mailbox_maps = hash:/etc/postfix/vmailbox virtual_minimum_uid = 500 virtual_uid_maps = static:501 virtual_gid_maps = static:501 ...
/etc/postfix/master.cf: ... dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} - d ${recipient} ...
/etc/dovecot/dovecot.conf: ... mail_location = maildir:~/Maildir
protocol lda { sendmail_path = /usr/sbin/sendmail } auth default { mechanisms = plain passdb passwd-file { args = /var/vmail/passwd } userdb static { args = uid=vmail gid=vmail home=/var/vmail/%d/%u } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = vmail } } } ...
Thankyou for any tips, much appreciated!
On Wed, 18 May 2011 14:50:54 -0700 errno errno@cox.net articulated:
Hello, list members!
I'm new to dovecot, and haven't needed to maintain an email server instance for quite some time.
I recently got a fairly simple postfix + dovecot installation functional as needed, however I now need to get procmail filtering incoming mail, and after reading various docs and wikis, I find that I'm still having a tough time feeling confident on how best to approach it in the simplest manner. (this is for a small installation.... 10 email accounts, max).
Below, I've provide the relevant snippets of my current functional configuration; how best to integrate procmail into the mix?
Why procmail? Use sieve instead. It is fully supported in Dovecot and IMHO far easier to use.
-- Jerry ✌ Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
.
On Wednesday, May 18, 2011 03:07:44 PM Jerry wrote:
On Wed, 18 May 2011 14:50:54 -0700 errno errno@cox.net articulated:
Below, I've provide the relevant snippets of my current functional configuration; how best to integrate procmail into the mix?
Why procmail? Use sieve instead. It is fully supported in Dovecot and IMHO far easier to use.
I hear you, and agree - I was able to determine that sieve was better supported. Unfortunately, I'm doing this for a client who is rather set in his ways and already has a largish custom procmail filter he wants/needs to use. For me to tell him, "no we need to use sieve instead", he will see that as a failure on my part; and/or will request that I install and configure a different combination of software that will facilitate his familiar territory of procmail.
Seeing as I already have postfix and dovecot functioning, I'd rather just get procmail in there and be done with it; is this possible?
Thankyou!
I have not tried this:
http://www.zimbra.com/forums/users/7239-any-way-add-message-filters-command-...
H
On Wed, May 18, 2011 at 03:20:08PM -0700, errno wrote:
On Wednesday, May 18, 2011 03:07:44 PM Jerry wrote:
On Wed, 18 May 2011 14:50:54 -0700 errno errno@cox.net articulated:
Below, I've provide the relevant snippets of my current functional configuration; how best to integrate procmail into the mix?
Why procmail? Use sieve instead. It is fully supported in Dovecot and IMHO far easier to use.
I hear you, and agree - I was able to determine that sieve was better supported. Unfortunately, I'm doing this for a client who is rather set in his ways and already has a largish custom procmail filter he wants/needs to use. For me to tell him, "no we need to use sieve instead", he will see that as a failure on my part; and/or will request that I install and configure a different combination of software that will facilitate his familiar territory of procmail.
Seeing as I already have postfix and dovecot functioning, I'd rather just get procmail in there and be done with it; is this possible?
This is all on the Postfix side. Leave Dovecot out of it. And it's trivial.
main.cf: mydestination = localhost, localhost.$mydomain[, ... ] virtual_alias_maps = (set to something)
virtual_alias_maps includes this: real@email.address setnways@localhost
Create a Unix user, "setnways".
~setnways/.forward: |/path/to/procmail
Populate ~setnways/.procmailrc as desired.
Obviously this won't work if you have disabled local(8) delivery.
Note: I set reply-to this list, but it would be more appropriate on postfix-users. Start a new thread there if you need help. See also: http://www.postfix.org/virtual.5.html http://www.postfix.org/aliases.5.html http://www.postfix.org/local.8.html And your OS documentation if needed.
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: headerJerry dovecot.user@seibercom.net writes:
Below, I've provide the relevant snippets of my current functional configuration; how best to integrate procmail into the mix?
Why procmail? Use sieve instead. It is fully supported in Dovecot and IMHO far easier to use.
Well, how can I call external program from sieve? (For example for decoding some data, and put them to database?) Is any extension for this? KJ
-- http://sporothrix.wordpress.com/2011/01/16/usa-sie-krztusza-kto-nastepny/ GNU is Not Unix
On 5/19/2011 7:04 AM, Kamil Jońca wrote:
Jerrydovecot.user@seibercom.net writes:
Below, I've provide the relevant snippets of my current functional configuration; how best to integrate procmail into the mix? Why procmail? Use sieve instead. It is fully supported in Dovecot and IMHO far easier to use. Well, how can I call external program from sieve? (For example for decoding some data, and put them to database?) Is any extension for this? KJ
Currently, no. Not an official one anyway.
We did see the potential of this a few months back and we've built a skeleton implementation of such an extension. 'Skeleton' in this case means that there is a plugin that implements the Sieve language extension, but it does not actually do anything yet. I've documented the language extension as follows:
http://hg.rename-it.nl/hidden/pigeonhole-0.2-sieve-pipe/raw-file/tip/doc/rfc...
I am not sure when we can continue work on this. For security reasons, external programs would not be forked from the Sieve interpreter (LDA/LMTP plugin) directly, but rather using some unix socket and a Dovecot service. It should at least be implemented for Dovecot v2.1.
Timo, any comments?
Regards,
Stephan.
Am 19.05.2011 09:07, schrieb Stephan Bosch:
On 5/19/2011 7:04 AM, Kamil Jońca wrote:
Jerrydovecot.user@seibercom.net writes:
Below, I've provide the relevant snippets of my current functional configuration; how best to integrate procmail into the mix? Why procmail? Use sieve instead. It is fully supported in Dovecot and IMHO far easier to use. Well, how can I call external program from sieve? (For example for decoding some data, and put them to database?) Is any extension for this? KJ
Currently, no. Not an official one anyway.
We did see the potential of this a few months back and we've built a skeleton implementation of such an extension. 'Skeleton' in this case means that there is a plugin that implements the Sieve language extension, but it does not actually do anything yet. I've documented the language extension as follows:
http://hg.rename-it.nl/hidden/pigeonhole-0.2-sieve-pipe/raw-file/tip/doc/rfc...
I am not sure when we can continue work on this. For security reasons, external programs would not be forked from the Sieve interpreter (LDA/LMTP plugin) directly, but rather using some unix socket and a Dovecot service. It should at least be implemented for Dovecot v2.1.
yeah that would be extrem nice there always some specials with i.e procmail does better ,not often ,but its nice to have
Timo, any comments?
Regards,
Stephan.
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
kjonca@o2.pl (Kamil Jońca) wrote:
Jerry dovecot.user@seibercom.net writes:
Below, I've provide the relevant snippets of my current functional configuration; how best to integrate procmail into the mix?
Why procmail? Use sieve instead. It is fully supported in Dovecot and IMHO far easier to use.
Well, how can I call external program from sieve? (For example for decoding some data, and put them to database?) Is any extension for this? KJ
I would suggest leaving sieve filtering for most users/mailboxes (delivery via dovecot's deliver) and executing deliver from procmail script of a few exceptions (delivery via procmail). [ I assume postix can be configured to do it ]
-- [pl>en: Andrew] Andrzej Adam Filip : anfi@onet.eu I never vote for anyone. I always vote against. -- W. C. Fields
participants (8)
-
/dev/rob0
-
Andrzej Adam Filip
-
errno
-
Harlan Stenn
-
Jerry
-
kjonca＠o2.pl
-
Robert Schetterer
-
Stephan Bosch