maildrop logging overwriting instead of appending
Ok, I finally took the plunge today and converted my .procmailrc into a .mailfilter, adjusted my .forward file, and am now, for the most part, a contented new maildrop user. :-) Just one problem: on each invocation of maildrop, the logfile is being overwritten, rather than appended to. I have the following in my .mailfilter file (this is outside of any specific filtering rule): logfile Mail/maildrop.log I can't see anything else anywhere in the maildrop docs that might affect the way the logfile is handled. According to the manpage, if the logfile already exists, it should be appended to, but this isn't what's happening. Clues, anyone? -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: maildrop logging overwriting instead of appending
On Fri, 30 Sep 2011, Conrad J. Sabatier wrote: Ok, I finally took the plunge today and converted my .procmailrc into a .mailfilter, adjusted my .forward file, and am now, for the most part, a contented new maildrop user. :-) Just one problem: on each invocation of maildrop, the logfile is being overwritten, rather than appended to. I have the following in my .mailfilter file (this is outside of any specific filtering rule): logfile Mail/maildrop.log Maybe use an absolute path like ~/Mail/maildrop.log or $HOME/Mail/maildrop.log? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: maildrop logging overwriting instead of appending
On Fri, 30 Sep 2011 18:16:17 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: On Fri, 30 Sep 2011, Conrad J. Sabatier wrote: Ok, I finally took the plunge today and converted my .procmailrc into a .mailfilter, adjusted my .forward file, and am now, for the most part, a contented new maildrop user. :-) Just one problem: on each invocation of maildrop, the logfile is being overwritten, rather than appended to. I have the following in my .mailfilter file (this is outside of any specific filtering rule): logfile Mail/maildrop.log Maybe use an absolute path like ~/Mail/maildrop.log or $HOME/Mail/maildrop.log? Well, I'll try that. The Mail/maildrop.log *is* being written to, but I've only seen at most a single delivery noted in it each time I've looked. Kinda weird. Let me see if an absolute path will somehow make a difference... -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: maildrop logging overwriting instead of appending
On Fri, 30 Sep 2011 20:31:36 -0500
Conrad J. Sabatier conr...@cox.net wrote:
On Fri, 30 Sep 2011 18:16:17 -0600 (MDT)
Warren Block wbl...@wonkity.com wrote:
On Fri, 30 Sep 2011, Conrad J. Sabatier wrote:
Just one problem: on each invocation of maildrop, the logfile is
being overwritten, rather than appended to.
I have the following in my .mailfilter file (this is outside of
any specific filtering rule):
logfile Mail/maildrop.log
Maybe use an absolute path like ~/Mail/maildrop.log or
$HOME/Mail/maildrop.log?
Well, I'll try that. The Mail/maildrop.log *is* being written to, but
I've only seen at most a single delivery noted in it each time I've
looked. Kinda weird.
Let me correct that: I'm seeing the deliveries for a single instance of
maildrop only each time, not necessarily just a single delivery.
Let me see if an absolute path will somehow make a difference...
Well, that didn't have any effect. Just tried using:
logfile ${HOME}/Mail/maildrop.log
Same behavior. This is really odd. Maybe I'll try rebuilding/
reinstalling maildrop. May be some quirk related to having built it
under 9.0-BETA2 and then running it now under 9.0-BETA3? Who
knows? :-)
Anyway, like I just mentioned in #bsdports a few minutes ago, maildrop
is already working so well, I hardly even need any logging. But I'd
still like to clear up this mystery. I hate things like this! :-)
As an aside to anyone still hesitant to convert from procmail to
maildrop:
Fear not! It's a remarkably easy transition, and the .mailfilter
syntax is *so* much less arcane than procmail's. A real breath of
fresh air, if I do say so. :-)
--
Conrad J. Sabatier
conr...@cox.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: maildrop logging overwriting instead of appending
On Fri, 30 Sep 2011 20:48:39 -0500 Conrad J. Sabatier conr...@cox.net wrote: On Fri, 30 Sep 2011 20:31:36 -0500 Conrad J. Sabatier conr...@cox.net wrote: On Fri, 30 Sep 2011 18:16:17 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: On Fri, 30 Sep 2011, Conrad J. Sabatier wrote: Just one problem: on each invocation of maildrop, the logfile is being overwritten, rather than appended to. [snip] Doh! I just realized what was causing the log to be overwritten. When I was first setting up and testing my .mailfilter file, I put the following in my .forward file: |exec /usr/local/bin/maildrop 2Mail/maildrop.log || exit 75 Changing the redirection operator to , of course, solved the problem. Sheesh, I feel almost as dumb as the author(s) of Bumblebee. :-) Conrad, giving himself a well-deserved palm-whack on the forehead -- Conrad J. Sabatier conr...@cox.net|exec /usr/local/bin/maildrop 2Mail/maildrop.log || exit 75 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
