Re: Procmail no filtra correctamente

[Lic. Domingo Varela Yahuitl]

http://www.linuxsc.net/filtrado-de-correo-con-procmail/




Enviado desde mi Samsung Mobile de Telcel
Obtener Outlook para Android


De: Aaron D. 
Enviado: jueves, 11 de febrero de 2021 03:37
Para: debian-user-spanish@lists.debian.org
Asunto: Procmail no filtra correctamente

Buenos días lista, tengo un problema con el siguiente filtro de
procmail:

:0:
* ^From: noveda...@amazon.es
publicity/

El resto de filtros (como de la lista) funcionan perfectamente, pero
los correos de amazon me siguen llegando al inbox (la dirección es
correcta).

Alguna idea?
--
Aaron D.

Re: Procmail no filtra correctamente

[Camaleón]

El 2021-02-11 a las 10:37 +0100, Aaron D. escribió:

> Buenos días lista, tengo un problema con el siguiente filtro de
> procmail:
> 
> :0:
> * ^From: noveda...@amazon.es
> publicity/
> 
> El resto de filtros (como de la lista) funcionan perfectamente, pero
> los correos de amazon me siguen llegando al inbox (la dirección es
> correcta).
> 
> Alguna idea?

Hum... nunca he usado Procmail pero si se basa en expresiones regulares 
convecionales, prueba a delimitar mejor el texto que te interesa 
filtrar:

* ^From:.*noveda...@amazon.es.*

En la wiki¹ de Archlinux tienes otro ejemplo:

* ^From.* someperson@\w+.com

¹https://wiki.archlinux.org/index.php/Procmail#Conditions

Saludos,

-- 
Camaleón 

Re: procmail, when were the last rights administered?

[Gene Heskett]

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 19 $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 

Re: procmail, when were the last rights administered?

[David Wright]

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 19 $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.

Re: procmail, when were the last rights administered?

[Gene Heskett]

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 19 $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 

Re: procmail, when were the last rights administered?

[Jude DaShiell]

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 <hfollm...@itcfollmann.com>
To: Gene Heskett <ghesk...@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 + (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





--

Re: procmail, when were the last rights administered?

[David Wright]

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 19 $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).

Re: procmail, when were the last rights administered?

[Henning Follmann]

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   | hfollm...@itcfollmann.com

Re: procmail, when were the last rights administered?

[Jonathan Dowland]

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.


signature.asc
Description: Digital signature

Re: procmail, when were the last rights administered?

[Gene Heskett]

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

> On Tue, Mar 07, 2017 at 02:47:42AM +, 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 

Re: procmail, when were the last rights administered?

[Gene Heskett]

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 

Re: procmail, when were the last rights administered?

[Andy Smith]

On Tue, Mar 07, 2017 at 02:47:42AM +, 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

Re: procmail, when were the last rights administered?

[Andy Smith]

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

Re: procmail

[ricky gutierrez]

El día 22 de octubre de 2014, 16:34, Santiago Vila sanv...@unex.es escribió:

 Si ese es el log del usuario, entonces ya vamos mal, porque procmail,
 cuando entrega un mensaje a un usuario, suele hacerlo con la identidad
 del propio usuario, y si el fichero log es de root y del grupo
 postfix, malamente podrá escribir nada ahí.

Ok , he estado probando varias ejemplos en la web si lograr algun
resultado , dentro del directorio /home/email/dominio
estan todos mis usuarios virtuales de postfix , ese directorio postfix
tiene que tener lectura y escritura.



 Otra cosa rara que veo es que no defines en ninguna parte la variable
 DEFAULT. Si tu configuración no es estándar (mbox en /var/mail/usuario)
 probablemente te hará falta.

ahora he probado este ejemplo donde aparece el DEFAULT como ruta por
defecto de mi directorio de buzon.

HELL=/bin/bash
PATH=/usr/bin:/bin
DROPPRIVS=yes
MAILDIR=/home/email/$DOMAIN/$USER/
DEFAULT=$MAILDIR/
LOGFILE=$MAILDIR/procmail.log # .
#VERBOSE=ON # ..

:0:
* ^X-Spam-Status: Yes
$Spam





 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/2014103405.GA19383@dell




-- 
rickygm

http://gnuforever.homelinux.com


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAL_GE3QMumEhM+gkNYDnPEYX8cXBND9V2BJU(yq461dNBL=g...@mail.gmail.com

Re: procmail

[Camaleón]

El Wed, 22 Oct 2014 12:40:17 -0600, ricky gutierrez escribió:

 saludos lista , estoy lidiando con una configuración de procmail y los
 mensajes marcados como spam por mi amavisd+spamassassin , la idea es qu
 mueva todo los mensajes marcados como spam a una carpeta llamada Spam
 dentro de su home/maildir .
 
 estoy usando maildir y postfixadmin con usuarios virtuales y testado
 esta configuración sin éxito.

Antes de nada asegúrate de que en la cabecera de los correos aparezca la 
marca del SA (X-Spam-Flag) ya que dependiendo de la configuración del SA 
puede incluirse sólo en determinados casos.

Comprueba también que no haya ningún archivo de Postfix que invalide el
archivo de configuración de Procmail ya que Postfix tendrá preferencia. 
 
 tengo un un archivo llamado  procmailrc dentro de /etc y lo mando a
 llamar desde el main.cf en postfix.
 
 :0 MAILDIR=$HOME/email/$DOMAIN/$USER/
 
 :
 ^X-Spam-Flag.*YES .Spam/
 
 pero no me esta dando resultado.
 
 alguna idea?

Nunca he usado Procmail pero en Internet tienes recetas para la 
configuración de filtros, por ejemplo:

Filtering Spam with Procmail (UNIX/ Linux) — Advanced
http://blink.ucsd.edu/technology/email/spam/filters/procmail-a.html

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2014.10.23.14.44...@gmail.com

Re: procmail

[ricky gutierrez]

El día 23 de octubre de 2014, 8:44, Camaleón noela...@gmail.com escribió:

 Antes de nada asegúrate de que en la cabecera de los correos aparezca la
 marca del SA (X-Spam-Flag) ya que dependiendo de la configuración del SA
 puede incluirse sólo en determinados casos.

Hola , lo esta haciendo perfecto.

X-Spam-Flag: YES
X-Spam-Score: 10.67
X-Spam-Level: **
X-Spam-Status: Yes, score=10.67



 Comprueba también que no haya ningún archivo de Postfix que invalide el
 archivo de configuración de Procmail ya que Postfix tendrá preferencia.

la verdad no , he probado tanto como en /etc/procmailrc y
/home/email/dominio/usuario/.procmailrc

sldss



http://gnuforever.homelinux.com


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAL_GE3Ttp0VvbSqFHN9PLzd8PPhEGsStLE_uxAaP0g�5g...@mail.gmail.com

Re: procmail

[Camaleón]

El Thu, 23 Oct 2014 08:49:08 -0600, ricky gutierrez escribió:

 El día 23 de octubre de 2014, 8:44, Camaleón noela...@gmail.com
 escribió:
 
 Antes de nada asegúrate de que en la cabecera de los correos aparezca
 la marca del SA (X-Spam-Flag) ya que dependiendo de la configuración
 del SA puede incluirse sólo en determinados casos.
 
 Hola , lo esta haciendo perfecto.
 
 X-Spam-Flag: YES 

(...)

Perfecto pues.

No sé si habrás probado con la receta del enlace que te pasado, que 
parece bastante sencilla:

# Catch SPAM
:0:
* ^X-Spam-Flag: YES
Spam

Como te he dicho antes de Procmail estoy pez pero yo comprobaría si 
permite trabajar con el formato maildir o si hay que configurar algo 
especial para que reconozca este tipo de buzones.

Más enlacitos 8:-)

Procmail recipes for Maildir folders
http://www.panix.com/help/procmail-maildir.html

Procmail - setup with postfix
http://wiki.kartbuilding.net/index.php/Procmail_-_setup_with_postfix
 
 Comprueba también que no haya ningún archivo de Postfix que invalide el
 archivo de configuración de Procmail ya que Postfix tendrá preferencia.
 
 la verdad no , he probado tanto como en /etc/procmailrc y
 /home/email/dominio/usuario/.procmailrc

Cuando usas una entrega local Postfix puede crear archivos ~/.forward 
para redirigir los mensajes y esto puede chocar con los filtros de 
Procmail.

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2014.10.23.15.13...@gmail.com

Re: procmail

[ricky gutierrez]

El día 23 de octubre de 2014, 9:13, Camaleón noela...@gmail.com escribió:


 Hola , lo esta haciendo perfecto.

 X-Spam-Flag: YES

 (...)

 Perfecto pues.

 No sé si habrás probado con la receta del enlace que te pasado, que
 parece bastante sencilla:

 # Catch SPAM
 :0:
 * ^X-Spam-Flag: YES
 Spam


Se parece al que tenia anteriormente.

 Como te he dicho antes de Procmail estoy pez pero yo comprobaría si
 permite trabajar con el formato maildir o si hay que configurar algo
 especial para que reconozca este tipo de buzones.

 Más enlacitos 8:-)

 Procmail recipes for Maildir folders
 http://www.panix.com/help/procmail-maildir.html

 Procmail - setup with postfix
 http://wiki.kartbuilding.net/index.php/Procmail_-_setup_with_postfix

probare.


 Comprueba también que no haya ningún archivo de Postfix que invalide el
 archivo de configuración de Procmail ya que Postfix tendrá preferencia.

 la verdad no , he probado tanto como en /etc/procmailrc y
 /home/email/dominio/usuario/.procmailrc

 Cuando usas una entrega local Postfix puede crear archivos ~/.forward
 para redirigir los mensajes y esto puede chocar con los filtros de
 Procmail.


como se podra comprobar esto?

slds y gracias ..


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAL_GE3Tb-K_FP0YQe3B182q5kgbUTczJQ_+_7nFaN=rn40+...@mail.gmail.com

Re: procmail

[Camaleón]

El Thu, 23 Oct 2014 09:30:52 -0600, ricky gutierrez escribió:

 El día 23 de octubre de 2014, 9:13, Camaleón noela...@gmail.com
 escribió:

(...)

 Comprueba también que no haya ningún archivo de Postfix que invalide
 el archivo de configuración de Procmail ya que Postfix tendrá
 preferencia.

 la verdad no , he probado tanto como en /etc/procmailrc y
 /home/email/dominio/usuario/.procmailrc

 Cuando usas una entrega local Postfix puede crear archivos
 ~/.forward
 para redirigir los mensajes y esto puede chocar con los filtros de
 Procmail.


 como se podra comprobar esto?

Son archivos que se encuentran en los directorios /home de los usuarios, 
podrás buscarlos a ojo o con la herramienta que más rabia te dé:

find $HOME/ -name *.forward

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2014.10.23.16.04...@gmail.com

Re: procmail

[ricky gutierrez]

Bueno al final me cance de procmail , estoy medio hechando a andar
sieve con dovecot , pero abrire otro hilo.

slsss

El día 23 de octubre de 2014, 10:04, Camaleón noela...@gmail.com escribió:
 El Thu, 23 Oct 2014 09:30:52 -0600, ricky gutierrez escribió:

 El día 23 de octubre de 2014, 9:13, Camaleón noela...@gmail.com
 escribió:

 (...)

 Comprueba también que no haya ningún archivo de Postfix que invalide
 el archivo de configuración de Procmail ya que Postfix tendrá
 preferencia.

 la verdad no , he probado tanto como en /etc/procmailrc y
 /home/email/dominio/usuario/.procmailrc

 Cuando usas una entrega local Postfix puede crear archivos
 ~/.forward
 para redirigir los mensajes y esto puede chocar con los filtros de
 Procmail.


 como se podra comprobar esto?

 Son archivos que se encuentran en los directorios /home de los usuarios,
 podrás buscarlos a ojo o con la herramienta que más rabia te dé:

 find $HOME/ -name *.forward

 Saludos,

 --
 Camaleón


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/pan.2014.10.23.16.04...@gmail.com




-- 
rickygm

http://gnuforever.homelinux.com


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAL_GE3RgUxTMfg7RekG=a+amqekh90exs3gh-so--h45ptf...@mail.gmail.com

Re: procmail

[Santiago Vila]

On Wed, Oct 22, 2014 at 12:40:17PM -0600, ricky gutierrez wrote:
 [ problemas con procmail ]
 alguna idea?

Añade

LOGFILE=fichero-escribible

