On Tue, May 07, 2002 at 11:33:32AM +0200, Jan Klaverstijn wrote:
[ ... ]
The are many reasons that someone would want this and not
'workarounds' all are possible outside the scope of fetchmail. I
for instance keep my mail a while on my ISP just so I can read it
during the day with webmail when at a customer's site.
Well, I'm very glad to see that someone beside myself also would
like this feature, and for a reason that's similar to mine.
As fetchmail keeps track of the UIDL's of the messages it has
downloaded before but are still on the server, any tool you write
has to read that list (it's in .fetchmailids). Also .fetchmailrc
has to be parsed for account information. So there is a tight link
between fetchmail and the functionality you're looking for. I
wrote a perl thingy run by cron every night that does just that
(available on request), but is limited to POP3 servers. I found
frequent malformed timestamps in the headers to be a challenge. Of
only the download date was recorded in .fetchmailids.
Well, it should be easy to add the download date to .fetchmailids,
or at worst case (possibly to preserve backward compatibility), to
store this date in another file.
In short, it would be great to have a syntax like keep=n with n in
eg. hours/days instead of plain keep. Unlike some other requests
it is imho true to the nature of fetchmail.
Yes, I totally agree.
If there are no takers I will consider writing a patch myself. But
my C is not what it used to be.
Well, my C is good, so how about if I attempt the patch? I can
spend an hour or so a day on it, so perhaps I'll have something to
submit in a week or so.
Jan Klaverstijn.
[ ... ]
--
Fetchmail User
fmail(_at_)asfast(_dot_)net