Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #178513 > unrolled thread

procmail, when were the last rights administered?

Back to article view | Back to linux.debian.user

Contents

  procmail, when were the last rights administered? Gene Heskett <gheskett@shentel.net> - 2017-03-07 03:40 +0100
    Re: procmail, when were the last rights administered? Andy Smith <andy@strugglers.net> - 2017-03-07 03:50 +0100
      Re: procmail, when were the last rights administered? Andy Smith <andy@strugglers.net> - 2017-03-07 04:00 +0100
        Re: procmail, when were the last rights administered? Gene Heskett <gheskett@shentel.net> - 2017-03-07 04:10 +0100
      Re: procmail, when were the last rights administered? Gene Heskett <gheskett@shentel.net> - 2017-03-07 04:00 +0100
        Re: procmail, when were the last rights administered? Henning Follmann <hfollmann@itcfollmann.com> - 2017-03-07 15:50 +0100
          Re: procmail, when were the last rights administered? Jude DaShiell <jdashiel@panix.com> - 2017-03-07 17:20 +0100
          Re: procmail, when were the last rights administered? David Wright <deblis@lionunicorn.co.uk> - 2017-03-07 17:20 +0100
            Re: procmail, when were the last rights administered? Gene Heskett <gheskett@shentel.net> - 2017-03-07 20:30 +0100
              Re: procmail, when were the last rights administered? David Wright <deblis@lionunicorn.co.uk> - 2017-03-07 23:20 +0100
                Re: procmail, when were the last rights administered? Gene Heskett <gheskett@shentel.net> - 2017-03-08 03:20 +0100
    Re: procmail, when were the last rights administered? Jonathan Dowland <jmtd@debian.org> - 2017-03-07 11:10 +0100

#178513 — procmail, when were the last rights administered?

And what replaces it in the MTA dept?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [next] | [standalone]

#178514

Hi Gene,

On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> And what replaces it in the MTA dept?

procmail is still in Debian stretch and if it still works for you
then it should continue to work for you.

More modern alternatives include Sieve:

    http://sieve.info/clients

and maildrop:

    http://www.courier-mta.org/maildrop/

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

"I remember the first time I made love.  Perhaps it was not love exactly but I
 made it and it still works." — The League Against Tedium

[toc] | [prev] | [next] | [standalone]

#178515

On Tue, Mar 07, 2017 at 02:47:42AM +0000, Andy Smith wrote:
> On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> > And what replaces it in the MTA dept?

Oh, and procmail is not an MTA (and neither is maildrop…), but more
correctly a Mail Delivery Agent, but I got what you meant.

Sieve is a mail filtering language that is implemented by multiple
different MDAs, but also some Mail User Agents and Mail Transfer
Agents.

Cheers,
Andy

[toc] | [prev] | [next] | [standalone]

#178517

On Monday 06 March 2017 21:54:26 Andy Smith wrote:

> On Tue, Mar 07, 2017 at 02:47:42AM +0000, Andy Smith wrote:
> > On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> > > And what replaces it in the MTA dept?
>
> Oh, and procmail is not an MTA (and neither is maildrop…), but more
> correctly a Mail Delivery Agent, but I got what you meant.
>
Correct, I should have said MDA, because fetchmail pulls my email for me.

> Sieve is a mail filtering language that is implemented by multiple
> different MDAs, but also some Mail User Agents and Mail Transfer
> Agents.
>
> Cheers,
> Andy


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#178516

On Monday 06 March 2017 21:47:42 Andy Smith wrote:

> Hi Gene,
>
> On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> > And what replaces it in the MTA dept?
>
> procmail is still in Debian stretch and if it still works for you
> then it should continue to work for you.
>
I wanted to add a formail line but the docs do not seem to cover that 
recipe. I want an email to gene@localhost when it sequesters a virii.

> More modern alternatives include Sieve:
>
>     http://sieve.info/clients
>
> and maildrop:
>
>     http://www.courier-mta.org/maildrop/
>
> Cheers,
> Andy


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#178536

