Content-Transfer-Encoding: |
quoted-printable |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Wed, 23 Jul 2003 12:07:25 -0600 |
Content-Type: |
text/plain; charset="iso-8859-1" |
MIME-Version: |
1.0 |
Reply-To: |
|
Parts/Attachments: |
|
|
We had a similar instance happen when a list owner sent out an email to a list containing malformed SMTP addresses. What I have to do now & then is go into /var/spool/listserv and isolate the jobs and move them to /var/spool/listserv.oops. Of course you have to stop listserv, move the jobs out of the queue and then restart it.
Noel Siksai
A+, RHCE
Avaya Corporate Email and Directory
Email backbone, Mass mail, Mailing lists, POST Tier 2 Admin.
[log in to unmask]
248-746-5210 (v)
248-362-1618 (f)
248-321-5684 (cell)
248-591-8106 (pager)
[log in to unmask] (email to pager)
"Every society honors its live conformists and its dead troublemakers."-Mahatma Gandhi
-----Original Message-----
From: Ben Parker [mailto:[log in to unmask]]
Sent: Wednesday, July 23, 2003 1:37 PM
To: [log in to unmask]
Subject: Re: Runaway SMTPS Log File
On Wed, 23 Jul 2003 11:27:54 -0400, Dave <[log in to unmask]> wrote:
>23 Jul 2003 00:00:01 *** LSMTP extensions activated ***
>
>23 Jul 2003 00:00:01 -> XDFN="John Smith"
>
>23 Jul 2003 00:00:01 500 Syntax error, command unrecognized
>
>This has apparently been going on for months.
>
>It seems that someone might have sent a DISTRIBUTE job with a syntax
>error. Still, I don't see why it should lead to this behavior.
You have an old outgoing *.MAIL file in x:\LISTSERV\SPOOL that is malformed in
some way that is causing this. Stop LISTSERV and delete that file (or move it
out of the ~\SPOOL dir to somewhere else, then restart.
>I've searched the spool directories and took a look at LSMTP
It's not in LSMTP anywhere. It's in LISTSERV's ~\SPOOL trying
(unsuccessfully) to get out. Due to the malformation, it will never be
successful.
>but can't
>find any trace of this problem, nor can I figure out how to stop it. I
>don't know if it's related to the lost mail, but it's definitely a
>problem. Any help would be appreciated.
Yes, it could be responsible for the missing mail, but you would need to
examine the file (after you move it elsewhere) to see what recipients are
listed who did not get the mail.
|
|
|