At 2:19 PM -0400 6/4/01, Homer Wilson Smith wrote:
> However we are running qpopper 2.52 and procmail 1.13.1 both
> of which I understand are old.
I'm sorry, but you're simply *begging* for spool corruption with
this combination.
>
> I been thinking of how to kludge this with a monitor on the popper
> log files, it sees the "can't read from lines" message and goes and fixes
> the mail file itself as best it can.
Why not just upgrade and fix the problems? Why spend time and
effort on a kludge that will itself need to be debugged?
>
> I know I should upgrade to 4.03, but the number of bugs
> being reported here is scary. This is a production system and
> we need mail to work perfectly. :)
It's because you want mail to work that you need to upgrade. And
right away. You're running versions of Qpopper and procmail with
known bugs and incompatibilities, you're experiencing the spool
corruption that can be expected when doing so, and you're afraid to
upgrade?
> No insult at all intended,
No insult intended to you either. I understand people who hesitate
to upgrade. I understand the devil you know versus the one you
don't, I understand a fear of the unknown, but frankly, I don't
understand how you would want to continue living with spool
corruption. In my opinion, that's about the worst problem you can
have. Even a crashing server is not as bad, as I see it, because
then at least the mail is still there. But with spool corruption
it's gone. Bye-bye.
> I LOVE popper and procmail and linux and everyone who has helped
> bring all this about, I am but a worm in the scheme of things. But
> my customers none the less hate mail problems.
If they hate problems, you really need to upgrade.
> Since this is the
> ONLY problem we are having, I would rather kludge a fix rather than
> upgrade to a whole new unknown bad of tricks.
That might make sense if your current problem was, say, some
clients weren't showing a progress bar during message downloads.
But your problem is spool corruption. That's as bad as it gets.
