Danke, für die Rechtschreibprüfung! War ein dummer Fehler von mir, stand
so tatsächlich drin.
\\\||///
\\ - - // .~..~. .~. .~.
( @ @ ) / V \ / V \ / V \ / V \
-oOo--( )--oOo---/ ( ) \ ---/ ( ) \---/ ( ) \---/ ( )
Guten Morgen Leute,
kann mir jemand bei procmail helfen?
Procmail funktioniert soweit, bis auf das log-file.
| VERBOSE= yes
| LOGABSTRACT=all
| MAILDIR=$HOME/Mail
| PROCMAILDIR=$HOME/.procmail
| LOGFILE=$PROGMAILDIR/log
Das Verzeichnis .procmail habe ich angelegt und mit touch auch eine
Datei
On Wed, 27 Nov 2002 06:22:14 +0100,
Oliver Fuchs wrote:
On Wed, 27 Nov 2002, csj wrote:
On Tue, 26 Nov 2002 06:24:11 +0100, Oliver Fuchs wrote:
On Mon, 25 Nov 2002, csj wrote:
Why doesn't the following .procmailrc recipe work?
:0fwh
it has to be
:0 fwh
On Thu, 28 Nov 2002, csj wrote:
I've checked that one out. It seems you still need some sed
tricks.
Hi,
I added your .procmailrc receipe and tested your configuration:
:0 fwh
| sed -e 's/^List-Post:/X-Mailing-List-Post-Address:/I ; s/mailto://'
sedprocmail
And it worked:
X-Mailing
On Tue, 26 Nov 2002 06:24:11 +0100, Oliver Fuchs wrote:
On Mon, 25 Nov 2002, csj wrote:
Why doesn't the following .procmailrc recipe work?
:0fwh
it has to be
:0 fwh
| sed -e 's/^List-Post:/X-Mailing-List-Post-Address:/I ; s/mailto://'
What exactly do you want to do here
On Wed, 27 Nov 2002, csj wrote:
On Tue, 26 Nov 2002 06:24:11 +0100, Oliver Fuchs wrote:
On Mon, 25 Nov 2002, csj wrote:
Why doesn't the following .procmailrc recipe work?
:0fwh
it has to be
:0 fwh
| sed -e 's/^List-Post:/X-Mailing-List-Post-Address:/I ; s/mailto
On Mon, 25 Nov 2002, csj wrote:
Why doesn't the following .procmailrc recipe work?
:0fwh
it has to be
:0 fwh
| sed -e 's/^List-Post:/X-Mailing-List-Post-Address:/I ; s/mailto://'
What exactly do you want to do here?
Oliver
--
... don't touch the bang bang fruit
--
To UNSUBSCRIBE
Why doesn't the following .procmailrc recipe work?
:0fwh
| sed -e 's/^List-Post:/X-Mailing-List-Post-Address:/I ; s/mailto://'
This is supposed to work on the following header:
List-Post: mailto:[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
-in der procmailrc wie folgt angegeben:
irgendwo/mbox # nichts nach dem Namen
(also mbox ist dann die Datei mit den Mails)
Maildir-Format: verwendet z.B. vom courier-IMAP-Server: Mails werden
jeweils in einer Datei in Ordnern verwaltet, wobei in jedem Ordner drei
Unterordner new, cur und tmp vorhanden
Hallo,
ich hab ein kleines Problem, irgendwie kommen keine Mails mehr mit
dieser .procmailrc an:
VERBOSE=yes
LOGFILE=procmail.log
:0fw
* 256000
| spamc
:0:
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
/dev/null
:0:
* ^X-Spam-Status: Yes
/home/martin/spam
:0 Wc
| razor-check
:0 Wa
/home
Hallo!
* Martin Hoefling wrote/schrieb:
dieser .procmailrc an:
| razor-check
Mein Spamassassion ruft razor automatisch auf, deiner nicht?
Woran könnte das liegen?
In meiner steht am Ende:
:0:
* ^To.*
$DEFAULT
(Wobei $DEFAULT natürlich definiert ist)
Gruß
//Robert W.
--
Q
das nirgends definiert ist (wie
im Bsp von Martin) dann scheint procmail gar nichts zu tun.
Also entweder:
ans Ende der procmailrc:
:0
/home/martin/inbox
Oder an den Anfang der procmailrc:
MAILDIR=$HOME #oder auch /home/martin
DEFAULT=$MAILDIR/inbox
LOGFILE=$MAILDIR/procmail.log
Gruss
Jens
... jetzt wirds immer lustiger,
ich hab am ende die Regel eingefügt, allerdings schreibt er alles in
eine Mail rein, also ich sehe praktisch alle Mails in einer.
Woran könnte das jetzt schon wieder liegen, ich rufe meine Mails mit
Evolution vom UW Imap ab.
Viele Grüsse
Martin
--
Häufig
Hi Martin,
Martin Hoefling schrieb:
ich hab am ende die Regel eingefügt, allerdings schreibt er alles in
eine Mail rein, also ich sehe praktisch alle Mails in einer.
Ich hatte mal ein ähnliches Problem. Ich hatte damals in meiner
.fetchmailrc procmail als MDA eingetragen, und hatte auch alle
Hello
If I set up a global /etc/procmailrc file for using spamassassin, it
seems to be ignored (ie, spamassassin doesn't ever get run).
So is there any setting that needs to be changed / made to the plain
vanilla exim of the testing distribution to allow this?
Cheers,
Sven
PS: Please CC: me
Sven == Sven Burgener [EMAIL PROTECTED] writes:
Sven Hello If I set up a global /etc/procmailrc file for using
Sven spamassassin, it seems to be ignored (ie, spamassassin
Sven doesn't ever get run).
Sven So is there any setting that needs to be changed / made to
Sven
Hola,
tengo un problema con procmail, he montado un procmail para limitar los
mails demas de 1Mg, el problema es, que el procmail en mi homedir va y
en el de otro user no, a ver si se os ocurre pq puede ser.
Los permisos estan bien grupo y usuario tb, el procmail es:
:0
*!^From:.*([EMAIL
tengo un problema con procmail, [...]
Pon
LOGFILE=$HOME/registro
VERBOSE=yes
en el fichero .procmailrc y analiza el contenido de `registro' después
de enviar mensajes de prueba.
Gostaria de saber como mandar todas os emails com o campo TO
[EMAIL PROTECTED] para uma pasta qualquer_lista. Estou
recebendo muitos emails de diferentes listas e me dei mal quando apaguei
um email de um professor da universidade sem me dar conta.
Obrigado,
C.A.R.L.O.S.:
boa política filtrar as listas pelo campo TO, pode ter sido
mandado para a lista pelo campo CC ou BCC e não seria filtrado. Utilize
algum campo que seja adicionado pelo gerenciador de lista.
Exemplo do meu $HOME/.procmailrc:
:0
* ^X-Mailing-List: debian-user-portuguese@lists.debian.org
debian
ele tem
recursos de filtragem de mensagens.
Não é uma boa política filtrar as listas pelo campo TO, pode ter sido
mandado para a lista pelo campo CC ou BCC e não seria filtrado. Utilize
algum campo que seja adicionado pelo gerenciador de lista.
Exemplo do meu $HOME/.procmailrc:
:0
* ^X
.
Exemplo do meu $HOME/.procmailrc:
:0
* ^X-Mailing-List: debian-user-portuguese@lists.debian.org
debian-user-portuguese
Esta regra manda todas as mensagens desta lista para o arquivo
debian-user-portuguese.
Dessa maneira entao nao importa se eh para o TO ,CC ou para o BCC ele vai
para
On Fri, Sep 20, 2002 at 12:14:41PM +0200, Santiago Vila wrote:
Faro wrote:
Umm, no me hagas mucho caso (o si), pero creo que si aplicas esa
regla vas a eliminar el 90% del correo válido.
Estoy completamente de acuerdo. Hazle caso :-)
Por si no te ha quedado claro. Hazle caso :)
Hola:
Hace poco que estoy metiéndome con el procmailrc para tratar de recibir
menos spam. Y hoy me dí cuenta de que hay varios mails (spam) que siguen
llegando, algo que tienen en común es que no son enviados por ningún MUA (el
header X-Mailer no aparece en el mensaje).
Mi
... y entonces Matias escribió:
Hola:
Hace poco que estoy metiéndome con el procmailrc para tratar de recibir
menos spam. Y hoy me dí cuenta de que hay varios mails (spam) que siguen
llegando, algo que tienen en común es que no son enviados por ningún MUA (el
header X-Mailer
On Fri, Sep 20, 2002 at 04:36:33AM -0300, Matias wrote:
Hola:
Hace poco que estoy metiéndome con el procmailrc para tratar de recibir
menos spam. Y hoy me dí cuenta de que hay varios mails (spam) que siguen
llegando, algo que tienen en común es que no son enviados por ningún MUA (el
El Fri, 20 Sep 2002 09:42:32 +0200
Faro [EMAIL PROTECTED] escribió:
Mi pregunta es: ¿Cómo pongo una regla en el procmailrc para que si en los
headers no aparece un X-Mailer: lo envie a /dev/null?
Umm, no me hagas mucho caso (o si), pero creo que si aplicas esa
regla vas
El Fri, 20 Sep 2002 10:04:18 +0200
Ignacio García Fernández [EMAIL PROTECTED] escribió:
On Fri, Sep 20, 2002 at 04:36:33AM -0300, Matias wrote:
Hola:
Hace poco que estoy metiéndome con el procmailrc para tratar de recibir
menos spam. Y hoy me dí cuenta de que hay varios mails (spam
... y entonces Matias escribió:
Justamente por eso, los correos comunes tienen un header X-Mailer |
User-Agent pero el spam que estoy recibiendo no. Y quisiera que los correos
que _no_ tienen este header desecharlos.
Creo que lo que necesitas usar es '!' para negar una condición y
... y entonces Faro escribió:
... y entonces Matias escribió:
Justamente por eso, los correos comunes tienen un header X-Mailer |
User-Agent pero el spam que estoy recibiendo no. Y quisiera que los
correos que _no_ tienen este header desecharlos.
Creo que lo que necesitas usar
Faro wrote:
Umm, no me hagas mucho caso (o si), pero creo que si aplicas esa
regla vas a eliminar el 90% del correo válido.
Estoy completamente de acuerdo. Hazle caso :-)
Usa herramientas ya hechas como razor y spamassassin.
Hi,
How to wrap long lines in .procmailrc? With \ or pressing simply enter?
Thanks
Attila
--
-
- Mail: [EMAIL PROTECTED]; Debian 3.0 Linux / 2.2.20 / exim -
- PGP key: gpg --keyserver keys.pgp.com --recv-key 0x2cc33acb
On Sat, 07 Sep 2002, Attila Csosz wrote:
Hi,
How to wrap long lines in .procmailrc? With \ or pressing simply enter?
Hi,
see man procmailex
Oliver
--
... don't touch the bang-bang fruit
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Hi.
Ist es mit Hilfe der oben genannten Datei möglich, Nachrichten gleich
als gelesen zu markieren?
Criena
--
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Mon /home/anthony est en drwxrwxrwx
.procmailrc en -rw-r--r--
le répertoire Mail en drwxrwxrwx
On Sun, Apr 07, 2002 at 09:15:51PM -0400, VALLIET Manu wrote:
Le 08/04/02, Anthony GARZIANO a ecrit:
Bonsoir,
j'ai rédigé le procmail qui suit.
Mais cela ne veut pas marcher.
J'ai un
Dans son message du 8/4/2002, Anthony GARZIANO écrivait:
Mon /home/anthony est en drwxrwxrwx
.procmailrc en -rw-r--r--
le répertoire Mail en drwxrwxrwx
On Sun, Apr 07, 2002 at 09:15:51PM -0400, VALLIET Manu wrote:
Le 08/04/02, Anthony GARZIANO a ecrit:
Bonsoir,
j'ai rédigé le
Mon /home/anthony est en drwxrwxrwx
.procmailrc en -rw-r--r--
le répertoire Mail en drwxrwxrwx
Dans mon souvenir, procmail n'aime pas que .procmailrc ou le repertoire
où il se trouve soit world ou même group writable (cf. man procmail).
Sylvain.
--
Sylvain Soliman [EMAIL
Le lun 08/04/2002 a 14:36, Sylvain Soliman a ecrit :
Mon /home/anthony est en drwxrwxrwx
.procmailrc en -rw-r--r--
le répertoire Mail en drwxrwxrwx
Dans mon souvenir, procmail n'aime pas que .procmailrc ou le repertoire
où il se trouve soit world ou même group writable (cf. man
est en drwxrwxrwx
^
un seul o
.procmailrc en -rw-r--r--
le répertoire Mail en drwxrwxrwx
On Sun, Apr 07, 2002 at 09:15:51PM -0400, VALLIET Manu wrote:
Le 08/04/02, Anthony GARZIANO a ecrit:
Bonsoir,
j'ai rédigé le procmail qui suit
Bonsoir,
j'ai rédigé le procmail qui suit.
Mais cela ne veut pas marcher.
J'ai un message d'erreur :
couldn't read /home/anthoony/.procmailrc
Quelqu'un voit une erreur dans mon fichier, il marchait très bien sur la
même bécane avant la réinstallation.
Au revoir.
Anthony
PATH=$HOME/bin:/usr/local
Le 08/04/02, Anthony GARZIANO a ecrit:
Bonsoir,
j'ai rédigé le procmail qui suit.
Mais cela ne veut pas marcher.
J'ai un message d'erreur :
couldn't read /home/anthoony/.procmailrc
Quelqu'un voit une erreur dans mon fichier, il marchait très bien sur la
même bécane avant la réinstallation
Senhores, desculpe a pergunta idiota, mas ja procurei em alguns
howto e nao encontrei resposta.
Preciso criar uma regra de uns 50 emails de dominios
diferentes para uma armazenar tudo em uma unica pasta a ser acessa pelo
pine.
Exemplo: Preciso que quando eu receber
Experimente:
:0
* [EMAIL PROTECTED]
TESTE
Construa uma regra análoga, para [EMAIL PROTECTED] Observe que usei :0 e não
:0: e não usei ponto após o asterisco (*) inicial. Certifique-se de que a pasta
TESTE (com letra maiúscula) existe no diretório de mails (MAILDIR). Se
definiste no início do .procmailrc
a
pasta TESTE (com letra maiúscula) existe no diretório de mails (MAILDIR). Se
definiste no início do .procmailrc
Aqui, eu faço assim para mandar minhas listas de Unix para a pasta debian:
:0:
* ^From.*debian|^From.*prog-br|^From.*linux-br|^From.*suse-axp|^From.*tex-br
debian
/home/erik/.procmailrc
Sep 30 01:31:07 localhost postfix/local[24575]: 69E441D772:
to=[EMAIL PROTECTED], relay=local, delay=1, status=sent (|procmail)
Sep 30 01:31:07 localhost postfix/smtpd[24572]: C4BEE1D773:
client=localhost[127.0.0.1]
Sep 30 01:31:07 localhost postfix/cleanup[24573]: C4BEE1D773
On Sun, 30 Sep 2001 01:43:16 -0700, Erik Steffl wrote:
[...] it used to have 664 permissions but I changed it to:
-rw---1 erik erik 660 May 12 19:41
/home/erik/.procmailrc
and it still complains!
any ideas? TIA.
Could be the permissions of your home directory. Check
Ralf G. R. Bergs wrote:
On Sun, 30 Sep 2001 01:43:16 -0700, Erik Steffl wrote:
[...] it used to have 664 permissions but I changed it to:
-rw---1 erik erik 660 May 12 19:41
/home/erik/.procmailrc
and it still complains!
any ideas? TIA.
Could
for another thread.
Do you have DEFAULT set in your .procmailrc?
I do indeed, and The plot thickens:
MAILDIR=$HOME/Mail
DEFAULT=$MAILDIR/INBOX
It must be something funky with my regexes.
Do you have logging enabled? I won't pretend to understand everything
procmail dumps to logs
on Tue, Aug 14, 2001 at 10:21:15PM -0400, Bill Lovett ([EMAIL PROTECTED]) wrote:
A couple times now I've edited my .procmailrc file, unwittingly
screwed something up, and only discovered my mistake after a day or
two goes by with not a peep out of otherwise high traffic lists.
Please set your
A couple times now I've edited my .procmailrc file, unwittingly screwed
something up, and only discovered my mistake after a day or two goes by with
not a peep out of otherwise high traffic lists.
But what happens to a message when procmail gets confused by a broken recipe?
Nothing shows up
On Tue, Aug 14, 2001 at 10:21:15PM -0400, Bill Lovett wrote:
| A couple times now I've edited my .procmailrc file, unwittingly
| screwed something up, and only discovered my mistake after a day or
| two goes by with not a peep out of otherwise high traffic lists.
|
| But what happens
less-than-optimal according to the procmail man page:
Procmail should be invoked automatically over the .forward
file mechanism as soon as mail arrives.
But perhaps that is best left for another thread.
Do you have DEFAULT set in your .procmailrc?
I do indeed, and The plot
Is it possible to specify multiple action lines for any given
procmail rule?
Like, say I want to achieve the following requirements:
o rewrite the To: header field such that it will appear as what
I rewrite it at the recepient.
o do the same (or insert) a CC: header field.
o then send
On Friday, February 02, 2001 at 18:41:16 (+0100), Sven Burgener wrote:
--8--
:0
* ^From: Mail Delivery Subsystem
| (formail -I To: [EMAIL PROTECTED]) |\
(formail -I CC: [EMAIL PROTECTED], [EMAIL PROTECTED]) | $SENDMAIL -t
:0
! [EMAIL PROTECTED]
--8--
The first recipy is a delivering
want the mail to appear to be destined to [EMAIL PROTECTED]
instead of the user on the system that has the above .procmailrc file
and that receives this email in the first place.
Additionally, I want to add a CC: to the message on-the-fly, overwriting
an existing one, if there.
I must apologise
I keep getting a Suspecious rc file /home/lance/.procmailrc Coundn't
read rc file when I fetchmail -m 'procmail' and get mail from my ISP.
I tried creating a .procmailrc from the dotfile generator but I still
got the same message. Anyone know why this is happening or how to fix the
problem
I happened to see this in the www.procmail.org mailing list archives
yesterday. Sorry I don't know the answer off the top of my head, but it's
there.
On Sat, Mar 18, 2000 at 04:17:56PM -0600, Lance Hoffmeyer wrote:
I keep getting a Suspecious rc file /home/lance/.procmailrc Coundn't
read rc
I had a directory named '~' the other day and tried to delete it. Needless to
say it started to delete my home directory.
Now when I use fetchmail and it tries to read my .procmailrc it tells me it is
a suspicious file and won't read it.
Anyone know what is going on here? My rights
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 2 Jul 1999 18:38:40 -0500, Lance Hoffmeyer wrote:
it is in a directory called data (i.e. /data/~).
rmdir \~I think
- --
Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
ICQ: 5107343 |
On Fri, Jul 02, 1999 at 06:38:40PM -0500, Lance Hoffmeyer wrote:
Now when I use fetchmail and it tries to read my .procmailrc it tells me it
is a suspicious file and won't read it.
Anyone know what is going on here? My rights are set to read/write for
everyone. My user is the owner
I have a bash command to reach my ISP
alias getmail=fetchmail -m '/usr/bin/procmail -f - '
/home/lance/.procmailrc is 'owner = lance' 'group = lance'
given rwx rwx and other given read-only rights
here is the error I get
reading message 1 of 1 (746 octets
Hi,
It's me again. I looked what's in the logfile of smail in an attempt to
see what is wrong with my .forward and .procmailrc files. I cannot figure
out what to do next, but it seems to me that it is something wrong
_before_ procmail, so procmail does not get any mail to process.
I wonder why
Catalin Popescu [EMAIL PROTECTED] writes:
It's me again. I looked what's in the logfile of smail in an attempt to
see what is wrong with my .forward and .procmailrc files. I cannot figure
out what to do next, but it seems to me that it is something wrong
_before_ procmail, so procmail does
Catalin Popescu [EMAIL PROTECTED] writes:
---
02/04/1998 22:36:19: [m0y0BYR-000I3ZC] Received FROM:[EMAIL PROTECTED]
HO\ST:localhost PROTOCOL:smtp PROGRAM:sendmail ORIG-ID:[EMAIL PROTECTED]
SIZE:462
02/04/1998
part, which I've been meaning
to add for a while and just did. I notice most spam has bogus or useless
To: lines, so that makes filtering that nasty stuff all the easier.
Here's an abbreviated version of my .procmailrc:
--- SNIP ---
PATH=$HOME/bin:/usr/local/bin:/usr/bin:/bin
MAILDIR=$HOME/mail
The Filtering Mail FAQ explains how to set up both procmail and mailagent.
http://www.ii.com/internet/faqs/launchers/mail/filtering-faq/
Cheers,
- Jim
pgpzXLTTlL8Zs.pgp
Description: PGP signature
Attached to this letter you will find a procmailrc file. Adjust
the MAILDIR variable and are set.
Here's what I want to do:
1) mail addressed to me goes into the inbox (even from mailing lists)
2) mailing lists are separated (already working)
3) remaining messages go into a junk
Here's what I want to do:
1) mail addressed to me goes into the inbox (even from mailing lists)
2) mailing lists are separated (already working)
3) remaining messages go into a junk folder
any ideas?
-Paul
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL
101 - 168 of 168 matches
Mail list logo
