I apologize for this being offtopic, but as the author of getmail, I can't let the following misinformation go uncorrected.
Charles Jie <[EMAIL PROTECTED]> wrote: > > 1. My getmail.log gives: > > Aborting... (command "/usr/bin/maildrop ~/.maildroprc" returned 19200 > (maildrop: signal 0x06)) Maildrop is dying because it's receiving signal #6. Not getmail's fault. > 2. My maildrop now looks OK and saves message to given mbox. The problem > is that getmail doesn't remove message in POP server. I'll get a copy > of the same message each time I run getmail. getmail refuses to delete the message because the local delivery failed. The alternative is to risk losing mail, and I won't let that happen. > 3. getmail also fails to fetch mail if the destination mbox doesn't > exist. Thus I can not let mutt remove the empty mbox file when all > messages are deleted. [...] > 6. Futher, getmail doesn't mention the restriction of point 3. Sure it does. It's answered in the FAQ, under "I've configured getmail to deliver to my mbox file, but it won't do it. Why?". > 7. It takes no hard work to prepare man page but it's a big convenience. Fine. You do the work, then. I already write the documentation in another format. > thanks, (and sorry to post getmail's question here. I regard such filter > function as a part of Using Mutt.) Don't send getmail questions to the mutt list, please. It's offtopic and annoys everyone. getmail has its own mailing list, mentioned several times in the documentation. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ -----------------------------------------------------------------------
