Great Circle Associates Majordomo-Users
(June 1994)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: handle bounces automaticall?
From: "John P. Rouillard" <rouilj @ cs . umb . edu>
Date: Wed, 29 Jun 1994 10:38:48 -0400
To: Alan Millar <AMillar @ bolis . sf-bay . org>
Cc: reisert @ wrksys . enet . dec . com, majordomo-users @ greatcircle . com
In-reply-to: Your message of "Wed, 29 Jun 1994 02:37:05 -0800." <m0qIw4v-0002ZjC@hock.bolis.sf-bay.org>


In message <m0qIw4v-0002ZjC@hock.bolis.sf-bay.org>, Alan Millar
writes:
>And verily didst John P. Rouillard spake of these matters:
>> In message <9406282124.AA13848@us4rmc.pko.dec.com>, Jim Reisert --
>> MLO5-2/36A -- DTN 223-5747 28-Jun-1994 1724 writes:
>> >I have 1.92.  I'm using resend.  Is there a way to handle bounces
>> >automatically - i.e.  if a message bounces, have MajorDomo automatically
>> >move the address from the list to the bounces list? Or does it all have to
>> >be done by hand (i.e.  by sending a BOUNCE command to MajorDomo)?
>> 
>> The short answer is no, sorry. 
>> 
>> (Standing out on limb) I claim there will never be a program invented
>> that can decipher the crap that some mailers pass back as a bounced
>> message. 
>
>Well, John, the timing is absolutely perfect.  I'm pulling out my
>pruning saw...

Well, I did say I was going out on a limb 8-).

>Announcing the Majordomo AutoBounce program!
>
>Believe it or not,

Comming from you Alan, I believe it, and I'll bet it works too.

>If you can codify these parameters for a few common mailers, and check
>the bounced message against them, you can pick out the address from
>the message.  Double-check the address to make sure it is a list
>member, and if it is, bounce it!

Interesting idea. As long as you can find an actual error line for the
mailer and differentiate it from informational messages with addresses
(such as those generated by deliver/procmail scripts etc) it seems
workable. The one thing that the program has to have is a very low
(non-existent) false positive rate (i.e. it unsubscribes somebody who
wasn't bouncing mail). Should I consider adding a flag to bounces to
"unbounce" somebody just in case the autobounce program gets too
enthusiastic?

>the list.  Note that there is a separate listname-autobounce alias
>for each list which passes the list name to the autobounce program.
>That way the scope of possibilities is much narrower, and we are
>more likely to get good results because we can check to make sure
>what we think is the bouncing address really is a list member.

One thing I would suggest is looking for an X-listname header or some
such as a sanity check on determining the list name. This would allow
it to be run from a .forward file for instance.

>After all that, a message is mailed to Majordomo with the unsubscribe
>command for the list and a subscribe command for the bounces list.
>You can specify any list name for the bounces list, in case you want
>to have separate ones or whatever.  Or you can tell it just to unsub
>but not add to any bounces list.

Nice touch.

>My production system is still running 1.62, so that's all I've tested
>it on.  I'm upgrading to 1.92 this week, so I'll post the program
>here after I've checked it out on 1.92 next week.

Cool. Probably the only change you will need is to require
config_parse.pl, and load the config file and use
%config_opts{$listname,'admin_passwd'} in place of the password from
the listname.passwd file.

You might also want to make configuration options for:

	enabling/disabiling the autobounce program
		(autobounce = yes/no)
	the name of the bounces list, or "none"
		(bouncelist = <word>)

If you want, I can do the config options before you release autobounce.

>One thing the program needs is a good way of specifying the bounce 
>message profiles so they can be easily added to.  Right now it
>looks like this:
> [...]
>I'd like an easy way to specify this outside of the code, so
>bounce profiles can be added without modifying the program
>file itself for safety's sake.  Any suggestions?

Well, since autobounce will exist in the majordomo installation area,
I can think of two things:

	Have them in the majordomo.cf with the other parameters
	and just require majordomo.cf (which I guess you already do)
	otherwise you couldn't find the list directory.

	Put them in a file called autobounce_pat.pl (or whatever), and
	just require it.

				-- John
John Rouillard

Senior Systems Consultant (SERL Project) University of Massachusetts at Boston
rouilj@cs.umb.edu (preferred)            Boston, MA, (617) 287-6480
==============================================================================
My employers don't acknowledge my existence much less my opinions.


Follow-Ups:
References:
Indexed By Date Previous: Re: handle bounces automaticall?
From: mmorse@nsf.gov (Michael H. Morse)
Next: Help in change sender address
From: pzee@express.com (Philip J. Zee)
Indexed By Thread Previous: Re: handle bounces automaticall?
From: Alan Millar <amillar@bolis.sf-bay.org>
Next: Re: handle bounces automaticall?
From: Alan Millar <amillar@bolis.sf-bay.org>

Google
 
Search Internet Search www.greatcircle.com