There have been discussions in the past on this list about how best to
filter bounces from non-deliverable mail. During the years I've been
running mailing lists I've picked out some patterns, and it would be
nice if I could implement a filter based on these patterns, but writing
an adequate parser if beyond my skills, and I wondered if anyone had
made some progress in this respect.
Basically the sorts of rules I am looking at are these;
If a message comes from the host that the mailbox no longer exists, the
address can be deleted.
If a message comes from an intermediate node that the host is
unreachable, then it is probably a temporary system problem.
If you get bounce messages from a dozen subscribers on the same network,
then it is almost certainly a system problem (the main exception being
end-of-term account cancellation at universities).
Does anyone have a way of parsing and sorting these messages
automatically? It is pretty easy to do visually, but it does add up to a
fair amount of time, and I would like to be able to cut down on the time
wastage.
--
Bill Silvert, Habitat Ecology Section, Bedford Institute of Oceanography,
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2, Tel. (902)426-1577
Follow-Ups:
|
|
