On Tue, Jan 15, 2002 at 03:06:42AM +0100, martin f krafft wrote:
| also sprach Thorsten Haude [EMAIL PROTECTED] [2002.01.15.0037 +0100]:
| Any suggestions here would be greatly appreciated.
| My mailer does this for me, you might consider to use another one.
|
| i see. (thorsten, ignore my
hmm, kanske ska tillägga att jag kör woody
ii sendmail 8.12.1-5
ii procmail 3.22-2
dessa .forward's har jag bl.a. testat
|IFS=' ' p=/usr/bin/procmail test -f $p exec $p -Yf- || exit
75 #orange
|IFS=' ' p=/usr/lib/sm.bin/procmail test -f $p exec $p -Yf- ||
exit 75 #orange
Alec wrote:
I want send all messages from [EMAIL PROTECTED] to /dev/null except for those
that contain (case insensitive) keyword in its subject. How can I do this?
I haven't tested this, but it should do the job:
:0:
* ^From:[EMAIL PROTECTED]
* !^Subject:.*keyword
/dev/null
You may have to
also sprach Stephen Gran [EMAIL PROTECTED] [2001.12.17.1639 +0100]:
This looks like maildir rather than mbox format - many people, and
some programs, prefer it. You'll have to look through your various
configs to see if any of them have a trailing / - e.g.
it's actually MH delivery as far as
Thus spake Martin A. Hansen:
hi
i have set up procmail to sort incoming mail into subfolders. the mail is
sortet and put in the subfolders all right, but every mail is put inside its
own folder so i get:
[EMAIL PROTECTED]:/home/maasha/mail# ls -al debian-user/
total 44
drwxr-xr-x
Martin A. Hansen wrote:
i have set up procmail to sort incoming mail into subfolders. the mail
is sortet and put in the subfolders all right, but every mail is put
inside its own folder so i get:
[EMAIL PROTECTED]:/home/maasha/mail# ls -al debian-user/
total 44
drwxr-xr-x2 maasha
on Fri, Dec 14, 2001 at 01:49:20PM -0900, Christopher S. Swingley ([EMAIL
PROTECTED]) wrote:
Hi
I recently changed my procmail rc file, and now I'm getting this
warning:
procmail: Extraneous locallockfile ignored
in my procmail logs. The change was:
:0:
^
The colon
El Thu, Dec 13, 2001 at 01:08:23PM +0100, Antonio Trujillo Carmona escribió:
¿Algien me puede ayudar a configurar el procmail para que los
mensajes de esta lista vallan al fichero ~/Mail/debian-es?
--*-- BEG: $HOME/.procmailrc --*--
MAILDIR=$HOME/Mail #you'd better make sure it exists
#
On Thursday 06 December 2001 17:32 pm, shock wrote:
So far, it's been *fantastic*. Mail::SpamAssassin is unbelievably
accurate, and the filter script behaves exactly as I expect it to.
I've been trying to install this module from CPAN with dh-make-perl. The
build fails claiming it can't
On Fri, Dec 07, 2001 at 12:20:29AM +, Pollywog wrote:
| On 2001.12.06 22:18 dman wrote:
| On Thu, Dec 06, 2001 at 09:01:36PM +, Pollywog wrote:
|
| | Maybe Procmail is in a different place than you set in your
| | procmailrc.
|
| What do you mean by this? I also have a long list of
On Fri, 7 Dec 2001 10:43:32 +0530
Raghavendra Bhat [EMAIL PROTECTED] wrote:
Get yourselves the razor, dman. It is very good at catching and
reporting spam.
apt-get install razor
I did this yesterday, but had to abandon it. I got quite a few errors and
messages sent back to the
On Thu, Dec 06, 2001 at 07:16:48PM -0500, dman wrote:
I saw a mention of a distributed spam-identification system in the
weekly news, so I'll check that out too sometime.
It's razor. I just installed it, and it correctly recognised the two spam
messages I had lying around in my mailbox :)
On Fri, Dec 07, 2001 at 05:26:33PM +, Phillip Deackes wrote:
| On Fri, 7 Dec 2001 10:43:32 +0530
| Raghavendra Bhat [EMAIL PROTECTED] wrote:
|
| Get yourselves the razor, dman. It is very good at catching and
| reporting spam.
|
| apt-get install razor
|
| I did this yesterday,
I've been thinking of making a similar thing, just so I can list each
spammer on one line instead of 4.
FYI, if you do something like this in your procmail recipe file:
SPAM=SPAM
SPAMMERS=$HOME/procmail/spammers
# Anti-spam
:0:
* ? (formail -x From: -x Sender: -x Reply-To:
On Fri, 7 Dec 2001 13:40:18 -0500
dman [EMAIL PROTECTED] wrote:
| I did this yesterday, but had to abandon it. I got quite a few errors
and
| messages sent back to the originator of the emails. This is part of my
| /var/log/exim/mainlog:
I think this might be relevant -
On Fri, 7 Dec 2001, Christopher S. Swingley wrote:
I've been thinking of making a similar thing, just so I can list each
spammer on one line instead of 4.
FYI, if you do something like this in your procmail recipe file:
SPAM=SPAM
SPAMMERS=$HOME/procmail/spammers
# Anti-spam
On Fri, Dec 07, 2001 at 11:21:57AM -0900, Christopher S. Swingley wrote:
| I've been thinking of making a similar thing, just so I can list each
| spammer on one line instead of 4.
|
| FYI, if you do something like this in your procmail recipe file:
|
| SPAM=SPAM
|
Klaus,
SPAM=SPAM
SPAMMERS=$HOME/procmail/spammers
# Anti-spam
:0:
* ? (formail -x From: -x Sender: -x Reply-To: -x Received: -x
Subject: | fgrep - iqf $SPAMMERS) .
$SPAM /|\
On 2001.12.06 20:23 dman wrote:
I've been getting a bunch of spam on a certain list. The latest
message has the following From: line :
From: Lisa J. [EMAIL PROTECTED]
(some have a different name, but the same address) I want to
automatically file these in the bit-bucket. Should be
dman wrote:
I've been getting a bunch of spam on a certain list. The latest
message has the following From: line :
From: Lisa J. [EMAIL PROTECTED]
(some have a different name, but the same address) I want to
automatically file these in the bit-bucket. Should be
straightforward,
On Thu, Dec 06, 2001 at 09:01:36PM +, Pollywog wrote:
| On 2001.12.06 20:23 dman wrote:
|
| I've been getting a bunch of spam on a certain list. The latest
| message has the following From: line :
|
| From: Lisa J. [EMAIL PROTECTED]
|
| (some have a different name, but the same
On 2001.12.06 20:23 dman wrote:
I've been getting a bunch of spam on a certain list. The latest
message has the following From: line :
i had the same problem with a different spammer. no matter what i did,
i simply could not get the procmail recipe to properly filter the
thing. i finally
On Thu, Dec 06, 2001 at 05:32:48PM -0600, shock wrote:
| On 2001.12.06 20:23 dman wrote:
|
| I've been getting a bunch of spam on a certain list. The latest
| message has the following From: line :
|
| i had the same problem with a different spammer. no matter what i did,
| i simply could
On 2001.12.06 22:18 dman wrote:
On Thu, Dec 06, 2001 at 09:01:36PM +, Pollywog wrote:
| Maybe Procmail is in a different place than you set in your
| procmailrc.
What do you mean by this? I also have a long list of other spammer
addresses in that same file, and those others get filed
dman [EMAIL PROTECTED] writes:
On Thu, Dec 06, 2001 at 05:32:48PM -0600, shock wrote:
| On 2001.12.06 20:23 dman wrote:
|
| I've been getting a bunch of spam on a certain list. The latest
| message has the following From: line :
|
| i had the same problem with a different spammer. no
* dman ([EMAIL PROTECTED]) spake thusly:
On Thu, Dec 06, 2001 at 05:32:48PM -0600, shock wrote:
| i had the same problem with a different spammer. no matter what i did,
| i simply could not get the procmail recipe to properly filter the
| thing.
at least I'm not a freak ;-)
nope, just a
On Thu, Dec 06, 2001 at 05:28:02PM -0700, Gary Hennigan wrote:
| dman [EMAIL PROTECTED] writes:
...
| I've been thinking of making a similar thing, just so I can list each
| spammer on one line instead of 4.
|
| You do know that you can use a logical OR in your rules right? The
| | symbol.
On Thu, Dec 06, 2001 at 01:17:30PM -0800, Craig Dickson wrote:
| dman wrote:
...
| :0
| * [EMAIL PROTECTED]
| /dev/null
|
| However the messages keep getting past these recipes and to my
| list-matching recipe.
|
| Those look like they ought to work. One thing, though I doubt it's
|
[Thu, Dec 06, 2001 at 07:16:48PM -0500] dman :
I saw a mention of a distributed spam-identification system in the
weekly news, so I'll check that out too sometime.
Get yourselves the razor, dman. It is very good at catching and
reporting spam.
apt-get install razor
--
ragOO,
Bonjour,
| formail -D 8192 msgid.cache
dans mon .procmailrc m'évitait de recevoir les doublons.
Ce n'est plus le cas depuis quelques jours. Je ne sais pas si c'est dû à
une modification dans procmail/formail/exim sur ma machine (je suis en
unstable) ou des modifications chez mes providers.
Richard Cobbe wrote:
I understood all of the rules that were posted except for one thing.
Just out of curiosity, what does the 1^0 above do? The procmail
manpages weren't much help.
Try man procmailsc and read up on scoring.
Craig
On Wed, 14 Nov 2001, Tres Hofmeister wrote:
I upgraded a potato box to woody recently. With the current
sendmail (8.12.1-2) and procmail (3.21.20011028.3.15.2-2), it looks
like the mail delivery agent (MDA) is sensible-mda, which seems to
use procmail as a first choice.
What
On (22/07/01 14:43), Lang Hurst wrote:
That works great. However I am often listening to my vorbis
collection. When my music is playing and a new email comes in, the
festival output just gets garbled with the music. I would like to set
up a procmail script that says
if xmms is playing:
On Sun, Jul 22, 2001 at 02:43:30PM -0700, Lang Hurst wrote:
I use the following procmail script to make festival speak the FROM and
SUBJECT headings of new email through my speakers:
SUBJECT=`formail -xSubject: \
| expand | sed -e 's/^[ ]*//g' -e 's/[ ]*$//g'`
SENDER=`formail -xFrom: \
|
On Thu, Oct 04, 2001 at 01:02:06AM +0200, [EMAIL PROTECTED] wrote:
if I use procmail, do I still need fetchmail? or exim/qmail? or procmail
can do the filtering, sending and receiving mail...
You still need fetchmail and exim (or whatever). Procmail only does 2
related things: it filters
Thus spake [EMAIL PROTECTED]:
if I use procmail, do I still need fetchmail? or exim/qmail? or procmail
can do the filtering, sending and receiving mail...
apropos procmail:
procmail (1) - autonomous mail processor
From the http://packages.debian.org site:
Can be used to create
On Wed, Oct 03, 2001 at 07:31:49PM -0400, Stephen Gran wrote:
Thus spake [EMAIL PROTECTED]:
if I use procmail, do I still need fetchmail? or exim/qmail? or procmail
can do the filtering, sending and receiving mail...
apropos procmail:
procmail (1) - autonomous mail processor
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 be the
El Mon, Sep 24, 2001 at 10:14:46PM +0200, Santiago Vila escribió:
Bueno, como veran no puedoi darle al procmail
Ahora, me filtra los mails, pero yo uso el pine.
Cuando creo la carpeta debian-list y me llegan los mails, en vez de crear
mails separados, me aparece un solo mail, el cual
Bueno, como veran no puedoi darle al procmail
Ahora, me filtra los mails, pero yo uso el pine.
Cuando creo la carpeta debian-list y me llegan los mails, en vez de crear
mails separados, me aparece un solo mail, el cual contiene todos los datos
de todos los mails que recibi..
El formato
El sáb, 22 de sep de 2001, a las 12:15:47 -0300, DIOS comento ...
Bueno, como veran no puedoi darle al procmail
Ahora, me filtra los mails, pero yo uso el pine.
Cuando creo la carpeta debian-list y me llegan los mails, en vez de crear
mails separados, me aparece un solo mail, el cual
Buena.
Cuando corro el procmail corre en primer plano y me impide el uso de la
terminal.
Yo quisiera que corra como un demonio, o por lo menos, que ande solamnte
cuando corro mi fetchmail...
Uy, esta me la se.
Te creas un fichero $HOME/.forward que contenga esto:
Y el viernes 21 de septiembre, DIOS escribió:
Cuando corro el procmail corre en primer plano y me impide el uso de la
terminal.
Yo quisiera que corra como un demonio, o por lo menos, que ande solamnte
cuando corro mi fetchmail...
Uy, esta me la se.
Te creas un fichero $HOME/.forward que
On Wed, 19 Sep 2001 17:03:41 EDT, Jason Rashaad Jackson writes:
OK. I have successfully gotten procmail up and running on my local host, a
nd it's happily filtering incoming mail. This is great for new stuff, but
what about all the old messages in my spoolfile that have piled (and piled
and
also sprach Jason Rashaad Jackson (on Wed, 19 Sep 2001 05:03:41PM -0400):
OK. I have successfully gotten procmail up and running on my local
host, and it's happily filtering incoming mail. This is great for
new stuff, but what about all the old messages in my spoolfile that
have piled (and
On Wed, 2001-09-19 at 17:03, Jason Rashaad Jackson wrote:
OK. I have successfully gotten procmail up and running on my local host, and
it's happily filtering incoming mail. This is great for new stuff, but what
about all the old messages in my spoolfile that have piled (and piled and
* Jason Rashaad Jackson [EMAIL PROTECTED] spake thus:
OK. I have successfully gotten procmail up and running on my local
host, and it's happily filtering incoming mail. This is great for new
stuff, but what about all the old messages in my spoolfile that have
piled (and piled and piled) up
Thank you!
That solved it and thanks again for the profound help.
--
* John Ericson [EMAIL PROTECTED]
* ICQ: 7325429 JID: [EMAIL PROTECTED]
* web: http://john.pp.se
On Mon, Sep 10, 2001 at 09:45:54PM +, John Ericson wrote:
I have a bit problem with 4 lines that lookes like this:
[...]
It works if I use:
* ^Subject: \[ Slashdot Message \] Daily Headlines
as only rule but I want to have an if .. or if ..
Could someone fill in the missing code? =)
On Mon, Sep 10, 2001 at 09:45:54PM +, John Ericson wrote:
I have a bit problem with 4 lines that lookes like this:
:0:
* ^Subject: 24 Hours of Slashdot Headlines For \
| ^Subject: \[ Slashdot Message \] Daily Headlines
in-slashdot_hl
You may want to write
:0:
* ^Subject: 24 Hours of
On 2001.09.05 23:25 Glyn Millington wrote:
SHELL=/bin/bash
LINEBUF=4096
PATH=/bin:/usr/bin:/usr/local/bin
VERBOSE=off
DEFAULT=$HOME/.incoming/other.spool
MAILDIR=$HOME/.incoming
LOGFILE=$HOME/Mail/procmaillog
FORMAIL=/usr/bin/formail
SENDMAIL=/usr/sbin/sendmail
Thanx for your
also sprach Timeboy (on Wed, 05 Sep 2001 09:18:56PM +0200):
:0
* ^To_ debian-user@lists.debian.org
Debian
you are writing to a file, so use a lockfile!
:0:
* ^To_ and so on (not the second colon after the 0)
but:
LOCKFILE=$HOME
this is your homedirectory. you can't write/lock that.
also sprach Glyn Millington (on Wed, 05 Sep 2001 10:25:52PM +0100):
If you use Exim then you should be able to use Procmail without a forward
file. Exim will find Procmail and use it.
you can configure postfix and qmail and sendmail to do the same.
# Back-p cache of 100 most recent messages
also sprach Timeboy (on Thu, 06 Sep 2001 10:00:04AM +0200):
Thanx for your suggestion. There are some new questions now: Why do you
use LINEBUF=4096? And for what is SENDMAIL= needed?
RTFM, will ya?
* [EMAIL PROTECTED]
And why TOdebian-user...? What does this TO du for you?
also
Martin F Krafft [EMAIL PROTECTED] writes:
also sprach Glyn Millington (on Wed, 05 Sep 2001 10:25:52PM +0100):
If you use Exim then you should be able to use Procmail without a forward
file. Exim will find Procmail and use it.
you can configure postfix and qmail and sendmail to do the same.
On 2001.09.06 13:30 Martin F Krafft wrote:
LOCKFILE=$HOME
this is your homedirectory. you can't write/lock that. just discard
the line and add the second colon, then lockfiles will be created
automatically based on the mailbox name.
Aha! An Explanation of this i hadn't find by reading man
On 2001.09.06 13:34 Martin F Krafft wrote:
RTFM, will ya?
And why TOdebian-user...? What does this TO du for you?
also RTFM, dude!
(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently\
(-Resent)?)-To):(.*[^a-zA-Z])?)
as opposed to your To_ which should be TO_ and is:
Hi!
What a bad thing. I experimented with my .procmailrec and lost 14 of
your mails. ARGHHH!! Next time i will use fetchmail -k for someting
like that.
Ok! If someone wrote me a message with subject Re: i810 sound?,
Re: procmail don't work or Re: isdnlog not working in the time
between 15:00
On Thu, Sep 06, 2001 at 06:25:59PM +0200, Timeboy wrote:
Hi!
What a bad thing. I experimented with my .procmailrec and lost 14 of
your mails. ARGHHH!! Next time i will use fetchmail -k for someting
like that.
Ok! If someone wrote me a message with subject Re: i810 sound?,
Re: procmail
with subject Re: i810 sound?,
Re: procmail don't work or Re: isdnlog not working in the time
between 15:00 and 16:40 clock Europe Berlin today, please send me
again if possible, so i can get a look to this lost mails.
That's what archives are for. It takes a bit for them to show up
On Wed, Sep 05, 2001 at 12:20:59PM +0200, Örjan Persson wrote:
tack för hjälpen ändå. hur funkar mailboxes +box egentligen?
Pluset är en så kallad mailbox shortcut[1], och i detta fallet
betyder det att mboxen ligger i din $folder-dir (specificeras i
muttrc).
Kommandot mailboxes
?rjan Persson wrote on Sep 04, 2001 at 08:44:57 PM:
fråga 2) jag sorterar t.ex. debian.se breven i
2001/09/debian-user-sweden, men när jag startar
mutt så måste jag gå igenom till 2001, 09, deb,
bara för att komma in i katalogen o kolla ifall
det finns nya mail, ska inte denna inställning
hej,
tack alla som hjälpt mig, jag har nu fått till
det, det var väldigt enkelt när man väl såg det.
var ett typo. så nu funkar det skit bra i mutt :)
örjan
--
[x] icq - 496723 [x] url - www.fobie.net
What might help would be knowing how you are calling procmail
when the message is coming in (ie- does it get call'd by the MTA as the
local deliver agent or via .forward)... Also it might help if you show'd
the actual procmail receipe you are trying to have executed... I for one
have
On 2001.09.05 18:00 Jeremy T. Bouse wrote:
What might help would be knowing how you are calling procmail
when the message is coming in (ie- does it get call'd by the MTA as the
local deliver agent or via .forward)...
I'ts bad! But i don't know that. In a RadHat book i've read that in
Timeboy [EMAIL PROTECTED] writes:
I'ts bad! But i don't know that. In a RadHat book i've read that in
most cases procmail will work automaticly with the installed MTA and
there is no neccessery thing to do. In man procmail i've read that i
need this .forward file if procmail is not
On Tue, Sep 04, 2001 at 08:44:57PM +0200, Örjan Persson wrote:
hej hej,
har tidigare använt pine, och började smått testa
mutt igen och börjar gilla det starkt (när jag
hittade pine alias filen :)
jag använder muttrc som jag hittade på denna sida:
http://mutt.lazygenes.net/
och sedan
Jason Majors wrote:
Is there a way to OR procmail conditions?
Yes, like this:
* ^(To|Cc|X-Apparently-To|From):.*@(foo|bar)\.com
$MAILDIR/foo/
This means if the To:, Cc:, X-Apparently-To:, or From: header contains
either @foo.com or @bar.com, put the message in $MAILDIR/foo/.
Craig
On Wed, Aug 29, 2001 at 09:03:48PM -0700, Craig Dickson scribbled...
Jason Majors wrote:
Is there a way to OR procmail conditions?
Yes, like this:
* ^(To|Cc|X-Apparently-To|From):.*@(foo|bar)\.com
$MAILDIR/foo/
This is ORing the contents of a condition. Trying to put the 20+
on Wed, Aug 29, 2001 at 08:54:34PM -0700, Jason Majors ([EMAIL PROTECTED])
wrote:
Is there a way to OR procmail conditions?
I have lots of lines like so:
:0
* (^From:.*Reel\.com)
/dev/null
:0
* (^From:.*sonypictures\.com)
/dev/null
You want a list processor:
:0
* test if sender
You can do this:
:0
* 1^0 ^cond 1
* 1^0 ^cond 2
* 1^0 ^cond 3
/dev/null
It uses scoring to do exactly what you want.
On Wed, Aug 29, 2001 at 08:54:34PM -0700, Jason Majors wrote:
Is there a way to OR procmail conditions?
I have lots of lines like so:
:0
*
El Wed, Aug 22, 2001 at 08:26:39AM +0200, Javier Fafián Alvarez contaba:
On Tue, Aug 21, 2001 at 07:08:54PM -0300, Santiago Pastorino wrote:
En el home de mi usuario archivo .procmailrc tengo lo siguiente:
:0
[EMAIL PROTECTED]
/dev/null
Pero con esto tengo que bajarlo y después se
On Tue, Aug 21, 2001 at 07:08:54PM -0300, Santiago Pastorino wrote:
En el home de mi usuario archivo .procmailrc tengo lo siguiente:
:0
[EMAIL PROTECTED]
/dev/null
Pero con esto tengo que bajarlo y después se aplica el filtro,
como hago para hacerlo directo sin tener que bajar un mensaje
... y entonces Santiago Pastorino escribió:
Pero con esto tengo que bajarlo y después se aplica el filtro,
como hago para hacerlo directo sin tener que bajar un mensaje
que tal vez sea grande.
No puedes con procmail que aplica los filtros una vez que has
bajado el mensaje.
Saludos.
Puedes usar mailfilter para filtrar antes de bajarte el correo entero.
Personalmente, aún no lo he probado: pero ya está en woody y según
leo en planeta linux argentina funciona bastante bien.
Échale un vistazo y decide tú mismo:
http://www.planetalinux.com.ar/article.php?aid=52
Una
Mauricio Vieira wrote:
Saudacoes,
como tinha apagado o meu .pinerc (com todas as minhas rules para as
milhares de listas que participo :), resolvi escrever o .procmailrc
as mensagens novas que chegam na minha INBOX ja estao sendo encaminhadas
para as devidas caixas postais de cada
On Mon, Jul 30, 2001 at 04:09:51PM -0300, Jordi S. Bunster wrote:
Hello list ... wonder if anyone gives me a hand on this one:
Here at my job two bosses need to send mail to everyone from time
to time. There're about 20 accounts only, so I did a small script
that runs every week and adds
Add this recipe:
# Begin
:0
* ! ([EMAIL PROTECTED])
* ! ([EMAIL PROTECTED])
/dev/null
# End
Or...you could just have procmail do the forwarding:
# Begin
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
# Not sure if it's commas or spaces. Try it on some dummy accounts first.
# Forwards
On 2001-07-30 16:09:51, Jordi S. Bunster wrote:
But ... right now everyone can send messages to that account. How
can I block mail to it from everyone except the two bosses (with
procmail?)
1. keep the list name secret and have everyone use bcc.
2. create a real mailbox, fetchmail and
I would pipe the contents of echo to a shell script. In that
script you could test for xmms with something like the
following:
#!/bin/bash
xmms=`ps -ef | grep xmms | grep -v grep`
if [ X$xmms = X ]; then
# xmms not running
echo $* | festival --tts
else
#
On Tue, Mar 06, 2001 at 01:02:30AM +0100, Santiago Vila wrote:
Diego Bote:
Tengo configurado el procmail para repartir el correo, y eso va
estupendo. Sin embargo cuando intento ponerle un script del tipo
|/home/mi_directorio/mis_scripts/el_script
en el .procmailrc de mi
On Tue, Mar 06, 2001 at 09:45:25AM +0100, Diego Bote wrote:
El script, por supuesto, tiene permisos de escritura. Este script lo
que hace es mirar el contenido de los mensajes que tienen un subjet
determinado y ejecuta las órdenes que éste, el mensaje, lleva como
contenidos. Repito
On Tue, Mar 06, 2001 at 06:28:21AM -0300, Blu wrote:
On Tue, Mar 06, 2001 at 09:45:25AM +0100, Diego Bote wrote:
El script, por supuesto, tiene permisos de escritura. Este script lo
que hace es mirar el contenido de los mensajes que tienen un subjet
determinado y ejecuta las órdenes
Hola amigos.
Todo solucionado.
Me explico. Ciertamente el script funcionaba desde línea de comando
pero no desde .procmailrc. Haciendo caso de las sugerencias del man puse un
logfile donde descubrí que el script era ejecutado pero no se encontraban los
ejecutables que
On Mon, Mar 05, 2001 at 07:41:28PM +0100, Diego Bote wrote:
Hola lista
Tengo configurado el procmail para repartir el correo, y eso va
estupendo. Sin embargo cuando intento ponerle un script del tipo
|/home/mi_directorio/mis_scripts/el_script
en el .procmailrc de mi
On Sun, Feb 25, 2001 at 05:17:24AM +, Gavin Hamill wrote:
Hullo!
I'm writing here 'because I never had this problem with Slackware' :)
Okie, in /var/spool/mail, I have a symlink from 'gdh' to my real mailbox
in /home/gdh/Mailbox, and this link in this preset dir lets crappy stuff
like
On Mon, 26 Feb 2001, Thomas Guettler wrote:
Do you really need this link? Why don't you don't you filter your
mails to different mboxes in your $HOME with procmail? (With a
.procmailrc)
Probably not, but it's handy for running the odd bit of legacy software
that needs this old 'standard'...
On Thu, Feb 15, 2001 at 07:40:40AM -0500, John Bacalle wrote:
* John Bacalle [EMAIL PROTECTED] [20010212 02:48]:
The following from man procmail should save the last 200 messages I have
received. But it just saves everything instead. My backup cache keeps
growing and growing till I manually
Primitivo Liberto dijo:
leí en las páginas man que:
Suspicious rcfile x The owner of the rcfile was not the recipient or root,
the file was world writable, or the directory that contained it was world
writable, or this was the default rcfile ($HOME/.procmailrc) and either it
was group
El viernes 09 de febrero de 2001 a la(s) 15:56:21 +0100, Amaya contaba:
Pero bueno, da igual... un ls -l por favor!!!
$ ls -ld .procmailrc .forward .
ls: .forward: No existe el fichero o el directorio
drwx--x--x 86 hue cc2k 6144 feb 10 13:23 ./
-rw---1 hue cc2k
On jue, feb 08, 2001 at 01:17:33 +0100, Amaya wrote:
Mande?
U... en Madrid te lo cuento, si viene Miquel también mejor, así no doy
una versión demasiado alterada de la noche de autos.
...Estoy muy cansada, ¿no?
Decidídamente: blinking_SI_/blinking.
Aprovecho el offtopic:
¿Alguien me
Javier Viñuales Gutiérrez dijo:
U... en Madrid te lo cuento, si viene Miquel también mejor, así no doy
una versión demasiado alterada de la noche de autos.
Con Miquel estuve ayer, precisamente... intentando irme a vivir al Laboratorio
;-)
Decidídamente: blinking_SI_/blinking.
He dormido
Amaya ha escrito:
La página man tampoco es muy concreta al respecto. Me voy a hacer una camisea
que ponga Suspicious rcfile, porque tatuármelo en el antebrazo ya me parece
de masoca y de macarra... ;-(
hola, a mi me paso eso mismo, suspicious rcfile y procmail no funcionaba
leí en las
Carles Pina i Estany:
En el FAQ de la lista linux-kernel (http://www.tux.org/lkml/) comentan que
para filtrar el correo se debería hacer:
# Linux-kernel list
:0: /var/lib/emacs/lock/!home!fred!mfilter!linux!kernel
* ^X-Mailing-List: [EMAIL PROTECTED]
On Sun, Dec 24, 2000 at 05:07:42PM -0200, Marcelo Chiapparini wrote:
Hi to all!
I am using fetchmail+exim+mutt as an email system. All the incomming emails
goes to /var/spool/mail/myaccount. I would like now to store the different
messages in separate mailboxes files defined in
Lo, on Sunday, December 24, Marcelo Chiapparini did write:
Hi to all!
I am using fetchmail+exim+mutt as an email system. All the incomming emails
goes to /var/spool/mail/myaccount. I would like now to store the different
messages in separate mailboxes files defined in /home/myaccount. I
On Mon, Dec 18, 2000 at 09:50:13AM +0100, Thorsten Haude wrote:
of such a recipe?
I asked for it a few ago. The trick is to let GPG do it. Put
set pgp_getkeys_command=
in your .muttrc and
keyserver wwwkeys.eu.pgp.net
in your .gnupg/options.
I have both of these options and will
Look on www.securityfocus.com: they had a thread about .procmailrc rules
for email trojans about the time of the (melissa?) virus.
On Mon, 13 Nov 2000 kmself@ix.netcom.com wrote:
on Mon, Nov 13, 2000 at 09:14:11PM -0900, Ethan Benson ([EMAIL PROTECTED])
wrote:
On Mon, Nov 13, 2000 at
%% Frodo Baggins [EMAIL PROTECTED] writes:
fb I use xemacs VM to read my email. I tried to install a
fb .procmailrc
fb file into my homedir, but that give me some big problems. More
fb specifically, I told procmail to put my mail into ~/Mail/INBOX, which
fb is my vm-primary-inbox.
801 - 900 of 1095 matches
Mail list logo
