Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Bad Email Addresses in Listserv Spool
From:
Michael Shannon <[log in to unmask]>
Reply To:
LISTSERV site administrators' forum <[log in to unmask]>
Date:
Tue, 2 Mar 2004 16:43:19 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (67 lines)
>Our organization recently created a list off all the subscribers to our
>other lists to push a new product. The problem is that some of these lists
>had not received traffic in a few years, and to make a long story short,
>there are a number of bad email addresses in this list.
>
>When we sent out a push to this list of 6000+, many of the .job files were
>stuck in the spool. Is there any way to tell Listserv not to check if an
>address is valid and so to just process the .job files and send error
>reports to the list admin?

A piling up of .JOB files indicates a problem with your SMTP gateway that
handles LISTSERV's outgoing mail.  You would be best to investigate what's
happening there, first, before looking anywhere else.

Having said that, validating addresses before sending is not the
responsibility of LISTSERV.  It will faithfully attempt to send to whatever
addresses you feed it.  In the same vein, your SMTP gateway will also
faithfully attempt to send to an address but it'll eventually stop if it
receives a vaild bounce or the message reaches the maximum queue expiry
limit.

Yous still need to find out why the .JOB files are still in the queue,
first.

>And is there a script anyone knows about or a
>third party product that goes through a listserv spool directory and
>removes
>bad email addresses based on a domain not found error or other criteria.
>With 6000+ subscribers, manually removing all the bad address so the
emails
>can go out is an impossible task.
>

This can't be done *before* a job is processed as there's no way of telling
if an address is bad until it's been sent to and an error generated.
You'll only find out if addresses are bad after the fact.

Check out the Autodelete= keyword in Appendix B of the LISTSERV Site
Maintainers Manual or online at
<http://www.lsoft.com/manuals/1.8e/sitemgr/listkeyw.html#kAutoDelete>.  For
a one-way list you could be really strict and code something like this:

Auto-Delete= Yes,Full-Auto,Delay(0),Max(0)

This will automatically delete someone on the first offence, no questions
asked, no discussions entered into, do not pass Go - do not collect $200.
:)

Setting Delay(0),Max(0) means you won't get a daily error report, though,
which will list everyone who's been deleted.  You need to at least have
Delay(1),Max(1) for this.

>Thanks,
>Greg



--
Regards,
 Michael Shannon
 Senior Consultant, Asia Pacific Region           [log in to unmask]
 L-Soft international, Inc.                     http://www.lsoft.com

 Chazzozz!!

 LISTSERV (R) is a registered trademark of L-Soft.

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV