i'm not positive what you had to program but it sounds like you could use
an mta that supports in-bound wildcards. then you could set the bounce
address, from line and reply-to line to a user specific address and process
them with a single (or worst case one per list) return address and a few
lines of your favorite scripting language.
if you had a clever mlm (say listserv) you could teach it to schedule an
in-band probe (qlist, the predecessor of ezmlm, does this with every
message) every N days or after K bounces.
>>>>> "Chuq" == Chuq Von Rospach <chuqui@plaidworks.com> writes:
Chuq> I didn't have list information in there because of the sheer
Chuq> number of lists and the complexity of trying to build a unique
Chuq> set of addresses for the site and tying list names to them. More
Chuq> programming hassle than I wanted to do this round.
--
paul
pjg(at)acsu.Buffalo.EDU |public keys at:
| http://urth.acsu.Buffalo.EDU/~pjg/key.html
if the above contains opinions they are mine unless marked otherwise.
References:
|
|
