similar to: can deliver filter through spamc?

Hi there, I'm using Dovecot 2.0.9-1 under Arch Linux. Currently, I have Maildir configured, and I move all my emails into dovecot by using this sequence: 1) cron starts fetchmail periodically under user manfred to collect my mails from various email accounts. 2) In ~/.fetchmailrc I have configured /usr/bin/maildrop as MDA. 3) In ~/.mailfilter (used by maildrop) I have extensive filtering in

I'm currently using maildrop to do delivery, because I like to use it's xfilter to pipe through spamc. I don't see a similar option for dovecot's deliver. Is there something? It would be nice to use deliver, since I use dovecot for reading mail.

I need some advice about replacing maildrop with the Dovecot LDA. I need to replicate a setup that uses postfix+maildrop+spamassassin. We'll be using Dovecot 1rc13. In the current setup, maildrop reads a file called .mailfilter in each user's folder, then call spamassassin according to the user's preferences. The file is simple, and looks like this -- if ( $SIZE > 20971520 ) {

I'd like to be able to deliver certain mail as 'read' from procmail. My procmail rules call deliver with -m to directly to inject filtered mail to maildir based directories. I like to keep copies of mail I've sent by cc'ing it to myself and using procmail to filter and store copies in the appropriate directory. I cannot seem to find a way of delivering cc'd mail from

I've been using Dovecot in some fresh installs lately and have found it fairly easy to configure. However I'm starting on a migration that involves moving from some very old software (ancient vpopmail, qmail and Courier). On the Courier front, I've reviewed the migration page in the wiki, and it looks like the main concerns are just matching the namespace and then using the migration

I'm using maildrop for delivery, because I want to filter through spamassassin before delivery. Maildrop makes that trivial. It seems deliver can pipe (one way) to a command, but what is needed is to pipe: deliver -> spamd -> deliver which is what the maildrop xfilter does.

On 17.04.18 12:38, Aki Tuomi wrote: > > > > On 17.04.2018 12:36, Reio Remma wrote: >> Hello! >> >> I noticed SpamAssassin *spamc* usage has entered the documentation at >> https://wiki2.dovecot.org/HowTo/AntispamWithSieve >> >> I'm wondering if the -C (report) option in sa-learn-ham.sh should >> use revoke instead of report for --ham

Hello! I noticed SpamAssassin *spamc* usage has entered the documentation at https://wiki2.dovecot.org/HowTo/AntispamWithSieve I'm wondering if the -C (report) option in sa-learn-ham.sh should use revoke instead of report for --ham messages? I started using imapsieve with spamc myself just a few weeks ago, but I haven't used the reporting ability yet. Reio -------------- next part

I'm trying to get the pipe backend to work with the new dovecot-antispam (I was very pleased to see the new version, thanks Johannes!) Before I would run the following over the maildir: spamc -d 10.0.1.109 -L ham < $file 2>&1 > /dev/null now, i'm using dovecot-antispam and mdbox and have the following configured: antispam_backend = pipe antispam_signature = X-Spam-Flag

Hi, My server uses a system comprised of postfix, dovecot and dspam to filter and deliver mail. Postfix used the following flags in calling spamc and dovecot: flags=DRhu user=dovecot:secmail argv=/usr/bin/spamc -u ${recipient} -e /usr/lib/dovecot/deliver -d ${recipient} after an upgrade from Debian lenny to squeeze we were able to get everything working except spam filtering. Spamassassin is

Hello list, we are using dovecot-lmtp for delivery to virtual users, and vmm[1] to manage them. 1. http://vmm.localdomain.org/ One nice feature of vmm is that every virtual user has their own UID/GID on the UNIX filesystem. There is no passwd entry, so no shell login, but each user effectively has a home directory and can run commands in isolation and with lowered privileges. This requires

We're considering a move from Courier to Dovecot.? So far, looks like it's not too bad, but the most challenging obstacle is what to do about our local delivery.? Factors: 1. we use a lot of maildrop "features" that are impossible in sieve without piping to an external program (would rather not re-write our working maildrop scripts in another language) 2. would love to try

Hello list, Is there a way to call a spam filter in dovecot-lda like maildrop uses the xfilter command within the .mailfilter file to do the same? Eric

Hi, on my small Xen-virtualised server with 48 MiB RAM I use Postfix and Dovecot, because the Debian administrators dislike qmail [1], which is in my opinion despite some maintainability and code quality issues a quite well designed software, because it mostly follows the UNIX principles. Postfix is not able to sort my E-Mail into different Maildir folders and after I looked at procmail's

Dear Listmember, I use http://www.courier-mta.org/reformail.html for "Detecting duplicate messages" ### The -D option implements a simple way to delete duplicate messages in incoming mail. filename is a file that will be approximately 'len' bytes long. This file will be used by reformail to save message IDs seen in recent mail. reformail reads the message on standard input. If

Hi all, I am trying to setup a mail server using postfix (virtual_mailboxes), spamassassin and dovecot, along with SQL where appropriate. From my research so far I realized that, for several reasons, it is required for me to use dovecot LDA instead of maildrop, local, procmail or other alternatives. My configuration was working flawlessly, until spamassassin per-user configuration came to

Hi, I have written a plugin so that each time a message is added to a specific box, a program is run and the message is piped into it. Note that the message is also really added to the box. I've been using it for nearly 3 month, for spam/ham learning, and have not had any problem with it. I guess it could also be used to implement an out box (I remember seeing someone asking for such

> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > On 19.01.2018 04:35, Adam Weinberger wrote: >> Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. >> It seems to be happening when I use vnd.dovecot.filter. When I comment >> out the block, things come through fine. >> >> My filter block looks like

Op 1/20/2018 om 11:01 PM schreef Adam Weinberger: >> On 20 Jan, 2018, at 10:05, Adam Weinberger <adamw at adamw.org> wrote: >> >> >>> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >>> >>> >>> >>> On 19.01.2018 04:35, Adam Weinberger wrote: >>>> Since upgrading to 2.3.0 / 0.5.0.1, incoming