y mira dentro para ver qué sucede. Si no es suficiente añade también

VERBOSE=yes


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141022203923.ga...@cantor.unex.es

Re: procmail

[ricky gutierrez]

Hola , hace unos 20 mn lo hice y creado un procmail.log en cada
carpeta de usuario , pero no veo que escriba nada

#cat /etc/procmailrc
:0
MAILDIR=$HOME/email/$DOMAIN/$USER/
LOGFILE=$MAILDIR/procmail.log
VERBOSE = yes
:
^X-Spam-Flag.*YES
.Spam/

2014-10-22 14:39 GMT-06:00 Santiago Vila sanv...@unex.es:
 On Wed, Oct 22, 2014 at 12:40:17PM -0600, ricky gutierrez wrote:
 [ problemas con procmail ]
 alguna idea?

 Añade

 LOGFILE=fichero-escribible

 y mira dentro para ver qué sucede. Si no es suficiente añade también

 VERBOSE=yes


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/20141022203923.ga...@cantor.unex.es




-- 
rickygm

http://gnuforever.homelinux.com


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cal_ge3rlzayp0cyto7_yhr5lz-wbnr0jxljskpv6-k5xcmq...@mail.gmail.com

Re: procmail

[Manolo Díaz]

El miércoles, 22 oct 2014 a las 23:22 horas (UTC+2),
ricky gutierrez escribió:

Hola , hace unos 20 mn lo hice y creado un procmail.log en cada
carpeta de usuario , pero no veo que escriba nada

No es un problema de permisos de escritura, supongo.

#cat /etc/procmailrc
:0
MAILDIR=$HOME/email/$DOMAIN/$USER/
LOGFILE=$MAILDIR/procmail.log
VERBOSE = yes
:
^X-Spam-Flag.*YES
.Spam/

2014-10-22 14:39 GMT-06:00 Santiago Vila sanv...@unex.es:
 On Wed, Oct 22, 2014 at 12:40:17PM -0600, ricky gutierrez wrote:
 [ problemas con procmail ]
 alguna idea?

 Añade

 LOGFILE=fichero-escribible

 y mira dentro para ver qué sucede. Si no es suficiente añade también

 VERBOSE=yes


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/20141022203923.ga...@cantor.unex.es







-- 
Manolo Díaz


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141022234138.45c37...@gmail.com

Re: procmail

[ricky gutierrez]

No , los permisos los veo bien

#ls -l procmail.log
-rwxrwx--- 1 root postfix 0 Oct 22 15:20 procmail.log

dentro del directorio del usuario

El día 22 de octubre de 2014, 15:41, Manolo Díaz
diaz.man...@gmail.com escribió:
 El miércoles, 22 oct 2014 a las 23:22 horas (UTC+2),
 ricky gutierrez escribió:

Hola , hace unos 20 mn lo hice y creado un procmail.log en cada
carpeta de usuario , pero no veo que escriba nada

 No es un problema de permisos de escritura, supongo.

#cat /etc/procmailrc
:0
MAILDIR=$HOME/email/$DOMAIN/$USER/
LOGFILE=$MAILDIR/procmail.log
VERBOSE = yes
:
^X-Spam-Flag.*YES
.Spam/

2014-10-22 14:39 GMT-06:00 Santiago Vila sanv...@unex.es:
 On Wed, Oct 22, 2014 at 12:40:17PM -0600, ricky gutierrez wrote:
 [ problemas con procmail ]
 alguna idea?

 Añade

 LOGFILE=fichero-escribible

 y mira dentro para ver qué sucede. Si no es suficiente añade también

 VERBOSE=yes


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact 
 listmas...@lists.debian.org
 Archive: https://lists.debian.org/20141022203923.ga...@cantor.unex.es







 --
 Manolo Díaz


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/20141022234138.45c37...@gmail.com




-- 
rickygm

http://gnuforever.homelinux.com


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cal_ge3teg8kwrdotmu9xmo8vqojkroytiis04+hfa2v1l81...@mail.gmail.com

Re: procmail

[Manolo Díaz]

El miércoles, 22 oct 2014 a las 23:45 horas (UTC+2),
ricky gutierrez escribió:

No , los permisos los veo bien

#ls -l procmail.log
-rwxrwx--- 1 root postfix 0 Oct 22 15:20 procmail.log

dentro del directorio del usuario

Te lo comento porque hace mcho usé procmail, y recuerdo problemas
de permisos. Creo recordar que procmail funcionaba bajo un usuario
propio, distinto al de postfix. ¿Puedes comprobarlo?

-- 
Manolo Díaz


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141023001209.7ba06...@gmail.com

Re: procmail

[Santiago Vila]

On Wed, Oct 22, 2014 at 03:45:22PM -0600, ricky gutierrez wrote:
 No , los permisos los veo bien
 
 #ls -l procmail.log
 -rwxrwx--- 1 root postfix 0 Oct 22 15:20 procmail.log
 
 dentro del directorio del usuario

Si ese es el log del usuario, entonces ya vamos mal, porque procmail,
cuando entrega un mensaje a un usuario, suele hacerlo con la identidad
del propio usuario, y si el fichero log es de root y del grupo
postfix, malamente podrá escribir nada ahí.

Otra cosa rara que veo es que no defines en ninguna parte la variable
DEFAULT. Si tu configuración no es estándar (mbox en /var/mail/usuario)
probablemente te hará falta.


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2014103405.GA19383@dell

Re: procmail et clamav

[Bernard Schoenacker]

Le Thu, 5 Jun 2014 17:27:25 +0200,
Bernard Schoenacker bernard.schoenac...@free.fr a écrit :

 bonjour,
 
 je n'ai pas trouvé de règle pour clamav et procmail
 
 
 slt
 bernard
 

bonjour,


j'ai trouvé chez ubuntu (manpage) la recette qui convient :

http://manpages.ubuntu.com/manpages/dapper/man1/clamassassin.1.html

PROCMAIL

   To pass your mail through clamassassin, add the  following
   command  to your procmailrc file (/etc/procmailrc or
   ~/.procmailrc):

:0fw
|/usr/bin/clamassassin

   The  above  will  forward  the  mail  to  clamassassin,  which
   will use /usr/bin/clamscan to scan the mail, and add the
   headers  X-Virus-Status and  X-Virus-Report  as appropriate. To
   filter infected mails, you have to set an additional 
   filter-rule:

:0:
* ^X-Virus-Status: Yes
IN.virus

   In this example, all infected mails are sorted to the
   IN.virus  mail folder.  If  you want to destroy such messages
   altogether, you can also change IN.virus to /dev/null.

   Forfurtherinformation,please have a
   look at /usr/share/doc/clamassassin/.


slt
bernard

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/20140605175931.40e259f3@hamtaro

Re: procmail et clamav

[BERTRAND Joël]

Bernard Schoenacker a écrit :

Le Thu, 5 Jun 2014 17:27:25 +0200,
Bernard Schoenacker bernard.schoenac...@free.fr a écrit :


bonjour,

je n'ai pas trouvé de règle pour clamav et procmail


slt
bernard



bonjour,


j'ai trouvé chez ubuntu (manpage) la recette qui convient :

http://manpages.ubuntu.com/manpages/dapper/man1/clamassassin.1.html

PROCMAIL

To pass your mail through clamassassin, add the  following
command  to your procmailrc file (/etc/procmailrc or
~/.procmailrc):

 :0fw
 |/usr/bin/clamassassin

The  above  will  forward  the  mail  to  clamassassin,  which
will use /usr/bin/clamscan to scan the mail, and add the
headers  X-Virus-Status and  X-Virus-Report  as appropriate. To
filter infected mails, you have to set an additional
filter-rule:

 :0:
 * ^X-Virus-Status: Yes
 IN.virus

In this example, all infected mails are sorted to the
IN.virus  mail folder.  If  you want to destroy such messages
altogether, you can also change IN.virus to /dev/null.

Forfurtherinformation,please have a
look at /usr/share/doc/clamassassin/.


slt
bernard



Bonsoir,

	Je ne comprends pas trop pourquoi tu cherches à utiliser procmail pour 
