From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Looking for IMAP->IMAP spam filtering
Date: Tue, 21 Feb 2012 17:00:21 +0000 (UTC) [thread overview]
Message-ID: <ji0ij5$242$1@dough.gmane.org> (raw)
In-Reply-To: CAA2qdGVFHpb-S=zLApNQQ3dvDD7Myna8WPE-vKEM223s1CfcKg@mail.gmail.com
On 2012-02-21, Pandu Poluan <pandu@poluan.info> wrote:
> Okay, I may have misunderstood your needs the first time around
> (blame it to not having my first cuppa tea of the day).
>
> So, you want to do these steps:
> - Pull email from an IMAP account in box A
> - Filter it in box B
> - Push it to box C
Skip the box B part. Pull an e-mail from IMAP mailbox A, filter it,
then either discard it or append it to IMAP mailbox C (with A and C
possibly on different servers).
> So, the third step is not an LDA.
Right. Nothing's local except the filtering.
> There are some alternatives, none of them are simple, though. The
> 'easiest' I think would be:
>
> - have fetchmail (on box B) pull email from box A, and deliver to local
> maildir (on B) via procmail+SA
>
> - have Dovecot watch the local maildir
>
> - have *another* fetchmail instance pull email from the local Dovecot and
> push it to an SMTP MTA on box C
If I'm going to use the SMTP server on box C, then I don't think
there's a need for the intermediate maildir stop, since I can have
procmail pipe the message to something like msmtp to deliver it to the
SMTP server. There are a couple problem with using the SMTP server.
The first is that you can't specify a mailbox. The big problem is
that the SMTP server may rewrite headers. For example, if it's gmail's
SMTP server, it will always muck up the From: header so the message
appars to be from the account that was used to log in to the SMTP
server (you loose the original From: header). Using the IMAP server
allows you to store a message an any folder you want and the headers
are unchanged.
> You can have multiple fetchmail daemons running at the same time by
> copying/symlinking the fetchmail initscript and creating a
> correspondent conf file. I've submitted a patch (that has been
> accepted into the tree) that allows multiple fetchmail daemons.
I think it would be simpler to write an LDA that delivers a message to
an IMAP mailbox and have procmail pipe messages to that for delivery.
It should only take a couple dozen lines of Python... (famous last words)
--
Grant Edwards grant.b.edwards Yow! But was he mature
at enough last night at the
gmail.com lesbian masquerade?
prev parent reply other threads:[~2012-02-21 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 23:40 [gentoo-user] Looking for IMAP->IMAP spam filtering Grant Edwards
2012-02-21 0:00 ` [gentoo-user] " Grant Edwards
2012-02-21 1:02 ` Pandu Poluan
2012-02-21 1:26 ` Grant Edwards
2012-02-21 1:29 ` [gentoo-user] " Pandu Poluan
2012-02-21 17:00 ` Grant Edwards [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ji0ij5$242$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox