I recently had a similar problem where, without obvious reason, one day
mail for a single user started to get 'lost' or truncated. An
investigation revealed that an xfilter command that passed the messages
off to a spam filter also created a log file. Over time this particular
users log file became maxed out and hence the problems. Once the rather
large log file was deleted, operations returned to normal. Perhaps your
observation that this starts a couple of months after a new user is
created points to a similar problem.
Cheers,
Joe
Sam Varshavchik wrote:
darr...@accenture.com writes:
The problem:
It appears that maildrop truncates and drops messages a couple months
after a user account is active. Over the course of one day, messages of
There's absolutely no code in maildrop that would begin to drop
messages a couple of months after a new user account was created.
In fact, maildrop has absolutely no bloody idea when a particular
account was created. That information is simply not available to
maildrop.
[root@cent ~]# rpm -q maildrop
maildrop-1.7.0-1.3
That version of maildrop is over a year old. Even if -- highly
unlikely -- there turns up a problem in that version of maildrop,
after all these years,
nobody would really care about this code, any mode.
Nov 12 14:41:03 cent spamd[2318]: connection from
localhost.localdomain [127.0.0.1] at port 34694
So you have some kind of a spam filter, that you've somehow glued
together with maildrop.
This is the most likely source of your dropped and truncated mail.
There are no known issues in maildrop that would cause lost or
truncated mail. If you use the xfilter command (or an equivalent) to
send mail through an external mail filter, and it loses or corrupts
the mail, there's absolutely nothing that maildrop can do about it.
3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Maildrop Dropping and...
