LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

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

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

Print Reply
"Patrick B. O'Brien" <[log in to unmask]>
Wed, 10 Dec 2003 07:12:11 -0800
text/plain (82 lines)
That is what I am suggesting. Your listserv_home/home/*.autodel file
should tell you more of why these emails did not go. 



-----Original Message-----
From: Cesar Sosa [mailto:[log in to unmask]]
Sent: Wednesday, December 10, 2003 6:21 AM
To: [log in to unmask]
Subject: Re: LISTSERV

Are you suggesting that those 100 names in the SPOOL files are getting
stuck there because of SPAM software?  Do I have to notify each of those
names about unblocking LISTSERV so they can get the mail?  Thanks for
your
assistance.








                      "Patrick B. O'Brien"
                      <[log in to unmask]         To:
[log in to unmask]
                      >                            cc:
                      Sent by: "LISTSERV           Subject: Re: LISTSERV
                      site administrators'
                      forum"
                      <[log in to unmask]
                      .LSOFT.COM>


                      12/09/2003 07:46 PM
                      Please respond to
                      "LISTSERV site
                      administrators'
                      forum"






Me too!

From what I understand, you have to notify the Admin of that particular
email server and tell them to let your stuff through!

Make sure your not Blacklisted!




-----Original Message-----
From: Cesar Sosa [mailto:[log in to unmask]]
Sent: Tuesday, December 09, 2003 1:03 PM
To: [log in to unmask]
Subject: LISTSERV

I am running LISTSERV 1.8e and using SENDMAIL on an Unix machine.  My
problem is that some of my mail files are getting stuck in the spool.
For
every message we send with approximately 2500 names listed, we lose two
files containing about 50 names each.  Consequently, about 100 people
are
not getting the required information in a timely manner.    Has anyone
seen
something similar and have any recommendations?  Can we make changes to
the
LISTSERV
optimization files to correct this problem?

Thanks for you assistance.




C. S.

ATOM RSS1 RSS2