|
I manage a nursing related listserve with about 700
subscribers over 100 emails daily. I'm assuming from "bounce mgmt"
that you mean handling error messages that come back from bad addresses,
full mailboxes, etc. It's not very graceful but I'll describe what I
did. I'm not sure if it would help anyone but I'd be happy to share my
code. I setup this process about a year ago and it's saved me a ton of
time managing bounced messages.
First I set the listserve owner to an
alias. The alias just splits the message to two
addresses. One address forwards to me and the other is a program
alias that calls cscript with a _vbscript_ file.
I setup a sql server database with three tables,
listserves, error_messages, and
addresses_dropped.
Listserve db has the following
fields:
id (key field)
list_name (varchar) name of
listserve
list_owner_email (varchar) email addy of list
owner
list_file_path (varchar) path to users.lst
file
error_threshold (int) number of errors allowed
before an address gets dropped
last_error (datetime) date of last
error
purge_interval (int) number of days to wait before
purging errors
last_purge (date) date last purge
performed
note (text) whatever
the error_messages table has following
fields:
id (int) key
field
message_from (varchar) message_to (varchar) message_subject (varchar) message_body (varchar) message_date (varchar) error_creator (varchar) error_count (int) creation_date (datetime) updated_date (datetime) note (varchar) addresses_dropped has following
fields:
id (int)
list_owner (varchar) error_subject (varchar) error_email (varchar) error_count (int) creation_date (datetime) updated_date (datetime) dropped_date (datetime) note (varchar) message_body (varchar) Essentially, all the code does is take an error
message and looks it up in the error_messages table. If the same
error, same address is already there, it increments the counter by
1. If the last time that address errored was greater than the
purge_interval and it's not reached the threshold, it discards the
error. If the threshold is reached and it's within the date range before
purging, it drops the email address from the users.lst file and adds the
record to the addresses_dropped table.
The last table really only serves a purpose of
reference. When people contact me asking why they stopped getting
messages, I have something to look up. It doesn't catch everything
but it manages to save me about 15 minutes every day. VB code is
attached.
If anyone uses this and improves on it, please
share with me.
Thanks!
-Gary
Gary Jorgenson,
RN President - Robin Technologies, Inc.
670 Lakeview Plaza Blvd., Suite J | Worthington, OH 43085 Phone: 614.888.3001 | Fax: 614.888.3002 | Cell: 614.657.8080 [EMAIL PROTECTED] | www.robintek.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doris McKay Sent: Friday, March 24, 2006 5:19 PM To: [email protected] Subject: Re: [IMail Forum] 2006 Listserver # 3 -
I can work around or live without all the rest, but
I really, really need bounce mgt.
Doris
Doris McKay, MS
LIS
Consultant/Webmaster Rolling Prairie Library System 345 W Eldorado Street Decatur, IL 62522 Phone: 217 429-2586 x115 Fax: 217 428-1852 [EMAIL PROTECTED] http://www.rpls.ws yeah Kevin Gillis wrote:
|
listmonitor.v_b_s
Description: Binary data
