public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Setting up fetchmail to feed postfix
Date: Sun, 26 Nov 2017 15:05:00 -0800	[thread overview]
Message-ID: <20171126230500.3cw3b4u3xs6pbyah@matica.foolinux.mooo.com> (raw)
In-Reply-To: <CAGfcS_=OfALqhq5s7FpEQBCpg2cuFfhjcsvSBEcnJLhj52NrTw@mail.gmail.com>

On 2017-11-26 16:46, Rich Freeman wrote:

> You'll find this recipe all over the place, but with procmail you can
> do this:
> https://mymegabyte.com/2010/03/filter-duplicate-emails-with-procmail/

I don't trust procmail anymore after CVE-2017-16844.  It took me a long
time, I had a weak spot for it, you might say, despite its horrible
looking source.  But now it's over.  I have rewritten my delivery
framework using Perl and Mail::Audit, and I feel very relieved.

> I highly recommend using it.  Works on lists/direct/etc.  You won't
> find yourself complaining about crossposts, being on CC, or whatever
> again.

On the other list I mentioned, I am getting dupes after a _month_.
It would take a huge .msgid file to detect that, and remember formail
does a linear search through it.

I'm experimenting with using the filesystem as a hashtable, creating an
empty file based on each Message-ID header (of course I munge it to get
a valid filename).

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.


  reply	other threads:[~2017-11-26 23:05 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 15:39 [gentoo-user] Setting up fetchmail to feed postfix Peter Humphrey
2017-11-24 16:08 ` Wols Lists
2017-11-24 16:34   ` Peter Humphrey
2017-11-24 18:10     ` Matthias Hanft
2017-11-27 13:44       ` Peter Humphrey
2017-11-30  0:39         ` Peter Humphrey
2017-11-30  6:46           ` J. Roeleveld
2017-11-30  8:13           ` Neil Bothwick
2017-11-24 16:16 ` Ralph Seichter
2017-11-24 16:40   ` Peter Humphrey
2017-11-24 17:29     ` Ralph Seichter
2017-11-24 17:30   ` Rich Freeman
2017-11-24 17:52     ` Ralph Seichter
2017-11-27 13:44       ` Peter Humphrey
2017-11-27 16:13         ` Ralph Seichter
2017-11-27 17:48           ` [gentoo-user] " Ian Zimmerman
2017-11-27 19:10             ` Ralph Seichter
2017-11-27 22:14             ` Neil Bothwick
2017-11-28  0:23               ` Peter Humphrey
2017-11-26 10:25     ` [gentoo-user] " J. Roeleveld
2017-11-24 22:24 ` Neil Bothwick
2017-11-25  8:43   ` Marc Joliet
2017-11-25  9:04     ` Neil Bothwick
2017-11-25  9:23       ` Marc Joliet
2017-11-25 16:20         ` Jalus Bilieyich
2017-11-26  2:30           ` Peter Humphrey
2017-11-26  6:58             ` Alan McKinnon
2017-11-26 10:45               ` Peter Humphrey
2017-11-26 15:58               ` Jalus Bilieyich
2017-11-26  8:52             ` Neil Bothwick
2017-11-26 10:00             ` Ralph Seichter
2017-11-26 11:00               ` Peter Humphrey
2017-11-26 17:46               ` [gentoo-user] " Ian Zimmerman
2017-11-26 18:46                 ` Ralph Seichter
2017-11-26 19:35                   ` Jack
2017-11-26 20:58                   ` Wols Lists
2017-11-26 21:46                     ` Rich Freeman
2017-11-26 23:05                       ` Ian Zimmerman [this message]
2017-11-26 23:18                         ` Rich Freeman
2017-11-26 10:22             ` [gentoo-user] " J. Roeleveld
2017-11-26 15:25               ` Mick

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=20171126230500.3cw3b4u3xs6pbyah@matica.foolinux.mooo.com \
    --to=itz@very.loosely.org \
    --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