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
"Ahern, Shannon" <[log in to unmask]>
Wed, 27 Mar 2002 12:41:33 -0800
text/plain (104 lines)
Thanks!

A is preferred, but I think we are looking at B.

Thank you!

Shannon

-----Original Message-----
From: Good, Donald [mailto:[log in to unmask]]
Sent: Wednesday, March 27, 2002 12:22 PM
To: [log in to unmask]
Subject: Re: Some technical help with outgoing listmail, please? (sent
to listowners and siteowners lists)


Are you saying that (A) you want to install LSMTP on the Listserv box or are
you saying that (B) the Listserv box already has an SMTP service and you
want it to handle Listserv delivery?

Obviously, (A) is the recommended approach.  To switch the Listserv delivery
from Exchange to another SMTP service, change the SMTP_FORWARD parameter in
the Listserv config file to point to the new SMTP server.  See
http://www.lsoft.com/manuals/1.8d/sitemgr/appendc.html

Allow the new SMTP server deliver directly to destination mail systems
rather than forwarding everything throught Exchange.

If your company has a firewall, you will probably need to make some rule
changes similar to those in place for your Exchange server.


-----Original Message-----
From: Ahern, Shannon [mailto:[log in to unmask]]
Sent: Tuesday, March 26, 2002 12:53 PM
To: [log in to unmask]
Subject: Some technical help with outgoing listmail, please? (sent to
listowners and siteowners lists)


Hi all-

We have been having a terrible time with relaying outgoing mail via our
Exchange server. At digest-time, due to the volume of our lists, we often
crash our mail server completely.

About a year ago, we were going to use the L-SMTP program, and I think our
IT group even bought it, but then never implemented it.

So we have had outgoing listmail relaying via our Exchange server for a long
time. But this is bad, not only because of the crashing, but also because we
cannot keep diagnostic logging on as it fills too quickly because of all the
listmail. So, when a user has a genuine mail problem, we really cannot see
what is going on.

We want to make the smtp on the box that actually has Listserv on it handle
the outgoing mail. Now, I am in NO WAY a mail admin - I can't read a header
to save my life. But I am the Listserv admin, and I am trying to work
together with IT to solve this problem.

IT suggested I ask "The List" (you folks) for input, and they put together a
little description of what is going on now. They are thinking that turning
off "forwarding" might make Listserv automatically use the local smtp, but
we don't want to inadvertently bring down all our lists if we are wrong.
:-)

Any help would be most appreciated!

Shannon  :-)



<description>
Let me give you an idea of our setup so you can describe it to them.

The listserv machine receives messages directly from the internet (messages
DO NOT come in through our mail server).

Once the listserv does its listserv thingy and wants to send out a message
it is set up to "forward" to our mail server.

From there, once our mail server receives the messages, it knows what to do
and starts sending out the messages.

Now, what we WANT to have happen after we make the change is the listserv no
longer forwards messages to our mail server to be sent out.

Just like the listserv receives messages directly, we want it to send out
messages directly.

Hopefully it is just as easy as turning off "forwarding" but I cannot tell
from the documentation. It does not really go into depth about how exactly
the process works from when the listserv receives messages to when it sends
them out.
</description>


~~~~~~~~~~~~~~~~~~~~~~~~~~~
Shannon Ahern
DevelopMentor WebMistress
310-543-1716
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It is our light, not our darkness, that most frightens us.  -Nelson Mandela

ATOM RSS1 RSS2