The logs show the messages getting to listserv.
The mail gets sent to the owner because of an error. The list owner and
the listserv administrator is notified of the error. The members of the
list never receive the mail content but the list owner does by default.
I can take that content, put it in a mail message from a regular mail
account not going through the application and the mail message gets
delivered to all in the list successfully. I'm convinced that the
application is putting in a wild character in the header but I cannot
prove it. That is why I wanted to setup a trace from listserv.
Does anyone know how to setup a trace in listserv. I cannot do it as the
sender because it is from the application.
This all worked two weeks ago and everyone claims nothing has changed.
We have all herd that one before.
Listserver gets the following error:
The enclosed message has been identified as a delivery error for the
SW-CONNECTION list because it was sent to
[log in to unmask]
------------------------------ Message in error
-------------------------------
Received: from s-listserv.thomsonlearning.com
(s-listserv.thomsonlearning.com
[198.80.146.63])
by s-listserv.thomsonlearning.com (8.11.6/8.11.6) with ESMTP id
j7CF59232447
for <[log in to unmask]>; Fri,
12 Aug 2005
11:05:09 -0400
Date: Fri, 12 Aug 2005 11:05:09 -0400
From: "L-Soft list server at S-LISTSERV.THOMSONLEARNING.COM (1.8e)"
<[log in to unmask]>
Subject: Your message to
[log in to unmask]
To: [log in to unmask]
Message-ID: <[log in to unmask]>
X-LSV-ListID: SW-CONNECTION
Fri, 12 Aug 2005 11:05:09
Your message to [log in to unmask]
has
been forwarded to the "list owners" (the people who manage
the
SW-CONNECTION list). If you wanted to reach a human being, you used
the correct procedure and you can ignore the remainder of this
message. If you were trying to send a command for the computer to
execute, please read on.
The SW-CONNECTION list is managed by a LISTSERV server. LISTSERV
commands
should always be sent to the "LISTSERV" address,
ie
[log in to unmask] LISTSERV never tries to
process messages sent to the SW-CONNECTION-request address; it simply
forwards them to a human being, and acknowledges receipt with the
present message.
The "listname-request" convention originated on the Internet a long
time ago. At the time, lists were always managed manually, and this
address was defined as an alias for the person(s) in charge of the
mailing list.
You would write to the "listname-request" address to ask for
information about the list, ask to be added to the list, make
suggestions about the contents and policy, etc. Because this address
was always a human being, people knew and expected to be talking to
a human being, not to a computer. Unfortunately, some recent list
management packages screen incoming messages to the
"listname-request" address and attempt to determine whether they are
requests to join or leave the list. They look for words such as
"subscribe," "add," "leave," "off," and so on. If they decide your
message is a request to join or leave the list, they update the list
automatically; otherwise, they forward the message to the list owners.
Naturally, this means that if you write to the list owners about
someone else's unsuccessful attempts to leave the list, you stand
good chances of being automatically removed from the list, whereas
the list owners will never receive your message. No one really benefits
from this.
There is no reliable mechanism to contact a human being for
assistance, and you can never be sure whether your request will be
interpreted as a command or as a message to the list owners. This is why
LISTSERV uses two separate addresses, one for the people in charge of
the list and one for the computer that runs it. This way you always
know what will happen, especially if you are writing in a language
other than English.
In any case, if your message was a LISTSERV command, you should
now resend it to [log in to unmask] The list
owners know that you have received this message and may assume that
you will resend the command on your own. You will find instructions
for the most common administrative requests below.
*********************
* TO LEAVE THE LIST *
*********************
Write to [log in to unmask] and, in the text of
your message (not the subject line), write: SIGNOFF SW-CONNECTION
********************
* TO JOIN THE LIST *
********************
Write to [log in to unmask] and, in the text of
your message (not the subject line), write: SUBSCRIBE SW-CONNECTION
************************
* FOR MORE INFORMATION *
************************
Write to [log in to unmask] and, in the text of
your message (not the subject line), write: "HELP" or "INFO"
(without the quotes). HELP will give you a short help message and INFO
a list of the documents you can order.
John Hiler
513-229-1131 Work
513-325-7572 Cell
-----Original Message-----
From: LISTSERV site administrators' forum
[mailto:[log in to unmask]] On Behalf Of Stan Horwitz
Sent: Friday, August 12, 2005 12:07 PM
To: [log in to unmask]
Subject: Re: list issue
On Aug 12, 2005, at 10:44 AM, Hiler, John wrote:
> I have a list that use to work fine from an application a couple of
> weeks ago. Now only the owner receives mail from the application.
> I can send a simple email to the list from an outside email account
> and from an inside Exchange email account.
> Is there a way I can trace what is being sent to the list as the owner
> when mail is sent from the application?
> I know there is the trace command that a user can use but I cannot get
> the application to set this.
John, are you able to access your Listserv's log files, or can you reach
those who can get to the log files?
The same question applies to the log files on the mail server that
handles the outbound email for the application you are working with. The
log files are a good resource to check in troubleshooting this issue.
In fact, if this situation confronted me, I would look at the mail
server's log file first, or have the person who is responsible for that
server look. You need to verify if the mail is actually being routed to
Listserv.
Your Listserv may not be getting the email, but the logs will show the
full picture, so before you spend much more time troubleshooting this
from a Listserv perspective, verify that Listserv is actually receiving
the missing email.
|