cela (mais sans nous indiquer ton MTA, difficile d'en dire plus).


	Procmail est appelé une fois le boulot du MTA fait. Autant faire ce 
travail en amont. Sous sendmail, le boulot est fait par une milter 
(clamav-milter) bien avant que sendmail balance le mail au MDA (qui peut 
être procmail si sendmail est configuré avec des maildirs).


JKB

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5390960d.8020...@systella.fr

Re: procmail et clamav

[Bernard Schoenacker]

Le Thu, 05 Jun 2014 18:08:45 +0200,
BERTRAND Joël joel.bertr...@systella.fr a écrit :

 Bernard Schoenacker a écrit :
  Le Thu, 5 Jun 2014 17:27:25 +0200,
  Bernard Schoenacker bernard.schoenac...@free.fr a écrit :
 
  bonjour,
 
  je n'ai pas trouvé de règle pour clamav et procmail
 
 
  slt
  bernard
 
 
  bonjour,
 
 
  j'ai trouvé chez ubuntu (manpage) la recette qui convient :
 
  http://manpages.ubuntu.com/manpages/dapper/man1/clamassassin.1.html
 
  PROCMAIL
 
  To pass your mail through clamassassin, add the  following
  command  to your procmailrc file (/etc/procmailrc or
  ~/.procmailrc):
 
   :0fw
   |/usr/bin/clamassassin
 
  The  above  will  forward  the  mail  to  clamassassin,
  which will use /usr/bin/clamscan to scan the mail, and add the
  headers  X-Virus-Status and  X-Virus-Report  as
  appropriate. To filter infected mails, you have to set an additional
  filter-rule:
 
   :0:
   * ^X-Virus-Status: Yes
   IN.virus
 
  In this example, all infected mails are sorted to the
  IN.virus  mail folder.  If  you want to destroy such
  messages altogether, you can also change IN.virus to /dev/null.
 
  Forfurtherinformation,please have a
  look at /usr/share/doc/clamassassin/.
 
 
  slt
  bernard
 
 
   Bonsoir,
 
   Je ne comprends pas trop pourquoi tu cherches à utiliser
 procmail pour cela (mais sans nous indiquer ton MTA, difficile d'en
 dire plus).
 
   Procmail est appelé une fois le boulot du MTA fait. Autant
 faire ce travail en amont. Sous sendmail, le boulot est fait par une
 milter (clamav-milter) bien avant que sendmail balance le mail au MDA
 (qui peut être procmail si sendmail est configuré avec des maildirs).
 
   JKB
 

bonjour,

cher professeur knatschké, je ne compte pas utiliser sendmail
et par conséquent je traite avec procmail le flux entrant et :

mon MUA est claws-mail ( MH ) avec nmh 
mon MTA est exim

je compte employer dès que possible MH-E avec emacs

mfg
bernard

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/20140605183238.3db2c9fc@hamtaro

Re: procmail et clamav

[Francois Mescam]

On 05/06/2014 17:27, Bernard Schoenacker wrote:
 bonjour,

 je n'ai pas trouvé de règle pour clamav et procmail
# anti-virus
:0HB:
* ! ? (formail | clamdscan --quiet -)
* ? echo emetteur reel $FROM  $LOGFILE
| formail -AX-Procmail: virus trouvé infected



-- 
 Francois Mescam Tel:+33 6 16 05 77 61

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/53909d5e.6020...@mescam.org

Re: procmail et clamav

[Bernard Schoenacker]

Le Thu, 05 Jun 2014 18:39:58 +0200,
Francois Mescam franc...@mescam.org a écrit :

 On 05/06/2014 17:27, Bernard Schoenacker wrote:
  bonjour,
 
  je n'ai pas trouvé de règle pour clamav et procmail
 # anti-virus
 :0HB:
 * ! ? (formail | clamdscan --quiet -)
 * ? echo emetteur reel $FROM  $LOGFILE
 | formail -AX-Procmail: virus trouvé infected
 
 
 

bonjour,

le format mbox est employé chez moi pour : /var/mail/$LOGNAME
le format MH est employé chez moi pour $HOME/Mail

 # Place mail sent to any MH-E mailing list in +mh-e.
  :0 w: mh-e$LOCKEXT
  * ^TO.*mh-e-.*@.*sourceforge.net
  | rcvstore -create +mh-e

source :
https://www.gnu.org/software/emacs/manual/html_node/mh-e/Procmail.html

 comment modifier la règle pour que se soit du MH ?

slt
bernard

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/20140605190249.2a8bebc4@hamtaro

Re: Procmail no funciona

[Federico Alberto Sayd]

On 15/05/13 12:21, co...@esid.gecgr.co.cu wrote:

Hola

Alguien que haya podido hacer funcionar el procmail que pudiera dar una
mano, no hay forma que me trabaje con postfix, no sé que estoy haciendo
mal.



/etc/procmailrc ?Como debe ir el fichero de configuración?

Ejemplo como hacer para que los correos entrantes no se dupliquen ni
tripliquen, etc.

Para que trabaje en cojunto con Postfix activé esto

mailbox_command = procmail -a $EXTENSION

pero nada


Mi postfix usa Maildir

los usuarios de correo estan en /home/usuario/Maildir/



Salu2




Y que dicen los logs de postfix cuando tratas de hacer la entrega?

Aquí tienes una receta de una configuración de Procmail funcionando con 
Maildir, con logueo activado.


# file: /etc/procmailrc
# system-wide settings for procmail
SHELL=/bin/bash
SENDMAIL=/usr/sbin/sendmail -oi -t
LOGFILE=/var/log/procmail.log
DEFAULT=$HOME/Maildir/
MAILDIR=$HOME/Maildir/

Saludos


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5194e5e2.9060...@uncu.edu.ar

Re: Procmail no funciona

[joel]

  
  
El 15/5/2013 10:21 a.m., co...@esid.gecgr.co.cu escribi:

  
Hola

Alguien que haya podido hacer funcionar el procmail que pudiera dar una
mano, no hay forma que me trabaje con postfix, no s que estoy haciendo
mal.



/etc/procmailrc ?Como debe ir el fichero de configuracin?

Ejemplo como hacer para que los correos entrantes no se dupliquen ni
tripliquen, etc.

Para que trabaje en cojunto con Postfix activ esto

mailbox_command = procmail -a "$EXTENSION"

pero nada


Mi postfix usa Maildir

los usuarios de correo estan en /home/usuario/Maildir/



Salu2





Mira colega, yo lo tengo trabajando con dovecot
  con filtro sieve, que a mi pararece que debe ser casi lo mismo,
en principio aunque no uses procmail, los correos no se te deben
repetir, quisas los que mas saben de esto te dicen otra cosa pero a
mi me parece asi, por lo pronto debes dar mas datos, por ejemplo tu
configuracin en main.cf

-- 
Saludos

--
  0ooo
  ooo0(   )
  (   )) /
   \ ((_/
\_)
`,,`,,`,,`,,
  Joel  Ventura Castillo
Tc. Ciencias Informticas
  Empresa Importadora - Exportadora ILECO
 Dir.: O' Relly No. 152 e/ San Ignacio y Mercaderes,
   Habana Vieja, Cuba.
   E-Mail: j...@ecoimpex.com.cu
   Telf.: 8625081 al 84, Ext. 156   
`,,`,,`,,`,,
  



-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5193ff73.7090...@ecoimpex.com.cu

Re: Procmail does not work

[David Guntner]

co...@esid.gecgr.co.cu grabbed a keyboard and wrote:
 Hi
 
 Someone who has been running the procmail that could give a
 hand, there is no way that I work with postfix, I know I'm doing
 wrong.
 
 /etc/procmailrc? Because you must go to the configuration file?

Here is what is in my /etc/procmailrc file, to allow for Maildir format
delivery:

$ cat /etc/procmailrc
# File:  /etc/procmailrc
# System-wide configuration settings for Procmail

SHELL=/bin/bash
SENDMAIL=/usr/sbin/sendmail -oi -t
#LOGFILE=/var/log/procmail.log
MAILDIR=$HOME/Mail/
DEFAULT=$HOME/Mail/
ORGMAIL=$HOME/Mail/
LINEBUF=16384

(For you, you'd want to change the /Mail/ part to say /Maildir/, since
that's where you want it to end up.

 Example how to make incoming messages are not duplicated or
 triple, etc..
 
 To work on cosets with Postfix I activated this
 
 mailbox_command = procmail-a $ EXTENSION

For starters, you need a space between the procmail and the -a.  And
no space between the $ and EXTENSION.  Fix those, and make sure your
/etc/procmailrc is along the lines of what I showed above, and you
should be fine.

 but nothing
 
 
 My postfix uses Maildir
 
 mail users are in /home/{user}/Maildir/

(I changed the above to make it more readable for what it probably
actually is...)

 --Dave




signature.asc
Description: OpenPGP digital signature

[Fwd: Re: Procmail does not work]

[cosme]

Hi David

I did exactly as you said but still not working

with the line mailbox_command = procmai -a $EXTENSION in Postfix and the
configuration file in /etc/promailrc  check this out


$ cat /etc/procmailrc

SHELL=/bin/bash
SENDMAIL=/usr/sbin/sendmail -oi -t
LOGFILE=/var/log/procmail.log
MAILDIR=$HOME/{user}/Maildir/
DEFAULT=$HOME/{user}/Maildir/
ORGMAIL=$HOME/{user}/Maildir/
LINE=16384
#DROPPRIVS=yes
VERBOSE=yes

:0c
! co...@esid.gecgr.co.cu

:0 Wh: msgid.lock
| formail -D 2048 msgid.cache


You need to configure something more?

remain at 0 /var/log/procmail.log













-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/43995e4d7cab74a60a807a70e092d88d.squirrel@192.168.13.16

Re: procmail en Debian

[Cristian Mitchell]

http://www.sromero.org/ext/articulos/sololnx/sololnx5.html

y mas

https://www.google.com.ar/search?q=procmailrc+ejemplosaq=2oq=procmailaqs=chrome.3.57j0l3.12638j0sourceid=chromeie=UTF-8


El 10 de mayo de 2013 16:51, co...@esid.gecgr.co.cu escribió:

 Hola

 Alguien me pudiera poner un ejemplo de como configurar procmail en Debian
 squeeze
 quiero poner reglas para todos los usuarios por lo que debo ponerlo en

 /etc/procmailrc

 Ejemplo como hacer para que los correos entrantes no se dupliquen ni
 tripliquen, etc.

 me inmagino que en el postfix debo activar la linea
 mailbox_command = procmail -a $EXTENSION

 Para que trabaje en cojunto con Postfix



 Cualquier otro ejemplo me serviria lo que quiero es entender como se
 configuran las reglas que uno necesita plicar

 Salu2



 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/a8e2559e3695b9c7aebb646a1ce1f6fb.squirrel@192.168.13.16




-- 
MrIX
Linux user number 412793.
http://counter.li.org/

las grandes obras,
las sueñan los santos locos,
las realizan los luchadores natos,
las aprovechan los felices cuerdo,
y las critican los inútiles crónicos,

Re: procmail filtering

[Chris Bannister]

On Thu, Jul 05, 2012 at 11:14:57AM +0200, Jochen Spieker wrote:
 lee:
  
  I've looked at formail + procmail , but formail forces it into mailbox
  format which I dont want.
 
 Formail doesn't actually save the mailboxes anywhere, procmail does
 that. And if you append a slash to the mailbox name, procmail generates
 maildirs. Example:
 
 MAILDIR=$HOME/Maildir/
 LOGFILE=$HOME/.procmail.log
 DEFAULT=$MAILDIR
 
 :0:
^
In that case you don't need the colon. That colon is for locking and
maildir doesn't require locking. 
e.g.

:0
* ^X-Mailing-List: debian...@lists.debian.org
* ^X-Mailing-List: debian-\/[-a-zA-Z0-9]+
.lists.debian.$MATCH/



-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120711033037.GU3873@tal

Re: procmail filtering

[lee]

On 07/05/2012 02:41 PM, Jon Dowland wrote:
 You can run procmail in filter mode and pipe it each mail that you wish to
 filter individually, but you must keep track of which mails have been piped to
 procmail and remove them/mark them 'processed' yourself, via shell scripts 
 etc.

 Make sure your procmail recipe(s) deliver to a sensible location.


Hi

thanks for the response.

L


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ff69f76.3080...@tlabs.ac.za

Re: procmail filtering

[lee]

On 07/05/2012 09:59 PM, Bob Proulx wrote:
 lee wrote:
 I've looked at formail + procmail , but formail forces it into mailbox
 format which I dont want.
 With Maildir format you don't need formail.  Just pipe each individual
 message to procmail.

 Of the top of my head and untested:

   for m in Maildir/new/* Maildir/cur/*; do
 procmail myprocmailrcfile  $m
   done

 Best to test it with one message first to make sure it all works
 before trying to run on a large mailbox.

 Bob
Hi

I did something similar but ended up creating alot of 'copies' which I
didn't want. but thanks. now I at least know
I was on the right track.

Regards
Lee


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ff69fba.5090...@tlabs.ac.za

Re: procmail filtering

[Jochen Spieker]

lee:
 
 I've looked at formail + procmail , but formail forces it into mailbox
 format which I dont want.

Formail doesn't actually save the mailboxes anywhere, procmail does
that. And if you append a slash to the mailbox name, procmail generates
maildirs. Example:

MAILDIR=$HOME/Maildir/
LOGFILE=$HOME/.procmail.log
DEFAULT=$MAILDIR

:0:
* ^X-Mailing-List: debian...@lists.debian.org
* ^X-Mailing-List: debian-\/[-a-zA-Z0-9]+
.lists.debian.$MATCH/

J.
-- 
My medicine shelf is my altar.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature

Re: procmail filtering

[Jon Dowland]

You can run procmail in filter mode and pipe it each mail that you wish to
filter individually, but you must keep track of which mails have been piped to
procmail and remove them/mark them 'processed' yourself, via shell scripts etc.

Make sure your procmail recipe(s) deliver to a sensible location.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120705124158.GC32553@debian

Re: procmail filtering

[Bob Proulx]

lee wrote:
 I've looked at formail + procmail , but formail forces it into mailbox
 format which I dont want.

With Maildir format you don't need formail.  Just pipe each individual
message to procmail.

Of the top of my head and untested:

  for m in Maildir/new/* Maildir/cur/*; do
procmail myprocmailrcfile  $m
  done

Best to test it with one message first to make sure it all works
before trying to run on a large mailbox.

Bob


signature.asc
Description: Digital signature

Re: procmail, problem with this delivering recipe

[T o n g]

On Tue, 03 Jan 2012 23:18:59 -0700, Bob Proulx wrote:

 there were actually more piping commands between formail  $SENDMAIL in
 my rcfile.
 
 Yes.  But as noted that is incorrect.  Only one action line is allowed
 there.

Hmm..., actually, it is correct. True, that there can only be exactly one 
action line, but that doesn't prevent me from concatenating consequent 
lines together with a trailing '\', just like what I'm doing in make as 
well. 

All those complicated piping will form a *single* action line. I've 
checked the log, procmail is OK with that, no error or complains, and I 
get exactly what I want from the $SENDMAIL command. Ie, everything is 
working fine, just that procmail considers it a non-delivering recipe, 
which seems strange to me. 

Further probing shows that, procmail considered the mail *header* is 
delivered and went on trying to deliver the mail *body* -- all such 
delivered messages are from 'foo@bar' and without any header. 

Just as a comparison, if not delivering to pipe but to a file, to be 
considered as a delivering recipe:

When you drop something to /dev/null, use the h flag so that procmail
does not unnecessarily try to feed whole message there

  :0 h
  * condition
  /dev/null

http://pm-doc.sourceforge.net/doc/#flag_h_and_sinking_to_devnull

I'm confused.
Please help.

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/je1oor$n0a$1...@dough.gmane.org

Re: procmail, problem with this delivering recipe

[T o n g]

On Wed, 04 Jan 2012 03:40:24 +, T o n g wrote:

   # send header only 

[ . . . ]

 I.e., having processed it, procmail went on with the following recipes
 instead of considering the mail delivered and cease processing the
 rcfile.

Hmm... looks like procmail considered the mail *header* delivered and 
went on trying to deliver the mail *body* -- all delivered messages are 
from foo@bar and without any header. Is it normal?

FYI, I learnt that, 

When you drop something to /dev/null, use the h flag so that procmail 
does not unnecessarily try to feed whole message there

  :0 h
  * condition
  /dev/null

http://pm-doc.sourceforge.net/doc/#flag_h_and_sinking_to_devnull

I'm confused. 
Please help.

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/je0ic2$h2e$1...@dough.gmane.org

Re: procmail, problem with this delivering recipe

[Bob Proulx]

T o n g wrote:
   :0 Hfhwi
   * ^Subject: \/.*
   | formail -b -c -X From: -X To: -X Subject: -X Date: . . . 
   | $SENDMAIL $SENDMAILFLAGS . . . 

You need to create another recipe for the second pipe.

  :0 Hfhwi
  * ^Subject: \/.*
  | formail -b -c -X From: -X To: -X Subject: -X Date: . . . 

  :0 A
  | $SENDMAIL $SENDMAILFLAGS . . . 

Bob


signature.asc
Description: Digital signature

Re: procmail, problem with this delivering recipe

[Bob Proulx]

T o n g wrote:
 Bob Proulx wrote:
:0 Hfhwi
* ^Subject: \/.*
| formail -b -c -X From: -X To: -X Subject: -X Date: . . . |
$SENDMAIL $SENDMAILFLAGS . . .
  
  You need to create another recipe for the second pipe.
  
:0 Hfhwi
* ^Subject: \/.*
| formail -b -c -X From: -X To: -X Subject: -X Date: . . .
  
:0 A
| $SENDMAIL $SENDMAILFLAGS . . .
 
 Thanks. It works.
 
 Hmm, may I know why the change is necessary?

The man page for procmailrc has the following information:

   A line starting with ':' marks the beginning of a recipe.  It  has  the
   following format:

  :0 [flags] [ : [locallockfile] ]
  zero or more conditions (one per line)
  exactly one action line

The documented format is exactly one action line and therefore you
can only have exactly one action line.  :-)

 there were actually more piping commands between formail  $SENDMAIL
 in my rcfile.

Yes.  But as noted that is incorrect.  Only one action line is allowed
there.  If I need to do something more complicated then normally I
create a script and put all of the complication there and simply call it.

 Now procmail considers the mail delivered, however I wanted to send
 header only, but now I receive some part of mail body as well. Thus
 I need to know why.

If you want the header only then you need to include the 'h' flag.

   bFeed the body to the pipe, file or mail destination (default).

   hFeed the header to the pipe, file or mail destination (default).

   wWait for the filter or program to finish and  check  its  exitcode
(normally  ignored);  if the filter is unsuccessful, then the text
will not have been filtered.

Therefore something like this for the second part of the recipe.  The
default will be the flags hb and you only want the 'h' flag.  Along
with 'w' of course to wait for the exit code of sendmail.

  :0 Ahw
  | $SENDMAIL $SENDMAILFLAGS . . .

Bob


signature.asc
Description: Digital signature

Re: Procmail regular expression: word end boundary matching

[Bob Proulx]

T o n g wrote:
 Bob Proulx wrote:
  I think it is a bug in the \ expansion.
 
 OMG, I thought it would be very hard for anyone to find out the answer. 
 
 THANKS A LOT. works like a charm.

That seems to be an okay workaround but it still looks like a bug.
Since I use procmail a lot it motivated me to look at least that far
into the problem.  Hopefully at some point the bug will be fixed and
then the two backslashes would need to be collapsed back to one again.

I reported the problem it here:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653624

Bob


signature.asc
Description: Digital signature

Re: Procmail regular expression: word end boundary matching

[Bob Proulx]

T o n g wrote:
 I seems not able to get the word end boundary matching for procmail 
 works. Here is my test rc file:
 
 :0 HB
 * 1^0 \test\
 * 1^0 test
 /dev/null
 
 and there is a ' test ' in my test email. 
 
 However, from the dry run log, I can see that '\test\' did not match 
 yet 'test' did. 

I think it is a bug in the \ expansion.  Try this with one extra
backslash in front of the left  only.  Not the right  one.  Only the
left one.

:0 HB
* 1^0 \\test\
* 1^0 test
/dev/null

 2. About word end boundary matching, I found the following from the web:

That documentation is in the procmailrc man page.

 \
 A shorthand for the character class [^a-zA-Z0-9_] except it can also 
 match newlines. 
 This is an incompatible imitation of the word end boundary operator 
 found in some extended regular expression implementations. Note that \ 
 and \ are actually identical. 

I think that is outdated because from testing the above the
documentation in the man page doesn't seem to match the behavior.  I
think the ERE engine may have been swapped out for a different one
after the documentation was written.

Bob


signature.asc
Description: Digital signature

Re: Procmail question/puzzle

[Michelle Konzack]

Hello Paul E Condon,

Am 2011-04-24 14:13:26, hacktest Du folgendes herunter:
 ## 'unreadable' mail
 :0:
 * 1^0 
 ^\/Subject:.*=\?(.*big5|iso-2022-jp|ISO-2022-KR|euc-kr|gb2312|ks_c_5601-1987|windows-1251|windows-1256)\?
 * 1^0 
 ^\/Content-Type:.*charset=(.*big5|iso-2022-jp|ISO-2022-KR|euc-kr|gb2312|ks_c_5601-1987|windows-1251|windows-1256)
 unreadable_

To let this work, you have to give  them  a  NEGATIVE  score  first  and
escape the - like

:0:
* -1^0
*  1^1 
^Subject:.*=\?(.*big5|iso\-2022-jp|ISO\-2022-KR|euc\-kr|gb2312|ks_c_5601\-1987|windows\-1251|windows\-1256)\?
*  1^1 
^Content-Type:.*charset=(.*big5|iso-2022\-jp|ISO\-2022-KR|euc\-kr|gb2312|ks_c_5601\-1987|windows\-1251|windows\-1256)
unreadable_

 ## bogofilter spam filtering:
 :0fw
 | /usr/bin/bogofilter -eplu

But bogofilter mark the message slike spamassassin...  You have now to
filter out thie crap.  Since I do not know bogofilter and the header  it
sets, I can not help you here.  Maybe you can send the full headers of a
scanned SPAM message here?

Thanks, Greetings and nice Day/Evening
Michelle Konzack

-- 
# Debian GNU/Linux Consultant ##
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsystems@tdnet France EURL   itsystems@tdnet UG (limited liability)
Owner Michelle KonzackOwner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France   77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

http://www.itsystems.tamay-dogan.net/  http://www.flexray4linux.org/
http://www.debian.tamay-dogan.net/ http://www.can4linux.org/

Jabber linux4miche...@jabber.ccc.de
ICQ#328449886

Linux-User #280138 with the Linux Counter, http://counter.li.org/


signature.pgp
Description: Digital signature

Re: Procmail

[Jean-Yves F. Barbier]

On Sun, 26 Dec 2010 13:31:58 +0100, Frédéric ZULIAN zul...@free.fr wrote:

 Fetchmail vas  chercher le courrier et le met bien 
 dans /var/mail/fred.
 
 Procmail ne vas pas chercher le courrier dans /var/mail/fred
 Pourtant j'ai recopier mes fichiers de configs dans mon précédent home.

est-ce que le transport du MTA (Exim, je suppose, vu la conf) est correctement
configuré pour appeler procmail lors de la distribution du courier?

 Peut-être un pb de droits ?
 
 Droits /home/fred/.fetchmailrc   0660   user/groupe fred:fred

from man fetchmailrc:
a named file argument must have permissions no more open than 0700 
(u=rwx,g=,o=) or else be /dev/null.

 Droits /home/fred/Mail 0700  user/groupe fred:fred

correct.

 Droits /var/mail/fred  0776  user/groupe  fred:mail  

c'est quoi ces droits débiles? (Read  Write pour n'importe qui sur tes
propres emails!!...)
les droits corrects sont:
/var/mail  = root:mail  42775
/var/mail/user = user:mail 100660
 
 procmail v3.22 2001/09/10
 Locking strategies: dotlocking, fcntl()
 Default rcfile: $HOME/.procmailrc
 It may be writable by your primary group
 Your system mailbox:/var/mail/fred
  ^^
voilà une partie de ta réponse: ta BAL devrait, semble-t'il, se trouver dans
$HOME/Mail/ (sèpu: ça fait trop longtemps que je n'utilise plus Exim, donc la
parole est à ses habitués.)

-- 
Landru! Guide us!
-- A Beta 3-oid, The Return of the Archons, stardate 3157.4

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/20101226140510.7e54f...@anubis.defcon1

Re: Procmail et ClamAV

[Christophe Gallaire]

Je n'avais pas vu ta réponse. 


Merci, je vais l'essayer.

@+

Christophe
Francois Mescam a dit dans un souffle :
Si cela peu servir voici la recette que j'utilise depuis plusieurs 
années donc j'aurai besoin de relire la doc si je veux comprendre le 
pourquoi du comment :


# anti-virus
:0HB:
* ! ? (formail | clamdscan --quiet -)
* ? echo emetteur reel $FROM  $LOGFILE
| formail -AX-Procmail: virus trouvé infected


On 14/11/2010 11:26, Christophe Gallaire wrote:

Bonjour,

J'essaie d'écrire une recette pour Procmail permettant d'analyser les
mails entrants. J'ai trouvé quelques pistes, notamment celle-là, mais je
ne suis pas vraiment certain de son efficacité :

# Rules for running ClamAV

CLAMSCAN=/usr/bin/clamdscan
VIRUSTARGET=/dev/null

:0
*  1
* multipart
{
# Okay, large multipart message run through clamscan
VIRUS=`$CLAMSCAN --mbox --disable-summary --stdout -`

:0 Di
* VIRUS ?? FOUND
$VIRUSTARGET
}

Je ne vois pas bien, par exemple, comment les fichiers infectés sont
redirigés
dans $VIRUSTRAGET. Pourquoi rediriger l'affichage sur la sortie standard
--stdout ? N'est-ce pas une valeur par défaut ? Est-il bien nécessaire
de renseigner l'option --mbox ? Pourquoi ce tiret isolé en fin de
commande ?

@+

Christophe



--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/ibpg60$m8...@dough.gmane.org


--
Christophe Gallaire

Attention ! Suppression des mails entrants dont la taille est supérieure à 2Mo !
N'envoyez, s'il vous plaît, que des pièces jointes en formats ouverts. 
---

Nouveau carnet de route : http://www.road2mayotte.org/blook
---
Linux On The Root : http://ubunteros.tuxfamily.org/
---
Clé de chiffrement : 34AA23BB


signature.asc
Description: Digital signature

Re: Procmail et ClamAV

[Francois Mescam]

Si cela peu servir voici la recette que j'utilise depuis plusieurs 
années donc j'aurai besoin de relire la doc si je veux comprendre le 
pourquoi du comment :


# anti-virus
:0HB:
* ! ? (formail | clamdscan --quiet -)
* ? echo emetteur reel $FROM  $LOGFILE
| formail -AX-Procmail: virus trouvé infected


On 14/11/2010 11:26, Christophe Gallaire wrote:

Bonjour,

J'essaie d'écrire une recette pour Procmail permettant d'analyser les
mails entrants. J'ai trouvé quelques pistes, notamment celle-là, mais je
ne suis pas vraiment certain de son efficacité :

# Rules for running ClamAV

CLAMSCAN=/usr/bin/clamdscan
VIRUSTARGET=/dev/null

:0
*  1
* multipart
{
# Okay, large multipart message run through clamscan
VIRUS=`$CLAMSCAN --mbox --disable-summary --stdout -`

:0 Di
* VIRUS ?? FOUND
$VIRUSTARGET
}

Je ne vois pas bien, par exemple, comment les fichiers infectés sont
redirigés
dans $VIRUSTRAGET. Pourquoi rediriger l'affichage sur la sortie standard
--stdout ? N'est-ce pas une valeur par défaut ? Est-il bien nécessaire
de renseigner l'option --mbox ? Pourquoi ce tiret isolé en fin de
commande ?

@+

Christophe



--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/ibpg60$m8...@dough.gmane.org

Re: procmail and Unicode header lines (RFC 2047)

[Stanisław Findeisen]

On 2010-10-29 10:39, Camaleón wrote:
 On Thu, 28 Oct 2010 21:19:30 +0200, Stanisław Findeisen wrote:
 
 Is there any support in Debian for Unicode e-mail header lines
 processing, e.g. with procmail?

 Those header lines look like this:

 Subject: =?ISO-2022-JP?B?GyRCNEE7eiROJTUlViU4JSclLyVIGyhC?=

 so they need to be decoded before doing anything useful with them. (See:
 http://www.debian.org/doc/manuals/intro-i18n/ch-internet.en.html)
 
 Mmm, procmail is a delivery agent, it does not render the messages. 
 
 What e-mail client are you using for displaying e-mails? I have not 
 problems with encoded subjects using rfc 2047, they seem to render just 
 fine in Mutt.

I was talking about e-mail processing (e-mail filtering, header fields
modifications etc.) on the server. So no, no end-user client e-mail
software involved.

-- 
http://people.eisenbits.com/~stf/
OpenPGP: DFD9 0146 3794 9CF6 17EA  D63F DBF5 8AA8 3B31 FE8A

Like hardship, risk  challenge?  --- Follow Jesus!!



signature.asc
Description: OpenPGP digital signature

Re: procmail and Unicode header lines (RFC 2047)

[Camaleón]

On Sun, 31 Oct 2010 07:46:45 +0100, Stanisław Findeisen wrote:

 On 2010-10-29 10:39, Camaleón wrote:

 Mmm, procmail is a delivery agent, it does not render the messages.
 
 What e-mail client are you using for displaying e-mails? I have not
 problems with encoded subjects using rfc 2047, they seem to render just
 fine in Mutt.
 
 I was talking about e-mail processing (e-mail filtering, header fields
 modifications etc.) on the server. So no, no end-user client e-mail
 software involved.

Yes, sorry, I was not aware of the filtering issue ;-(

I thought Procmail was using the same path as Postfix, SpamAssassin or 
Avamisd-new (AFAIK, they do not decode the subject so you have to put the 
exact string line to get filters working).

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.10.31.11.12...@gmail.com

Re: procmail and Unicode header lines (RFC 2047)

[Stanisław Findeisen]

On 2010-10-29 21:35, Bob Proulx wrote:
 Stanisław Findeisen wrote:
 Is there any support in Debian for Unicode e-mail header lines
 processing, e.g. with procmail?
 Subject: =?ISO-2022-JP?B?GyRCNEE7eiROJTUlViU4JSclLyVIGyhC?=

 so they need to be decoded before doing anything useful with them. (See:
 http://www.debian.org/doc/manuals/intro-i18n/ch-internet.en.html)
 
 As far as I know there is no support in procmail for decoding those
 fields.  I have always needed to create rules working with the encoded
 data.
 
 Example from some localized mailman filtering:
   * 1^0 ^Subject: [^ ]+ post from
   * 1^0 ^Subject: .*El_envio_a_
   * 1^0 ^Subject: .*Un_envoi_sur_la_liste_
   * 1^0 ^Subject: .*_taraf=FDndan_g=F6nderilen_
 
 Using wildcards for the interesting characters has worked fairly well
 with the European languages.  But I have no experience and no
 suggestion for your example JP locale though.

Hm I wrote this little script:

http://people.eisenbits.com/~stf/software/conv2047/

It is easy to use it in .procmailrc along with formail (you decode
encoded subject (or any other field) and *then* you search for your
patterns of interest). Then you can, for instance, modify the subject
and encode it back.

It works for me, at least.

-- 
http://people.eisenbits.com/~stf/
OpenPGP: DFD9 0146 3794 9CF6 17EA  D63F DBF5 8AA8 3B31 FE8A

Like hardship, risk  challenge?  --- Follow Jesus!!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ccbf11d.7050...@eisenbits.com

Re: procmail and Unicode header lines (RFC 2047)

[Bob Proulx]

Stanisław Findeisen wrote:
  Is there any support in Debian for Unicode e-mail header lines
  processing, e.g. with procmail?
  Subject: =?ISO-2022-JP?B?GyRCNEE7eiROJTUlViU4JSclLyVIGyhC?=
 ...
 Hm I wrote this little script:
 
 http://people.eisenbits.com/~stf/software/conv2047/
 
 It is easy to use it in .procmailrc along with formail (you decode
 encoded subject (or any other field) and *then* you search for your
 patterns of interest). Then you can, for instance, modify the subject
 and encode it back.
 
 It works for me, at least.

Neat!  I will have to check it out.

Thanks,
Bob


signature.asc
Description: Digital signature

Re: procmail and Unicode header lines (RFC 2047)

[Camaleón]

On Thu, 28 Oct 2010 21:19:30 +0200, Stanisław Findeisen wrote:

 Is there any support in Debian for Unicode e-mail header lines
 processing, e.g. with procmail?
 
 Those header lines look like this:
 
 Subject: =?ISO-2022-JP?B?GyRCNEE7eiROJTUlViU4JSclLyVIGyhC?=
 
 so they need to be decoded before doing anything useful with them. (See:
 http://www.debian.org/doc/manuals/intro-i18n/ch-internet.en.html)

Mmm, procmail is a delivery agent, it does not render the messages. 

What e-mail client are you using for displaying e-mails? I have not 
problems with encoded subjects using rfc 2047, they seem to render just 
fine in Mutt.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.10.29.08.39...@gmail.com

Re: procmail and Unicode header lines (RFC 2047)

[Bob Proulx]

Stanisław Findeisen wrote:
 Is there any support in Debian for Unicode e-mail header lines
 processing, e.g. with procmail?
 Subject: =?ISO-2022-JP?B?GyRCNEE7eiROJTUlViU4JSclLyVIGyhC?=
 
 so they need to be decoded before doing anything useful with them. (See:
 http://www.debian.org/doc/manuals/intro-i18n/ch-internet.en.html)

As far as I know there is no support in procmail for decoding those
fields.  I have always needed to create rules working with the encoded
data.

Example from some localized mailman filtering:
  * 1^0 ^Subject: [^ ]+ post from
  * 1^0 ^Subject: .*El_envio_a_
  * 1^0 ^Subject: .*Un_envoi_sur_la_liste_
  * 1^0 ^Subject: .*_taraf=FDndan_g=F6nderilen_

Using wildcards for the interesting characters has worked fairly well
with the European languages.  But I have no experience and no
suggestion for your example JP locale though.

You might try the procmail users mailing list for perhaps better
suggestions.

Bob


signature.asc
Description: Digital signature

Re: Procmail: re-sort all messages

[Chris Bannister]

On Fri, May 07, 2010 at 03:38:51PM +0300, Alexander Batischev wrote:
 Hi,
 
 I've just installed fetchmail → procmail → mutt → msmtp chain and want
 to configure procmail properly. Of course, I can't write all the rules
 in the right way from scratch, so there must be some testing. The only
 way to check how rules works is actually run procmail and see what
 happens. Here is where problems starts.

http://www.ii.com/internet/robots/procmail/qs/

-- 
Religion is excellent stuff for keeping common people quiet.
   -- Napoleon Bonaparte


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100508150554.gc20...@fischer

Re: Procmail: re-sort all messages

[Alexander Batischev]

On Fri, May 07, 2010 at 02:30:06PM +0100, Jon Dowland wrote:
 You can invoke procmail by piping an email to it.
 
 find $LOCAL_MAIL_DIR -type f | while read mail; do procmail  $mail; done
That's it! Thank you very much!

Thank you Monique Y. Mudama and Chris Bannister for nice hints, too — now I
have archiving enabled and have something to read :)


Regards,
Alexander Batischev


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100508152055.ga14...@eternity.smila.com

Re: Procmail: re-sort all messages

[Jon Dowland]

On 07/05/10 13:38, Alexander Batischev wrote:
 So here is what I'm looking for: is there a way to run procmail on
 already downloaded messages? Maybe I should download them to separate
 directory and run procmail on it? Maybe I can just pass existing
 (already sorted) mail directory to procmail for re-sorting? I hope
 there are some way to do that.

You can invoke procmail by piping an email to it.

find $LOCAL_MAIL_DIR -type f | while read mail; do procmail  $mail; done



signature.asc
Description: OpenPGP digital signature

Re: Procmail: re-sort all messages

[Monique Y. Mudama]

On Fri, May  7 at 15:38, Alexander Batischev penned:
 Hi,
 
 I've just installed fetchmail ??? procmail ??? mutt ??? msmtp chain
 and want to configure procmail properly. Of course, I can't write
 all the rules in the right way from scratch, so there must be some
 testing. The only way to check how rules works is actually run
 procmail and see what happens. Here is where problems starts.
 

This doesn't answer your direct question, but my first procmail rule
copies the message to an archive mailbox.  That way if I screw up the
later rules, I can still see the original message.

My rule for this is:

:0 c:
$HOME/mail/archive/backup

(backup is in mbox format)

I also have this at the top to see what procmail's doing:

LOGFILE=$HOME/log/procmail.log
#add a line between each entry for readability
LOG=

#applies to log
VERBOSE=yes

I use logrotate to trim both the backup mailbox and the procmail log
file.


-- 
monique


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100507155651.gd1...@mail.bounceswoosh.org

Re: Procmail et renvoie de mail

[Jean-Yves F. Barbier]

Le Wed, 24 Mar 2010 09:13:27 +0100,
zut...@laposte.net a écrit :

 Bonjour,
 
 J'ai deux ou trois adresse chez la poste.
 
 Ces adresses sont regroupé sur un seul compte.
 Je récupère tous cela via fetchmail. Puis, procmail trie mon courrier.
 
 J'envoie grâce à ce dernier aux différents user. Toutefois, l'adresse from
 semble modifié. Je ne peut donc plus re-trier par procmail de façon
 efficace.

Ca n'est pas clair: est-ce que procmail dépose les emails récupérés dans
des BALs locales, ou bien renvoit-il ces emails sur d'autres adresses
email non-locales?


-- 
Lonely is a man without love.
-- Englebert Humperdinck

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/20100324220649.671f9...@anubis.defcon1

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Paul Cartwright]

On Tue August 25 2009, Chris Jones wrote:
  but looking at the procmailrc( now non-existant), then thinking about
  my 200 kmail filters, I'm not sure I could tackle that task..

 As another poster hinted, this is another example of the hidden benefits
 of cloning the Microsoft model.

I'm not sure I understand.. what I DID find out was, my procmailrc file 
WORKED.. the problem is, I didn't do it right. I sent all my personal email ( 
for the last 4 days) to a mbox file in my home directory. I THOUGHT I had 
kmail setup to get that mail, but it didn't. SO, I had to forward it back to 
my /var/mail/user and resend it..
how do I get kmail to accept email from that mbox file, or did I do it wrong?

-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Paul Cartwright]

On Tue August 25 2009, Micha wrote:
  what benefit would I get from procmail?

 1. The ability to move from kmail to something else if you want without
 rewriting your rules.

good idea.. I like that, especially when testing different email programs.

 2. The ability to pull mail without having kmail running (via a cron job or
 fetchmail daemon)
I do that now with fetchmail, it brings it all in to my /var/mail/user

 3. Text file with regular expression based rules that you know where it
 resides and can back it up and human read it

this I DO like ! the ability to use filters across email programs.

 If you don't care about these three than nothing (some consider the third a
 downside, not an improvement but that's personal preference not an
 absolute)

 On the downside, if you want to explicitly pull mail now, pulling mail from
 kmail doesn't pull the mail off your accounts, you need to do that
 explicitly from the command line

 It's all down to personal preferences.

 I played around a lot at the time looking for a mail client I'd be happy
 with (Still haven't found one) and worked quite a bit with mutt (I'm not
 sure if it even supports pulling mail itself) so fetchmail + procmail was
 the best option for me.

right now, on my system I have icedove, evolution, kmail, and claws, all setup 
for my local user. procmail seems to move the mail into an mbox file, and I 
haven't figured out how to get any email program to read an mbox folder.

 If this is a remotely accessible machine, you also have the advantage of
 being able to use a gui mail client locally and a text one remotely or
 serve your folders via an imap server and then you are not limited at all.

tell me about this  text one remotely.. I can ssh into my box, but this 
file, being mbox, isn't easily readable, or is this where mutt comes in?
actually it is a folder of mbox files.. when I checked yesterday, there were 
250 files..

-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Ron Johnson]

On 2009-09-01 04:45, Paul Cartwright wrote:

On Tue August 25 2009, Chris Jones wrote:

but looking at the procmailrc( now non-existant), then thinking about
my 200 kmail filters, I'm not sure I could tackle that task..

As another poster hinted, this is another example of the hidden benefits
of cloning the Microsoft model.


I'm not sure I understand.. what I DID find out was, my procmailrc file 
WORKED.. the problem is, I didn't do it right. I sent all my personal email ( 
for the last 4 days) to a mbox file in my home directory. I THOUGHT I had 
kmail setup to get that mail, but it didn't. SO, I had to forward it back to 
my /var/mail/user and resend it..

how do I get kmail to accept email from that mbox file, or did I do it wrong?


If your person message store is an mbox file, then I'd:
1. shutdown kmail,
2. append the errant mbox file onto your master mbox file,
3. rm any index files that kmail uses,
4. restart kmail.

--
Brawndo's got what plants crave.  It's got electrolytes!


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Ron Johnson]

On 2009-09-01 04:51, Paul Cartwright wrote:
[snip]


right now, on my system I have icedove, evolution, kmail, and claws, all setup 
for my local user. procmail seems to move the mail into an mbox file, and I 
haven't figured out how to get any email program to read an mbox folder.


But you see, that's the beauty of IMAP: the MUA does not know nor 
care where the email is stored, or how it's stored.



If this is a remotely accessible machine, you also have the advantage of
being able to use a gui mail client locally and a text one remotely or
serve your folders via an imap server and then you are not limited at all.


tell me about this  text one remotely.. I can ssh into my box, but this 


Text-based MUA.


file, being mbox, isn't easily readable, or is this where mutt comes in?
actually it is a folder of mbox files.. when I checked yesterday, there were 
250 files..


Store your email in an IMAP daemon, i.e., let the imapd worry 
about where and how it stores all your email in one central location.


Then, no matter where you are in the world, using whatever kind of 
client machine, you can access your email.


So, you can ssh into your home machine, then run Mutt/Alpine, or run 
Mutt/Alpine/Outlook/Tbird/Claws on a remote machine, and give it 
your home machine's IP address, your username and password.  (For 
that, though, you'd need to also run imapsd.)


Or... run a web server and webmail app on your home machine, and 
remotely access your email that way.


Bottom line: unless you are rooted to one MUA on one machine, IMAP 
is *the* way to go...


--
Brawndo's got what plants crave.  It's got electrolytes!


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Paul Cartwright]

On Tue September 1 2009, Ron Johnson wrote:
 If your person message store is an mbox file, then I'd:

this is the part I can't figure out.. I don't have an mbox setup on kmail, I 
don't see a way for it to read an mbox folder.. I tried to create an mbox 
folder in an account, but I don't see any way to do that.

 1. shutdown kmail,
 2. append the errant mbox file onto your master mbox file,
 3. rm any index files that kmail uses,
 4. restart kmail.

basically, I just did a for i in `ls`  /var/mail/ME done
so they all ended back up in my inbox.


-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Ron Johnson]

On 2009-09-01 05:19, Paul Cartwright wrote:

On Tue September 1 2009, Ron Johnson wrote:

If your person message store is an mbox file, then I'd:


this is the part I can't figure out.. I don't have an mbox setup on kmail, I 
don't see a way for it to read an mbox folder.. I tried to create an mbox 
folder in an account, but I don't see any way to do that.


There's *definitely* a way!  I just don't know it... :)


1. shutdown kmail,
2. append the errant mbox file onto your master mbox file,
3. rm any index files that kmail uses,
4. restart kmail.


basically, I just did a for i in `ls`  /var/mail/ME done
so they all ended back up in my inbox.



That'll work, too, because /var/mail/$USER is an mbox file...

--
Brawndo's got what plants crave.  It's got electrolytes!


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Micha Feigin]

On Tue, 1 Sep 2009 05:51:49 -0400
Paul Cartwright a...@pcartwright.com wrote:

 On Tue August 25 2009, Micha wrote:
   what benefit would I get from procmail?
 
  1. The ability to move from kmail to something else if you want without
  rewriting your rules.
 
 good idea.. I like that, especially when testing different email programs.
 
  2. The ability to pull mail without having kmail running (via a cron job or
  fetchmail daemon)
 I do that now with fetchmail, it brings it all in to my /var/mail/user
 
  3. Text file with regular expression based rules that you know where it
  resides and can back it up and human read it
 
 this I DO like ! the ability to use filters across email programs.
 
  If you don't care about these three than nothing (some consider the third a
  downside, not an improvement but that's personal preference not an
  absolute)
 
  On the downside, if you want to explicitly pull mail now, pulling mail from
  kmail doesn't pull the mail off your accounts, you need to do that
  explicitly from the command line
 
  It's all down to personal preferences.
 
  I played around a lot at the time looking for a mail client I'd be happy
  with (Still haven't found one) and worked quite a bit with mutt (I'm not
  sure if it even supports pulling mail itself) so fetchmail + procmail was
  the best option for me.
 
 right now, on my system I have icedove, evolution, kmail, and claws, all 
 setup 
 for my local user. procmail seems to move the mail into an mbox file, and I 
 haven't figured out how to get any email program to read an mbox folder.

you can put it in other formats as well such as maildir, although mail programs
should support mbox is it is the traditional unix format. If I recall correctly
though kmail, icedove and evolution are all notorious for storing mail in their
own hidden folder and they don't work with a different directory (I think that
there are hacks to do it though). I need to test again. One of the reasons I
use claws mail

another option is to setup a local imap server and contact that (an option a
lot of people use)

 
  If this is a remotely accessible machine, you also have the advantage of
  being able to use a gui mail client locally and a text one remotely or
  serve your folders via an imap server and then you are not limited at all.
 
 tell me about this  text one remotely.. I can ssh into my box, but this 
 file, being mbox, isn't easily readable, or is this where mutt comes in?
 actually it is a folder of mbox files.. when I checked yesterday, there were 
 250 files..
 

use mutt or pine or webmail


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Andrew Sackville-West]

On Wed, Aug 26, 2009 at 12:30:03AM -0400, Chris Jones wrote:
 On Tue, Aug 25, 2009 at 10:57:01PM EDT, Celejar wrote:
  On Tue, 25 Aug 2009 13:32:21 +0300
  Micha mi...@post.tau.ac.il wrote:
 
  ...
 
   3. Text file with regular expression based rules that you know where
   it resides and can back it up and human read it
 
  As the resident Sylpheed fanboy, I must point out that Sylph stores
  all its configuration, including its filter rules (which can utilize
  regex's), in fairly easy to understand XML files under
  $HOME/.sylpheed-2.0.
 
 Nice.. 
 
 So it should be fairly straightforward to generate a procmail .rc file
 and move the filters  where they rightly belong..

hmmm... that would be a lovely little bit of transformation code to
write... if I only had the time.

A


signature.asc
Description: Digital signature

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Celejar]

On Wed, 26 Aug 2009 00:30:03 -0400
Chris Jones cjns1...@gmail.com wrote:

 On Tue, Aug 25, 2009 at 10:57:01PM EDT, Celejar wrote:
  On Tue, 25 Aug 2009 13:32:21 +0300
  Micha mi...@post.tau.ac.il wrote:
 
  ...
 
   3. Text file with regular expression based rules that you know where
   it resides and can back it up and human read it
 
  As the resident Sylpheed fanboy, I must point out that Sylph stores
  all its configuration, including its filter rules (which can utilize
  regex's), in fairly easy to understand XML files under
  $HOME/.sylpheed-2.0.
 
 Nice.. 
 
 So it should be fairly straightforward to generate a procmail .rc file
 and move the filters  where they rightly belong..
 
 :-)


:/  Actually not too difficult; I did once write a perl script that
uses XML::Parser to convert Sylph / Claws XML based addressbooks to CSV
format, and doing something similar for the filter rules files
shouldn't be much different.

http://www.claws-mail.org//tools/claws-mail-clawsxml2csv.tar.gz 

Celejar
-- 
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Andrei Popescu]

On Mon,24.Aug.09, 20:56:27, Paul Cartwright wrote:

 but looking at the procmailrc( now non-existant), then thinking about my 200 
 kmail filters, I'm not sure I could tackle that task..

maildir (and procmail too as I hear, but I don't like its syntax) is 
*very* powerful. I recently did a major rewrite on my maildrop rules. I 
had one rule for each Debian list, now I have exactly one:

# These are the lists.debian.org lists
if (/^List-Id:.*debian-(.*)\.lists.debian.org/)
{
to Maildir/.debian.$MATCH1  
}

Similar for googlegroups, alioth, ... All that was needed was a bit of 
folder renaming ;)

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Micha]

On 8/24/2009 11:34 PM, Paul Cartwright wrote:

On Mon August 24 2009, Micha wrote:

Personally I use fetchmail + procmail to fetch and filter my mail


I use fetchmail to pull in my mail for all my domain accounts. Kmail pulls it
all in via my local user. From there I have many, MANY filters to put mail in
separate folders.
what benefit would I get from procmail?



1. The ability to move from kmail to something else if you want without 
rewriting your rules.
2. The ability to pull mail without having kmail running (via a cron job or 
fetchmail daemon)
3. Text file with regular expression based rules that you know where it resides 
and can back it up and human read it


If you don't care about these three than nothing (some consider the third a 
downside, not an improvement but that's personal preference not an absolute)


On the downside, if you want to explicitly pull mail now, pulling mail from 
kmail doesn't pull the mail off your accounts, you need to do that explicitly 
from the command line


It's all down to personal preferences.

I played around a lot at the time looking for a mail client I'd be happy with 
(Still haven't found one) and worked quite a bit with mutt (I'm not sure if it 
even supports pulling mail itself) so fetchmail + procmail was the best option 
for me.


If this is a remotely accessible machine, you also have the advantage of being 
able to use a gui mail client locally and a text one remotely or serve your 
folders via an imap server and then you are not limited at all.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Andrei Popescu]

On Ma,25.aug.09, 13:32:21, Micha wrote:
 
 On the downside, if you want to explicitly pull mail now, pulling
 mail from kmail doesn't pull the mail off your accounts, you need to
 do that explicitly from the command line

Not very familiar with kmail, but claws-mail (sylpheed too?) has 
configurable Actions which you can use to run external 
programs/scripts.

 I played around a lot at the time looking for a mail client I'd be
 happy with (Still haven't found one) and worked quite a bit with
 mutt (I'm not sure if it even supports pulling mail itself) so
 fetchmail + procmail was the best option for me.

mutt does SMTP, POP3 and IMAP now, but who cares ;)

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Chris Jones]

On Mon, Aug 24, 2009 at 08:56:27PM EDT, Paul Cartwright wrote:

[..]

 but looking at the procmailrc( now non-existant), then thinking about
 my 200 kmail filters, I'm not sure I could tackle that task..

As another poster hinted, this is another example of the hidden benefits
of cloning the Microsoft model.

CJ


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Ron Johnson]

On 2009-08-25 13:55, Chris Jones wrote:

On Mon, Aug 24, 2009 at 08:56:27PM EDT, Paul Cartwright wrote:

[..]


but looking at the procmailrc( now non-existant), then thinking about
my 200 kmail filters, I'm not sure I could tackle that task..


As another poster hinted, this is another example of the hidden benefits
of cloning the Microsoft model.


Is that a benefit or a benefit?

--
Obsession with preserving cultural heritage is a racist impediment
to moral, physical and intellectual progress.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Chris Jones]

On Tue, Aug 25, 2009 at 03:02:44PM EDT, Ron Johnson wrote:
 On 2009-08-25 13:55, Chris Jones wrote:
 On Mon, Aug 24, 2009 at 08:56:27PM EDT, Paul Cartwright wrote:

 [..]

 but looking at the procmailrc( now non-existant), then thinking
 about my 200 kmail filters, I'm not sure I could tackle that task..

 As another poster hinted, this is another example of the hidden
 benefits of cloning the Microsoft model.

 Is that a benefit or a benefit?

I'll leave that for the OP to decide.. 

Thanks for providing the historical background.. never knew Microsoft
had invented the all-in-one mailer that does one thing right.. make it
difficult to switch.

CJ


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Ron Johnson]

On 2009-08-25 18:29, Chris Jones wrote:

On Tue, Aug 25, 2009 at 03:02:44PM EDT, Ron Johnson wrote:

On 2009-08-25 13:55, Chris Jones wrote:

On Mon, Aug 24, 2009 at 08:56:27PM EDT, Paul Cartwright wrote:

[..]



but looking at the procmailrc( now non-existant), then thinking
about my 200 kmail filters, I'm not sure I could tackle that task..



As another poster hinted, this is another example of the hidden
benefits of cloning the Microsoft model.



Is that a benefit or a benefit?


I'll leave that for the OP to decide.. 


Thanks for providing the historical background.. never knew Microsoft
had invented the all-in-one mailer that does one thing right.. make it
difficult to switch.


Actually, I think that was a Nutscrape innovation, needed because 
of Windows' limited/non-existent multitasking abilities at the time.


--
Obsession with preserving cultural heritage is a racist impediment
to moral, physical and intellectual progress.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Celejar]

On Tue, 25 Aug 2009 13:32:21 +0300
Micha mi...@post.tau.ac.il wrote:

 On 8/24/2009 11:34 PM, Paul Cartwright wrote:
  On Mon August 24 2009, Micha wrote:
  Personally I use fetchmail + procmail to fetch and filter my mail
 
  I use fetchmail to pull in my mail for all my domain accounts. Kmail pulls 
  it
  all in via my local user. From there I have many, MANY filters to put mail 
  in
  separate folders.
  what benefit would I get from procmail?

...

 3. Text file with regular expression based rules that you know where it 
 resides 
 and can back it up and human read it

As the resident Sylpheed fanboy, I must point out that Sylph stores
all its configuration, including its filter rules (which can utilize
regex's), in fairly easy to understand XML files under
$HOME/.sylpheed-2.0.

Celejar
-- 
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Celejar]

On Tue, 25 Aug 2009 13:44:57 +0300
Andrei Popescu andreimpope...@gmail.com wrote:

 On Ma,25.aug.09, 13:32:21, Micha wrote:
  
  On the downside, if you want to explicitly pull mail now, pulling
  mail from kmail doesn't pull the mail off your accounts, you need to
  do that explicitly from the command line
 
 Not very familiar with kmail, but claws-mail (sylpheed too?) has 
 configurable Actions which you can use to run external 
 programs/scripts.

Of course Sylph does ;)

Celejar
-- 
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Chris Jones]

On Tue, Aug 25, 2009 at 10:57:01PM EDT, Celejar wrote:
 On Tue, 25 Aug 2009 13:32:21 +0300
 Micha mi...@post.tau.ac.il wrote:

 ...

  3. Text file with regular expression based rules that you know where
  it resides and can back it up and human read it

 As the resident Sylpheed fanboy, I must point out that Sylph stores
 all its configuration, including its filter rules (which can utilize
 regex's), in fairly easy to understand XML files under
 $HOME/.sylpheed-2.0.

Nice.. 

So it should be fairly straightforward to generate a procmail .rc file
and move the filters  where they rightly belong..

:-)

CJ



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Manoj Srivastava]

On Tue, Aug 25 2009, Andrei Popescu wrote:

 On Mon,24.Aug.09, 20:56:27, Paul Cartwright wrote:

 but looking at the procmailrc( now non-existant), then thinking about my 200 
 kmail filters, I'm not sure I could tackle that task..

 maildir (and procmail too as I hear, but I don't like its syntax) is 
 *very* powerful. I recently did a major rewrite on my maildrop rules. I 
 had one rule for each Debian list, now I have exactly one:

 # These are the lists.debian.org lists
 if (/^List-Id:.*debian-(.*)\.lists.debian.org/)
 {
   to Maildir/.debian.$MATCH1  
 }

 Similar for googlegroups, alioth, ... All that was needed was a bit of 
 folder renaming ;)

Hmm. Here is my Debian section; this pulls out emails for my
 packages from the pts, discards all other devel-changes mail;  pulls
 out boring debbugs  email, send bugs for my package into a package
 specific folder,  pulls out mail sent to bugs I reported separately,
 and then files every debian group to a separate folder.

Oh, I used to separate out ballots and votes, etc, but that is
 mostly done away with.

After mailagent, procmail seems ... underpowered.

manoj

##
##
##
#Debian  #
##
##
##
##
INITIAL  X-PTS-Package: /([-\w]+)/ 
  { ANNOTATE -d X-Agent-list 'pkg-%1';
  ASSIGN list 'pkg-%1';
  REJECT MailingList };
# X-Mailing-List To Resent-From Resent-To Resent-Reply-To Cc
INITIAL  X-Loop: /debian-devel-changes/i   { REJECT JUNK; };

# Do not wish to see acks for bug reports
INITIAL From: /own...@bugs.debian.org/, Subject: /Bug#\d+: Acknowledgement /
   { REJECT JUNK; };

# These have little information really
INITIAL From: /own...@bugs.debian.org/, Subject: /Bug#\d+: Info received/i
   { REJECT ClosedBugs };

INITIAL  X-Loop: /debian-bugs-dist/i{ REJECT DEBIANBUGS };
INITIAL  X-Loop: /own...@bugs.debian.org/i  { REJECT DEBIANBUGS };

INITIAL X-Loop X-Mailing-List To Resent-From Resent-To Resent-Reply-To Cc:
 /lists.debian.org/i  { REJECT DEBIAN };

INITIAL X-Loop X-Mailing-List To Resent-From Resent-To Resent-Reply-To Cc:
 /debian-ctte/i  { REJECT DEBIAN };

INITIAL X-Loop: /deity/i  { ASSIGN list deity; REJECT MailingList  };

INITIAL Sender From: /install...@ftp-master.debian.org/
{ ASSIGN list 'installed'; REJECT MailingList };

# Handle My own bugs
DEBIANBUGS To Resent-CC: /Manoj Srivastava/
{ REJECT MYBUGS };

MYBUGS X-Debian-PR-Package: /([-\w]+)/ 
  { ANNOTATE -d X-Agent-list 'pkg-%1';
  ASSIGN list 'pkg-%1';
  REJECT MailingList };

# Resent-To: Manoj Srivastava is for bugs I reported
MYBUGS /./
{ ASSIGN list 'debian';
  ANNOTATE -d X-Agent-list unknown-bug-list;
  REJECT MailingList;
};

#handle policy bugs
DEBIANBUGS X-Debian-PR-Package: /debian-policy/
{ ASSIGN list 'debian-policy';
  ANNOTATE -d X-Agent-list debian-list;
  REJECT MailingList;
};

DEBIANBUGS X-Debian-PR-Package: /general/
{ ASSIGN list 'debian-devel';
  ANNOTATE -d X-Agent-list general-bugs;
  REJECT MailingList;
};

DEBIANBUGS X-Debian-PR-Package: /wnpp/
{ ASSIGN list 'wnpp';
  ANNOTATE -d X-Agent-list debian-list;
  REJECT MailingList;
};

DEBIANBUGS Subject: /\[proposal\]/i, X-Debian-PR-Package: /debian-policy/
{ ASSIGN list 'debian-policy';
  ANNOTATE -d X-Agent-list debian-list;
  REJECT MailingList;
};

DEBIANBUGS All:  /./  
{
   ASSIGN list 'debian-bugs';
   ANNOTATE -d X-Agent-list debian-list;
   REJECT MailingList;
};

DEBIAN X-Loop:
  /(debian-bugs-(closed|forwarded))(-(request|dist))?...@lists.debian.org/i
   { REJECT ClosedBugs };
DEBIAN X-Loop X-Mailing-List To Resent-From Resent-To Resent-Reply-To Cc :
   /(debian-ctte+)(-(request|dist|private))?...@debian.org/gi
   { ASSIGN list '%1';
 ANNOTATE -d X-Agent-list debian-list;
 REJECT MailingList;
   };

DEBIAN  Subject: /CFV: Proposal/, X-Loop: /debian-vote/ { REJECT VOTE };

DEBIAN X-Loop: /(debian-[\w-]+)(-(request|dist))?...@lists.debian.org/gi
   { ASSIGN list '%1';
 SUBST #list /-(digest|request|dist)//gi;
 SUBST #list /devel-changes/changes/i;
 ANNOTATE -d X-Agent-list debian-list;
 REJECT MailingList;
   };

VOTE Body: /^\s*I vote\s+\w+\s+on/i
{ UNIQUE -a (vote); VACATION off; MESSAGE ~/etc/mail/voteack; 
  REJECT VOTEACK; };
VOTE 

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Ron Johnson]

On 2009-08-25 23:30, Chris Jones wrote:

On Tue, Aug 25, 2009 at 10:57:01PM EDT, Celejar wrote:

On Tue, 25 Aug 2009 13:32:21 +0300
Micha mi...@post.tau.ac.il wrote:



...



3. Text file with regular expression based rules that you know where
it resides and can back it up and human read it



As the resident Sylpheed fanboy, I must point out that Sylph stores
all its configuration, including its filter rules (which can utilize
regex's), in fairly easy to understand XML files under
$HOME/.sylpheed-2.0.


Nice.. 


So it should be fairly straightforward to generate a procmail .rc file
and move the filters  where they rightly belong..


Or, if you are in your right mind, maildrop.

--
Obsession with preserving cultural heritage is a racist impediment
to moral, physical and intellectual progress.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

RE: ProcMail, WAS: Re: Fetchmail and Gmail

[Kevin Ross]

 From: Paul Cartwright [mailto:a...@pcartwright.com]
 Sent: Monday, August 24, 2009 1:35 PM
 
 On Mon August 24 2009, Micha wrote:
  Personally I use fetchmail + procmail to fetch and filter my mail
 
 I use fetchmail to pull in my mail for all my domain accounts. Kmail
 pulls it
 all in via my local user. From there I have many, MANY filters to put
 mail in
 separate folders.
 what benefit would I get from procmail?

The processing happens at the server level instead of the client level.
This means the mail is already filed into the proper folders when you launch
your favorite mail client.  This also means you can easily move back and
forth between mail clients and not have to rewrite the rules for each
client, if the client even supports filters.  This is especially useful if
you also have a webmail server running on your computer.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Ron Johnson]

On 2009-08-24 17:11, Kevin Ross wrote:

From: Paul Cartwright [mailto:a...@pcartwright.com]
Sent: Monday, August 24, 2009 1:35 PM

On Mon August 24 2009, Micha wrote:

Personally I use fetchmail + procmail to fetch and filter my mail

I use fetchmail to pull in my mail for all my domain accounts. Kmail
pulls it
all in via my local user. From there I have many, MANY filters to put
mail in
separate folders.
what benefit would I get from procmail?


The processing happens at the server level instead of the client level.
This means the mail is already filed into the proper folders when you launch
your favorite mail client.  This also means you can easily move back and
forth between mail clients and not have to rewrite the rules for each
client, if the client even supports filters.  This is especially useful if
you also have a webmail server running on your computer.


But if Paul is asking the benefit of procmail over competing MDAs 
like maildrop, then the benefit is cryptic line noise a la Perl.


--
Obsession with preserving cultural heritage is a racist impediment
to moral, physical and intellectual progress.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Paul Cartwright]

On Mon August 24 2009, Ron Johnson wrote:
 But if Paul is asking the benefit of procmail over competing MDAs
 like maildrop, then the benefit is cryptic line noise a la Perl.

what I'm asking is.. will it benefit me to change the way I do email and add 
another program into the mix.
right now I do fetchmail to /var/mail/myuser
kmail picks up the mail, does all the filtering...
when I fire up icedove, it is a totally separate set of folders  emails ( 
dating back 2 years:)

I'm not sure I understand how I can use procmail to put mail into filtered 
folders that any mail program can read.
It would be nice to be able to switch programs  still have all my mail in the 
same folders..
but looking at the procmailrc( now non-existant), then thinking about my 200 
kmail filters, I'm not sure I could tackle that task..

-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

RE: ProcMail, WAS: Re: Fetchmail and Gmail

[Kevin Ross]

 From: Paul Cartwright [mailto:a...@pcartwright.com] 
 Sent: Monday, August 24, 2009 5:56 PM
 
 On Mon August 24 2009, Ron Johnson wrote:
  But if Paul is asking the benefit of procmail over competing MDAs
  like maildrop, then the benefit is cryptic line noise a la Perl.
 
 what I'm asking is.. will it benefit me to change the way I 
 do email and add 
 another program into the mix.
 right now I do fetchmail to /var/mail/myuser
 kmail picks up the mail, does all the filtering...
 when I fire up icedove, it is a totally separate set of 
 folders  emails ( 
 dating back 2 years:)
 
 I'm not sure I understand how I can use procmail to put mail 
 into filtered 
 folders that any mail program can read.
 It would be nice to be able to switch programs  still have 
 all my mail in the 
 same folders..
 but looking at the procmailrc( now non-existant), then 
 thinking about my 200 
 kmail filters, I'm not sure I could tackle that task..

Personally I use Maildirs.  Mail is delivered to a Maildir folder under each
user's home directory.  Folders in your mail client are also folders in the
Maildir.  Many mail clients can read Maildirs (Evolution being one.
Possibly Icedove, not sure though.)  Procmail understands Maildirs.  You
just tell it the folder name you want a message copied to in your rules.

You can also use an IMAP server, as I do.  IMAP allows folders, unlike POP3.
And most IMAP servers understand Maildirs.  Then just point any mail client
to the IMAP server (which can be localhost), and your mail client will
display the folder hierarchy.  Webmail servers will connect to an IMAP
server running on the localhost, so then you will be able to access your
email from any web browser anywhere, assuming your computer is reachable
from the Internet, and still see all your folders.

Also, personally I use a different mail filtering program, not procmail, but
the basic functionality is the same.

-- Kevin


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: ProcMail, WAS: Re: Fetchmail and Gmail

[Ron Johnson]

On 2009-08-24 19:56, Paul Cartwright wrote:

On Mon August 24 2009, Ron Johnson wrote:

But if Paul is asking the benefit of procmail over competing MDAs
like maildrop, then the benefit is cryptic line noise a la Perl.


what I'm asking is.. will it benefit me to change the way I do email and add 
another program into the mix.

right now I do fetchmail to /var/mail/myuser
kmail picks up the mail, does all the filtering...
when I fire up icedove, it is a totally separate set of folders  emails ( 
dating back 2 years:)


I'm not sure I understand how I can use procmail to put mail into filtered 
folders that any mail program can read.
It would be nice to be able to switch programs  still have all my mail in the 
same folders..
but looking at the procmailrc( now non-existant), then thinking about my 200 
kmail filters, I'm not sure I could tackle that task..




Adding to Kevin's excellent points:

The Windows Way (actually pioneered by Netscape, but who's 
quibbling?) combines server and client functionality into the MUA. 
This was needed on Win3.1 and Win9X, and tradition has kept it afloat.


On Linux, though, mail clients don't have to be so do-all.

By using a mail retriever, you've made the important First Step in 
divesting your Mail User Agent from non-User functionality.


The next step is to integrate procmail with fetchmail and have it 
deposit the email in a client-neutral location.  Maildir and IMAP 
were designed for this very purpose.


Then you will be able to use whatever MUA you want (or Mutt, if you 
are using Testing or Sid, and X ever craps out for a few days), on 
whatever machine you desire (as long as it is networked with your 
main PC).


--
Obsession with preserving cultural heritage is a racist impediment
to moral, physical and intellectual progress.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Procmail +Spamassassin+clamav

[Franck Delage]

Salut,

Peux-tu envoyer tes mails en texte, plutôt qu'en html ?

Nous sommes beaucoup à être des muttophiles, et du coup c'est
illisible. Ou alors faut ouvrir dans w3m, c'est de la paperasse...

Merci.
-- 
Franck Delage
Création et hébergements de sites web
www.web82.net


signature.asc
Description: Digital signature

Re: procmail rule to filter debian-user

[Michelle Konzack]

Am 2008-09-23 23:58:12, schrieb Bijan Soleymani:
 Hey everyone,
 
 I need a rule to filter debian-user into a seperate maildir. I know 
 there's the header:
 X-Maling-List: debian-user...
 
 so I tried:
 * ^X-Mailing-List: debian-user.*
 /home/bijan/Maildir/.lists.debian/
 
 and several variations, but none of them worked.

RTFM:   man procmailex

Because it is:

8--
  Maildir=/home/bijan/Maildir
  DEFAULT=${MAILDIR}

  :0
  * ^X-Mailing-List:.*debian-user@
  .lists.debian/
8--

Thanks, Greetings and nice Day/Evening
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
+49/177/935194750, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: procmail rule to filter debian-user

[s. keeling]

Alex Samad [EMAIL PROTECTED]:
  On Thu, Sep 25, 2008 at 05:44:00AM +0200, s. keeling wrote:
  
  my procmail rule, and mine splits each debian list into its own mbox,
  and handles newsfroup backscatter:
  
# 
# debian-${MATCH}
#
# The MATCH operator \/ matches whatever the regexp that follows
# it matches.
#
:0
* 1^0 ^X\-Mailing\-List:.*debian-\/[a-z.-]*
* 1^0 ^Newsgroups:.*debian.\/[a-z.-]*
* 1^0 ^Cc: [EMAIL PROTECTED]
{
  LOG=debian-${MATCH} - 
  :0:
  00.debian
}
 
  bit lost here.

My fault.

  I understand you pull out the debian mailing list with \/[a-z.-]*
  then you log to mailinglist specific log files with
  LOG=debian-${MATCH} - . 

No, that just tells procmail to mention debian-${MATCH} in the log
file, as in which folder got that mail.

  but doesn't this deposit all mails in
  00.debian , shouldn't it be 00.debian-${MATCH} ?

I mis-spoke, sorry.  Thanks for finishing my thought for me.  I used
to split them all into their own mbox.  Your 00.debian-${MATCH} is
correct for splitting them that way.

Now, I read Debian mailinglists with slrn via the mail to News gateway
linux.debian.${MATCH} :-).  I read mail with mutt, and only
occasionally get mails from Debian, and those all fall into
~/Mail/00.debian.


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)http://blinkynet.net/comp/uip5.html  Linux Counter #80292
- -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: procmail rule to filter debian-user

[Bob Cox]

On Tue, Sep 23, 2008 at 23:58:12 -0400, Bijan Soleymani ([EMAIL PROTECTED]) 
wrote: 

 Hey everyone,

 I need a rule to filter debian-user into a seperate maildir. I know  
 there's the header:
 X-Maling-List: debian-user...

 so I tried:
 * ^X-Mailing-List: debian-user.*
 /home/bijan/Maildir/.lists.debian/

How about:

:0 :
* [EMAIL PROTECTED]
/home/bijan/Maildir/.lists.debian/

Something very similar works for me (but not using maildir format,
hence no trailing slash).

-- 
Bob Cox.  Stoke Gifford, near Bristol, UK.
Registered user #445000 with the Linux Counter - http://counter.li.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: procmail rule to filter debian-user

[Steve Kemp]

On Tue Sep 23, 2008 at 23:58:12 -0400, Bijan Soleymani wrote:

 I need a rule to filter debian-user into a seperate maildir. I know  
 there's the header:
 X-Maling-List: debian-user...

  You might find this general purpose solution for handling multiple
 Debian lists useful:

http://www.debian-administration.org/articles/400

Steve
-- 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: procmail rule to filter debian-user

[Jamie Griffin]

  I need a rule to filter debian-user into a seperate maildir. I know  
  there's the header:
  X-Maling-List: debian-user...

:0
*^List-Id:*lists.debian.org
/home/bijan/Maildir/.lists.debian/

should do it. 

If you set some variables at the top of your .procmailrc you can easily avoid 
writing out the full path of the Maildir in each recipe; for example:

PATH=/usr/local/bin:/usr/bin:/bin:/usr/games
SHELL=/bin/bash
MAILDIR=/home/bijan/Maildir/
DEFAULT=$MAILDIR/inbox/

You may have done that already, but just in case you had not. It can help when 
writing the recipes. 

So, with that in mind, the following should work equally as well:

:0
*^List-Id:*lists.debian.org
.lists.debian/

The lack of the second colon at the start of the recipe is important when using 
Maildir format - it prevents the locking feature of procmail which is generally 
used for mbox format. Also, as others have pointed, don't miss the trailing 
slash which tells procmail to create the mailbox in Maildir format.

But, as recipes go these are really basic. Procmail is complex so it's worth 
spending some time reading up on it. 

HTH, 

Jamie


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: procmail rule to filter debian-user

[Andrei Popescu]

On Wed, 24 Sep 2008 08:05:02 +0100 Bob Cox wrote:

 How about:
 
 :0 :
 * [EMAIL PROTECTED]
 /home/bijan/Maildir/.lists.debian/
 
 Something very similar works for me (but not using maildir format,
 hence no trailing slash).

Isn't this going to miss all those posts that are Cc'd to debian-user?
(I have no idea of procmail rules, I prefer maildrop)

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: PGP signature

Re: procmail rule to filter debian-user

[s. keeling]

Ron Johnson [EMAIL PROTECTED]:
 
  If you aren't wedded to procmail for some other reason, then maybe 
  maildrop would be more to your liking, since it has a much simpler 
  syntax.  Here's my maildrop rule for filtering d-u mails:
 
  if ( /^X-Mailing-List:.*debian-user@lists.debian.org*/ )
 {
   to Maildir/.Lists.Debian.User.2008q3
 }

For completeness, that's not much less complex (aka line noise) than
my procmail rule, and mine splits each debian list into its own mbox,
and handles newsfroup backscatter:

  # 
  # debian-${MATCH}
  #
  # The MATCH operator \/ matches whatever the regexp that follows
  # it matches.
  #
  :0
  * 1^0 ^X\-Mailing\-List:.*debian-\/[a-z.-]*
  * 1^0 ^Newsgroups:.*debian.\/[a-z.-]*
  * 1^0 ^Cc: [EMAIL PROTECTED]
  {
LOG=debian-${MATCH} - 
:0:
00.debian
  }

I've been recommending noobs try maildrop first for years.  Procmail
may be a howitzer where a shiv is needed.  :-)


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)http://blinkynet.net/comp/uip5.html  Linux Counter #80292
- -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: procmail rule to filter debian-user