On Mon, Mar 06, 2017 at 09:59:16PM -0500, Gene Heskett wrote:
> On Monday 06 March 2017 21:47:42 Andy Smith wrote:
> 
> > Hi Gene,
> >
> > On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> > > And what replaces it in the MTA dept?
> >
> > procmail is still in Debian stretch and if it still works for you
> > then it should continue to work for you.
> >
> I wanted to add a formail line but the docs do not seem to cover that 
> recipe. I want an email to gene@localhost when it sequesters a virii.
> 
[...]

What do you mean by "formail line"?
formail is a command to pipe a mbox thru procmail.

-H


-- 
Henning Follmann           | hfollmann@itcfollmann.com

[toc] | [prev] | [next] | [standalone]

#178540

formail can also force correct formatting on incoming email. On Tue, 7 Mar 
2017, Henning Follmann wrote:

> Date: Tue, 7 Mar 2017 09:43:17
> From: Henning Follmann <hfollmann@itcfollmann.com>
> To: Gene Heskett <gheskett@shentel.net>
> Cc: debian-user@lists.debian.org
> Subject: Re: procmail, when were the last rights administered?
> Resent-Date: Tue,  7 Mar 2017 14:43:46 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> On Mon, Mar 06, 2017 at 09:59:16PM -0500, Gene Heskett wrote:
>> On Monday 06 March 2017 21:47:42 Andy Smith wrote:
>>
>>> Hi Gene,
>>>
>>> On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
>>>> And what replaces it in the MTA dept?
>>>
>>> procmail is still in Debian stretch and if it still works for you
>>> then it should continue to work for you.
>>>
>> I wanted to add a formail line but the docs do not seem to cover that
>> recipe. I want an email to gene@localhost when it sequesters a virii.
>>
> [...]
>
> What do you mean by "formail line"?
> formail is a command to pipe a mbox thru procmail.
>
> -H
>
>
>

-- 

[toc] | [prev] | [next] | [standalone]

#178541

On Tue 07 Mar 2017 at 09:43:17 (-0500), Henning Follmann wrote:
> On Mon, Mar 06, 2017 at 09:59:16PM -0500, Gene Heskett wrote:
> > On Monday 06 March 2017 21:47:42 Andy Smith wrote:
> > 
> > > Hi Gene,
> > >
> > > On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> > > > And what replaces it in the MTA dept?
> > >
> > > procmail is still in Debian stretch and if it still works for you
> > > then it should continue to work for you.
> > >
> > I wanted to add a formail line but the docs do not seem to cover that 
> > recipe. I want an email to gene@localhost when it sequesters a virii.
> > 
> [...]
> 
> What do you mean by "formail line"?
> formail is a command to pipe a mbox thru procmail.

Yes, but it's also used _by_ procmail during its processing.
For example, here's a standard procmailrc recipe for eliminating
messages with identical Message-IDs:

:0 Wh: $HOME/msgid.lock
| formail -D 199999 $HOME/msgid.cache

So Gene might be looking for a potted recipe for formail to do what he
wants, whatever he means by "sequesters a virii", and recipes with
formail in them might make good examples to hack at.

The obvious place to start is procmailex: insert the safety net; then
the example above shows the W code for checking the exit code of
formail/virus-scanner/whatever before proceeding, then the vacation
example would help with how to generate the desired email
notification depending on the exit code. Remember to add the c flag
so that the recipe is non-delivering: that means the actual (received)
email will always drop through to the next recipe. Otherwise, piping
through the virus-scanner might be interpreted as "delivery". After
testing remove the safety net if desired.

man procmail/procmailrc/procmailex/formail all work here on wheezy and
jessie, so I'm not sure why he felt the need to put Alternative Facts
into his Subject header.

Cheers,
David.

PS I dodged your bullet (mail-followup-to).

[toc] | [prev] | [next] | [standalone]

#178552

On Tuesday 07 March 2017 11:16:55 David Wright wrote:

