Procmail partially working

[J. Zidar]

I have setup fetchmail to get my mail from my two pop3 accounts and to be then
processed by procmail. Mail is then processed by Spamassassin, messages that
were found to be spam "should" be moved to oblivion (/dev/null), but nothing
happens. I can still marked spam in my inbox.

What should I do? Is there a permission issue with /dev/null?

Here's my .procmailrc file:
#Take to SA
:0fw
| /usr/bin/spamassassin

#Move flagged spam into the bottomless Unix pit.
:0:
* ^X-Spam-Flag: YES
/dev/null

:0:
* ^X-Spam-Status: Yes
/dev/null

Thanks for any advice.

Jernej


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[J. Zidar]

Monday 28 of July 2003 15:14 je &F pisal:

>On Mon, Jul 28, 2003 at 02:56:38PM +0200, J. Zidar wrote:

>> I have setup fetchmail to get my mail from my two pop3 accounts and to
>> be then processed by procmail. Mail is then processed by Spamassassin,
>> messages that were found to be spam "should" be moved to oblivion
>> (/dev/null), but nothing happens. I can still marked spam in my inbox.
>>
>> What should I do? Is there a permission issue with /dev/null?
>>
>> Here's my .procmailrc file:
>> #Take to SA
>>
>> :0fw
>> :
>> | /usr/bin/spamassassin
>>
>> #Move flagged spam into the bottomless Unix pit.
>>
>> :0:
>>
>> * ^X-Spam-Flag: YES
>> /dev/null
>>

>:0: says to use a locallockfile, which by default is the destination
>
>filename with $LOCKEXT appended, and you won't be able to write to
>/dev/null.lock. Try ':0:$HOME/.procmail.spam-lock' or something instead.
>
>Cheers,
>
>--
>Colin Watson [cjwatson@flatline.org.uk]

I've done as your suggested an now no spam is seen in my inbox. cute.

Thank you a million,
Jernej Zidar


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Joey Hess]

Colin Watson wrote:

> > #Move flagged spam into the bottomless Unix pit.
> > :0:
> > * ^X-Spam-Flag: YES
> > /dev/null

>
> :0: says to use a locallockfile, which by default is the destination
> filename with $LOCKEXT appended, and you won't be able to write to
> /dev/null.lock. Try ':0:$HOME/.procmail.spam-lock' or something instead.

Better yet don't lock it at all, /dev/null really does not care if two
processes write to it at once.

--
see shy jo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/JUVD3xwsXJZQhyMRAgKJAKCV+dYCXS7hqtuBDvkqJRX0YPEawg CgpVmZ
wK9eO/ormM1T2u6pT3kbCoc=
=AVpW
-----END PGP SIGNATURE-----

[Colin Watson]

On Mon, Jul 28, 2003 at 11:46:11AM -0400, Joey Hess wrote:

> Colin Watson wrote:

[somebody broke attributions]

> > > #Move flagged spam into the bottomless Unix pit.
> > > :0:
> > > * ^X-Spam-Flag: YES
> > > /dev/null

> >
> > :0: says to use a locallockfile, which by default is the destination
> > filename with $LOCKEXT appended, and you won't be able to write to
> > /dev/null.lock. Try ':0:$HOME/.procmail.spam-lock' or something instead.

>
> Better yet don't lock it at all, /dev/null really does not care if two
> processes write to it at once.

Obviously I need more coffee :-)

--
Colin Watson [cjwatson@flatline.org.uk]


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Alan Connor]

> From [email]cjwatson@debian.org[/email] Mon Jul 28 09:51:49 2003

>
>
> On Mon, Jul 28, 2003 at 11:46:11AM -0400, Joey Hess wrote:

> > Colin Watson wrote:

> [somebody broke attributions]

> > > > #Move flagged spam into the bottomless Unix pit.
> > > > :0:
> > > > * ^X-Spam-Flag: YES
> > > > /dev/null
> > >
> > > :0: says to use a locallockfile, which by default is the destination
> > > filename with $LOCKEXT appended, and you won't be able to write to
> > > /dev/null.lock. Try ':0:$HOME/.procmail.spam-lock' or something instead.

> >
> > Better yet don't lock it at all, /dev/null really does not care if two
> > processes write to it at once.

>
> Obviously I need more coffee :-)
>
> --
> Colin Watson [cjwatson@flatline.org.uk]
>

I have heard that it is a bad idea to use lockfiles with /dev/null in procmail.

The source was more than credible but couldn't remember why....


Alan


--

For Linux/Bash users: Eliminate spam from your life
with the Mailbox-Sentry-Program. See the thread
MSP on comp.mail.misc for the latest version.



--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]