Re: Interesting Fetchmail Foible
On Friday 18 January 2008, Александър Л. Димитров wrote: Quoth David Baron: On Wednesday 16 January 2008, Александър Л. Димитров wrote: Quoth David Baron: Would there be any script, option, or such to solve this problem in a more elegant manner and leave things alone when the network is doing what it is supposed to do? Depends. Are you using procmail, too? If so, you might be interested in the following rule I have in my .procmailrc: # Dupes? Nuke'em! :0 Wh: msgid.lock : | $FORMAIL -D 8192 msgid.cache That's it. All there is to it. Just put that little beast in and all duplicate massages will get deleted. Great. Just put it in. $FORMAIL, I assume is a predefined macro for procmail? msgid -- do I need to install this? No, $FORMAIL holds the location of the 'formail' program, most likely /usr/bin/formail (just type `which formail', to find out). msgid is nothing more than a name for the file the already-retrieved message-ids will get stored in, nothingadditional Thanks. I replaced $FORMAIL with /usr/bin/formail. Locate msgid | grep cache only yields something connected with opera. Their are a bunch of msgid thingies connected with kde and some other things but these two items are not found.
Re: Interesting Fetchmail Foible
On Friday 18 January 2008, Александър Л. Димитров wrote: Quoth David Baron: On Wednesday 16 January 2008, Александър Л. Димитров wrote: Quoth David Baron: Would there be any script, option, or such to solve this problem in a more elegant manner and leave things alone when the network is doing what it is supposed to do? Depends. Are you using procmail, too? If so, you might be interested in the following rule I have in my .procmailrc: # Dupes? Nuke'em! :0 Wh: msgid.lock : | $FORMAIL -D 8192 msgid.cache That's it. All there is to it. Just put that little beast in and all duplicate massages will get deleted. Great. Just put it in. $FORMAIL, I assume is a predefined macro for procmail? msgid -- do I need to install this? No, $FORMAIL holds the location of the 'formail' program, most likely /usr/bin/formail (just type `which formail', to find out). msgid is nothing more than a name for the file the already-retrieved message-ids will get stored in, nothingadditional Thanks. I replaced $FORMAIL with /usr/bin/formail. Locate msgid | grep cache only yields something connected with opera. Their are a bunch of msgid thingies connected with kde and some other things but these two items are not found. Oooh! It created that cache on my home directory. Is this where it belongs? Seem to be this stuff belongs somewhere on /var...
Re: Interesting Fetchmail Foible
Quoth David Baron: On Wednesday 16 January 2008, Александър Л. Димитров wrote: Quoth David Baron: Would there be any script, option, or such to solve this problem in a more elegant manner and leave things alone when the network is doing what it is supposed to do? Depends. Are you using procmail, too? If so, you might be interested in the following rule I have in my .procmailrc: # Dupes? Nuke'em! :0 Wh: msgid.lock : | $FORMAIL -D 8192 msgid.cache That's it. All there is to it. Just put that little beast in and all duplicate massages will get deleted. Great. Just put it in. $FORMAIL, I assume is a predefined macro for procmail? msgid -- do I need to install this? No, $FORMAIL holds the location of the 'formail' program, most likely /usr/bin/formail (just type `which formail', to find out). msgid is nothing more than a name for the file the already-retrieved message-ids will get stored in, nothingadditional signature.asc Description: Digital signature
Re: Interesting Fetchmail Foible
On Tue, 15 Jan 2008 23:23:43 +0100 Александър Л. Димитров [EMAIL PROTECTED] wrote: Quoth David Baron: I have been having network problems lately. Comes up for a second, then dies, repeatedly. So I get the same emails, over and over again. Fetchmail can apparently get them but not tell the provider that they have been received so delete them on their server. Until the network is up properly, I must shut down fetchmail. Would there be any script, option, or such to solve this problem in a more elegant manner and leave things alone when the network is doing what it is supposed to do? Depends. Are you using procmail, too? If so, you might be interested in the following rule I have in my .procmailrc: # Dupes? Nuke'em! :0 Wh: msgid.lock | $FORMAIL -D 8192 msgid.cache That's it. All there is to it. Just put that little beast in and all duplicate massages will get deleted. (there is something similar for maildrop, too. Just in case you use it - but I forgot, just what it was... GIYF ;-) ). Maildrop's reformail utility is similar to procmail's formail; it also has a -D option. Aleks Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Interesting Fetchmail Foible
I have been having network problems lately. Comes up for a second, then dies, repeatedly. So I get the same emails, over and over again. Fetchmail can apparently get them but not tell the provider that they have been received so delete them on their server. Until the network is up properly, I must shut down fetchmail. Would there be any script, option, or such to solve this problem in a more elegant manner and leave things alone when the network is doing what it is supposed to do? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Interesting Fetchmail Foible
On Tue, 15 Jan 2008 20:44:10 +0200 David Baron [EMAIL PROTECTED] wrote: I have been having network problems lately. Comes up for a second, then dies, repeatedly. So I get the same emails, over and over again. Fetchmail can apparently get them but not tell the provider that they have been received so delete them on their server. Until the network is up properly, I must shut down fetchmail. Would there be any script, option, or such to solve this problem in a more elegant manner and leave things alone when the network is doing what it is supposed to do? What are the contents of your .fetchmailrc file? -- Raquel If you complain of neglect of Education in sons, what shall I say with regard to daughters, who every day experience the want of it? --Abigail Adams -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Interesting Fetchmail Foible
On Tue, Jan 15, 2008 at 08:44:10PM +0200, David Baron wrote: I have been having network problems lately. Comes up for a second, then dies, repeatedly. So I get the same emails, over and over again. Fetchmail can apparently get them but not tell the provider that they have been received so delete them on their server. Until the network is up properly, I must shut down fetchmail. Would there be any script, option, or such to solve this problem in a more elegant manner and leave things alone when the network is doing what it is supposed to do? Not elegant, but can you get at your email at your ISP's web site using your browser and delete it there? -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Interesting Fetchmail Foible
Quoth David Baron: I have been having network problems lately. Comes up for a second, then dies, repeatedly. So I get the same emails, over and over again. Fetchmail can apparently get them but not tell the provider that they have been received so delete them on their server. Until the network is up properly, I must shut down fetchmail. Would there be any script, option, or such to solve this problem in a more elegant manner and leave things alone when the network is doing what it is supposed to do? Depends. Are you using procmail, too? If so, you might be interested in the following rule I have in my .procmailrc: # Dupes? Nuke'em! :0 Wh: msgid.lock | $FORMAIL -D 8192 msgid.cache That's it. All there is to it. Just put that little beast in and all duplicate massages will get deleted. (there is something similar for maildrop, too. Just in case you use it - but I forgot, just what it was... GIYF ;-) ). Aleks signature.asc Description: Digital signature
