Occasionally procbounce detects an excessive number of bounces and proceeds to unsubscribe the sender, not the bouncing address. Have looked at procbounce and rc.request, but I can't find how this can happen. I am using the default bounce parameters, using 3.13.1 in a Solaris environment with the public (not Sun) sendmail. Any ideas?
Del
D. L. Kimbler, Ph.D., P.E. Professor, Industrial Engineering Clemson University Voice: (864)656-5645 Fax: (864)656-0795
"Del Kimbler" kimbler@ces.clemson.edu writes:
Occasionally procbounce detects an excessive number of bounces and proceeds to unsubscribe the sender, not the bouncing address. Have looked at procbounce and rc.request, but I can't find how this can happen. I am using the default bounce parameters, using 3.13.1 in a Solaris environment with the public (not Sun) sendmail. Any ideas?
Upgrade to SmartList 3.15: when I checked, it appeared that most of the problems bounces were DSNs (Delivery Status Notifications), so I taught procbounce how to parse DSNs. It'll only remove one address per bounce message, regardless of how many are reported, but at least it'll remove a problem recipient and not the sender.
Philip Guenther
smartlist@lists.rwth-aachen.de
-
Del Kimbler -
Philip Guenther