> On Tue 07 Mar 2017 at 09:43:17 (-0500), Henning Follmann wrote:
> > On Mon, Mar 06, 2017 at 09:59:16PM -0500, Gene Heskett wrote:
> > > On Monday 06 March 2017 21:47:42 Andy Smith wrote:
> > > > Hi Gene,
> > > >
> > > > On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> > > > > And what replaces it in the MTA dept?
> > > >
> > > > procmail is still in Debian stretch and if it still works for
> > > > you then it should continue to work for you.
> > >
> > > I wanted to add a formail line but the docs do not seem to cover
> > > that recipe. I want an email to gene@localhost when it sequesters
> > > a virii.
> >
> > [...]
> >
> > What do you mean by "formail line"?
> > formail is a command to pipe a mbox thru procmail.
>
> Yes, but it's also used _by_ procmail during its processing.
> For example, here's a standard procmailrc recipe for eliminating
>
> messages with identical Message-IDs:
> :0 Wh: $HOME/msgid.lock
> :
> | formail -D 199999 $HOME/msgid.cache
>
> So Gene might be looking for a potted recipe for formail to do what he
> wants, whatever he means by "sequesters a virii", and recipes with
> formail in them might make good examples to hack at.
>
> The obvious place to start is procmailex: insert the safety net; then
> the example above shows the W code for checking the exit code of
> formail/virus-scanner/whatever before proceeding, then the vacation
> example would help with how to generate the desired email
> notification depending on the exit code. Remember to add the c flag
> so that the recipe is non-delivering: that means the actual (received)
> email will always drop through to the next recipe. Otherwise, piping
> through the virus-scanner might be interpreted as "delivery". After
> testing remove the safety net if desired.
>
> man procmail/procmailrc/procmailex/formail all work here on wheezy and
> jessie, so I'm not sure why he felt the need to put Alternative Facts
> into his Subject header.
>
Because the procmail web site has had a moving site message up since 
sometime in 2014?

And I've been told repeatedly that "its dead Jim", try something else.
But I'm with you folks, for me it Just Works(TM) but I've long since 
forgotten the how to write a new recipe part for it.

> Cheers,
> David.
>
> PS I dodged your bullet (mail-followup-to).


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#178559

On Tue 07 Mar 2017 at 14:21:41 (-0500), Gene Heskett wrote:
> On Tuesday 07 March 2017 11:16:55 David Wright wrote:
> 
> > On Tue 07 Mar 2017 at 09:43:17 (-0500), Henning Follmann wrote:
> > > On Mon, Mar 06, 2017 at 09:59:16PM -0500, Gene Heskett wrote:
> > > > On Monday 06 March 2017 21:47:42 Andy Smith wrote:
> > > > > Hi Gene,
> > > > >
> > > > > On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> > > > > > And what replaces it in the MTA dept?
> > > > >
> > > > > procmail is still in Debian stretch and if it still works for
> > > > > you then it should continue to work for you.
> > > >
> > > > I wanted to add a formail line but the docs do not seem to cover
> > > > that recipe. I want an email to gene@localhost when it sequesters
> > > > a virii.
> > >
> > > [...]
> > >
> > > What do you mean by "formail line"?
> > > formail is a command to pipe a mbox thru procmail.
> >
> > Yes, but it's also used _by_ procmail during its processing.
> > For example, here's a standard procmailrc recipe for eliminating
> >
> > messages with identical Message-IDs:
> > :0 Wh: $HOME/msgid.lock
> > :
> > | formail -D 199999 $HOME/msgid.cache
> >
> > So Gene might be looking for a potted recipe for formail to do what he
> > wants, whatever he means by "sequesters a virii", and recipes with
> > formail in them might make good examples to hack at.
> >
> > The obvious place to start is procmailex: insert the safety net; then
> > the example above shows the W code for checking the exit code of
> > formail/virus-scanner/whatever before proceeding, then the vacation
> > example would help with how to generate the desired email
> > notification depending on the exit code. Remember to add the c flag
> > so that the recipe is non-delivering: that means the actual (received)
> > email will always drop through to the next recipe. Otherwise, piping
> > through the virus-scanner might be interpreted as "delivery". After
> > testing remove the safety net if desired.
> >
> > man procmail/procmailrc/procmailex/formail all work here on wheezy and
> > jessie, so I'm not sure why he felt the need to put Alternative Facts
> > into his Subject header.
> >
> Because the procmail web site has had a moving site message up since 
> sometime in 2014?
> 
> And I've been told repeatedly that "its dead Jim", try something else.
> But I'm with you folks, for me it Just Works(TM) but I've long since 
> forgotten the how to write a new recipe part for it.

