On Nov 3, 2004, at 4:47 PM, Troy Richard wrote:
So you would just install the mailman on the 2nd server and then just send
all the mail through the mail server. The only problem I'm seeing with
that is how do you get the incoming mail to the web server for mailman to
process?
Just set up a second webserver that only processes mailman and stick it on the mail server. It is the easiest... Or have a separate mail server that only handles lists and have mailman installed on that, which is what I do. It could even be a virtual machine type server if you have that capability (like a "jail" on FreeBSD)
Chad
Troy
At 3:44 PM -0600 2004-11-03, Troy Richard wrote:
Not sure if this can be done but that would be one way around it. Anyone have any ideas if this possible.
Another way to resolve this issue is to have Mailman dump all outgoing mail on another server (or set of servers). Mailman doesn't have to worry about developing large queues or anything, and the bulk of the work handling the mail messages is done by the downstream machines.
-- Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755
SAGE member since 1995. See <http://www.sage.org/> for more info.
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
