Thought I'd try my luck with your list. I didn't have much luck on the
majordomo-users's discussion group. Any information with respect to where
to place the Majordomo system with respect to your corporate systems and
domains would be appreciated.
-----Original Message-----
From: Gary Thandi [mailto:Gary.Thandi@360.net]
Sent: Friday, November 22, 2002 11:02 AM
To: 'majordomo-users@greatcircle.com'
Subject: Majordomo architecture question
Hi,
I am a Majordomo newbie. Seems like a great product and the actual setup of
it is a breeze. What I haven't been able to find is information on the
actual server setup with respect to it's place as a networked device.
We have an email content scanner for all corporate mail on the Internet.
This content scanner securely routes mail to our internal system by the
domain name.
My questions are:
1. Should you create a separate DNS sub domain for the Majordomo box ie.
<list name>@lists.360.net? In this case, I would need a separate MX record
for that new sub domain pointing to the Majordomo box.
OR
2. Should this system be a pier to the email content scanner, which would
allow it to send email directly out to the Internet? I would set up
Majordomo so that only an authorized user can send outbound messages to the
subscription list.
Can anyone point me in the right direction of Majordomo best practices at
the architecture level?
Thanks in advance.
Gary.
|
|