Yes, my last modification date for .procmailrc is 2004-03-30.
But that's what   man procmailex   is for, a 500-line file of
glossed recipes catering for different situations. With the
hints above, which part of the jigsaw are you missing?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#178560

On Tuesday 07 March 2017 17:16:28 David Wright wrote:

> On Tue 07 Mar 2017 at 14:21:41 (-0500), Gene Heskett wrote:
> > On Tuesday 07 March 2017 11:16:55 David Wright wrote:
> > > On Tue 07 Mar 2017 at 09:43:17 (-0500), Henning Follmann wrote:
> > > > On Mon, Mar 06, 2017 at 09:59:16PM -0500, Gene Heskett wrote:
> > > > > On Monday 06 March 2017 21:47:42 Andy Smith wrote:
> > > > > > Hi Gene,
> > > > > >
> > > > > > On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> > > > > > > And what replaces it in the MTA dept?
> > > > > >
> > > > > > procmail is still in Debian stretch and if it still works
> > > > > > for you then it should continue to work for you.
> > > > >
> > > > > I wanted to add a formail line but the docs do not seem to
> > > > > cover that recipe. I want an email to gene@localhost when it
> > > > > sequesters a virii.
> > > >
> > > > [...]
> > > >
> > > > What do you mean by "formail line"?
> > > > formail is a command to pipe a mbox thru procmail.
> > >
> > > Yes, but it's also used _by_ procmail during its processing.
> > > For example, here's a standard procmailrc recipe for eliminating
> > >
> > > messages with identical Message-IDs:
> > > :0 Wh: $HOME/msgid.lock
> > > :
> > > | formail -D 199999 $HOME/msgid.cache
> > >
> > > So Gene might be looking for a potted recipe for formail to do
> > > what he wants, whatever he means by "sequesters a virii", and
> > > recipes with formail in them might make good examples to hack at.
> > >
> > > The obvious place to start is procmailex: insert the safety net;
> > > then the example above shows the W code for checking the exit code
> > > of formail/virus-scanner/whatever before proceeding, then the
> > > vacation example would help with how to generate the desired email
> > > notification depending on the exit code. Remember to add the c
> > > flag so that the recipe is non-delivering: that means the actual
> > > (received) email will always drop through to the next recipe.
> > > Otherwise, piping through the virus-scanner might be interpreted
> > > as "delivery". After testing remove the safety net if desired.
> > >
> > > man procmail/procmailrc/procmailex/formail all work here on wheezy
> > > and jessie, so I'm not sure why he felt the need to put
> > > Alternative Facts into his Subject header.
> >
> > Because the procmail web site has had a moving site message up since
> > sometime in 2014?
> >
> > And I've been told repeatedly that "its dead Jim", try something
> > else. But I'm with you folks, for me it Just Works(TM) but I've long
> > since forgotten the how to write a new recipe part for it.
>
> Yes, my last modification date for .procmailrc is 2004-03-30.
> But that's what   man procmailex   is for, a 500-line file of
> glossed recipes catering for different situations. With the
> hints above, which part of the jigsaw are you missing?
>
> Cheers,
> David.

How to make this recipe pair send me an email when it trips.
# Scan for viruses
:0
VIRUS=|clamdscan --stdout -

:0w
* VIRUS ?? ^.*: \/.* FOUND
$VIRIBOX


That would be to "gene@localhost"

Thanks.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#178527

[Multipart message — attachments visible in raw view] — view raw

On Mon, Mar 06, 2017 at 09:29:37PM -0500, Gene Heskett wrote:
> And what replaces it in the MTA dept?

I still use procmail myself, but I do think about moving away one day.

If you are using Exim, and if your mail arrival route is via your Exim
(you mention fetchmail in follow-up email but I am not sure whether or
not fetchmail will route the fetched mail via the local MTA), then you
could take a look at Exim filters. I've been recommended them a few
times but they can't do everything you can achieve with procmail (and,
I think vice versa)

http://www.exim.org/exim-html-current/doc/html/spec_html/filter_ch-forwarding_and_filtering_in_exim.html
 
Otherwise investigate Sieve as others have said.


-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web