* Guy Van Sanden [Apr 18. 2001 00:33]:

Strange as it might sound, I'm not getting that.... It seems to effect a number of people, but not everybody...

Maybe you had it like me in a folder for dupliciates? I use it to eliminate replies both from the list and personal. It works by caching the unique message-id for the mail, and then saving as a duplicate it if just processed. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.

I got over 400 exact copies (to the second) of your message! Ya think they got the point? ;-) JLK On Wednesday 18 April 2001 02:28, Guy Van Sanden wrote:

Strange as it might sound, I'm not getting that.... It seems to effect a number of people, but not everybody...

...

...

...

...

...

>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 18/04/2001, 08:56:10, Eddie Howson wrote

regarding [SLE] Everlasting email messages:

...

I am receiving the same email message from Yves Baudrier

...

re: [SLE] help setting up lexmark z52 printer. What is going on and

how can

...

it be stopped? I am currently filtering it but need a more permanent solution. I don't think I am the only one.

Thanks

Eddie

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com

* S.Toms [Apr 18. 2001 17:10]:

Use the following within your procmailrc file

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

which will take care of any duplicate messages that anyone sends. Give you an idea, the above filtered out approximately 170 messages and only put 1 of them within my Inbox.

That is the rule I talked about in another posting. Works really well. It can backup the dupes etc. man procmail{,rc,ex} have more info. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.

I noticed that you posted this nice little procmail recipe about a month ago. I tried it out but get a list of error messages in my log file for each message that arrives. First, I think the way this is written I should be getting an error. Have I done something wrong or is it normal to get the following with each message... procmail: Lock failure on "msgid.lock" formail: Couldn't open "msgid.cache" Second, assuming that I should get an error except when it works is there a way of avoiding all these errors messages (other than stopping loggin). I get a lot of mail and this is creating a huge log file! Third, should there be a "." infront of the msgid.cache? Gerry On Wed, 18 Apr 2001, S.Toms wrote:

Use the following within your procmailrc file

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

which will take care of any duplicate messages that anyone sends. Give you an idea, the above filtered out approximately 170 messages and only put 1 of them within my Inbox.

The rule is... :0Wh: msgid.lock | formail -D 8192 .msgid.cache I have it in my home directory .procmailrc file. Hmmm, sounds like this may be one fo the problems (ie permissions). Gerry On Sat, 5 May 2001, Mads Martin Jørgensen wrote:

* gerry@dorfam.ca [May 05. 2001 08:32]:

...

I noticed that you posted this nice little procmail recipe about a month ago. I tried it out but get a list of error messages in my log file for each message that arrives.

First, I think the way this is written I should be getting an error. Have I done something wrong or is it normal to get the following with each message...

procmail: Lock failure on "msgid.lock" formail: Couldn't open "msgid.cache"

Can you show us the rule? This indecates that you're trying to write the msgid.{lock,cache} in a place without rights.

-- "The lyf so short, the craft so long to learne." Geoffrey Chaucer