Δαφνη Ευτυχια Αρθουρος

Sometime last night, the default action of the mail filter at my ISP was changed to screen the beagle virus. Unfortunately a small error introduced in the global configuration file causes most of my mail to not be delivered correctly. As far as I can tell I'm not actually losing mail, because of the idiosyncratic way I've got my forward/filter/download scripts set up (there's a backup copy as a side effect, eating disk space but coming in handy now), but seeing it in a timely manner and having access to it on a machine from which I can send replies are both affected. I've written to the helpdesk with clues, and if the error is in the line I think it's in, it should be an easy fix. But in the meantime expect me to be much less aware of what's being sent to me (and more likely to postpone responding when I do see it because of the extra steps required).

And if anyone knows how to tell Procmail not to read /etc/procmailrc (I didn't see a flag for that on the man page), please let me know.

[Edit @ 12:05 -- About 11:30 I started noticing mailing being delivered normally again, and took a little while to investigate and make sure that was in fact the case. The timestamp on the global rc file is 9:22, which would explain the few doubled messages I got before I noticed mail getting delivered without the new script I hacked up this morning. No answer to the message I sent to the support desk -- mine probably wasn't the first complaint and they might not have read it yet. *shrug* No matter; it appears to be repaired. **whew**]