[s. keeling]

Bijan Soleymani [EMAIL PROTECTED]:
 
  I need a rule to filter debian-user into a seperate maildir. I know 
  there's the header:
  X-Maling-List: debian-user...
 
  so I tried:
  * ^X-Mailing-List: debian-user.*
  /home/bijan/Maildir/.lists.debian/
 
  and several variations, but none of them worked.

Describe your understanding of worked.  Have you set VERBOSE=yes in
your .procmailrc?  What's the log file say happened?

These may be useful:

  PMDIR= $HOME/procmail
  LOGFILE  = $PMDIR/log
  LOGABSTRACT  = yes

See my other post for a working rule.


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)http://blinkynet.net/comp/uip5.html  Linux Counter #80292
- -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: procmail rule to filter debian-user

[s. keeling]

Andrei Popescu [EMAIL PROTECTED]:
  On Wed, 24 Sep 2008 08:05:02 +0100 Bob Cox wrote:
 
  How about:
  
  :0 :
  * [EMAIL PROTECTED]
  /home/bijan/Maildir/.lists.debian/
  
  Something very similar works for me (but not using maildir format,
  hence no trailing slash).
 
  Isn't this going to miss all those posts that are Cc'd to debian-user?
  (I have no idea of procmail rules, I prefer maildrop)

^TO_ is a procmail macro == (man procmailrc):

  
`(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-
   Z0-9_.])?)', which should catch all destination specifications
   containing a specific address. 


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)http://blinkynet.net/comp/uip5.html  Linux Counter #80292
- -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: procmail rule to filter debian-user

[Alex Samad]

On Thu, Sep 25, 2008 at 05:44:00AM +0200, s. keeling wrote:
 Ron Johnson [EMAIL PROTECTED]:
  
   If you aren't wedded to procmail for some other reason, then maybe 
   maildrop would be more to your liking, since it has a much simpler 
   syntax.  Here's my maildrop rule for filtering d-u mails:
  
   if ( /^X-Mailing-List:.*debian-user@lists.debian.org*/ )
  {
to Maildir/.Lists.Debian.User.2008q3
  }
 
 For completeness, that's not much less complex (aka line noise) than
 my procmail rule, and mine splits each debian list into its own mbox,
 and handles newsfroup backscatter:
 
   # 
   # debian-${MATCH}
   #
   # The MATCH operator \/ matches whatever the regexp that follows
   # it matches.
   #
   :0
   * 1^0 ^X\-Mailing\-List:.*debian-\/[a-z.-]*
   * 1^0 ^Newsgroups:.*debian.\/[a-z.-]*
   * 1^0 ^Cc: [EMAIL PROTECTED]
   {
 LOG=debian-${MATCH} - 
 :0:
 00.debian
   }

bit lost here.

I understand you pull out the debian mailing list with \/[a-z.-]*
then you log to mailingl ist specific log files with
LOG=debian-${MATCH} - .  but doesn't this deposit all mails in
00.debian , shouldn't it be 00.debian-${MATCH} ?

 
 I've been recommending noobs try maildrop first for years.  Procmail
 may be a howitzer where a shiv is needed.  :-)
 
 
 -- 
 Any technology distinguishable from magic is insufficiently advanced.
 (*)http://blinkynet.net/comp/uip5.html  Linux Counter #80292
 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me.
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 

-- 
BOFH excuse #110:

The rolling stones concert down the road caused a brown out


signature.asc
Description: Digital signature