[Mailman-Users] using mailman on a server other than the one that DNS is pointing to

[Adam Parker, OD]

no, i'm not actually using that domain.  Cpanel allows you to easily set up
a list - it just asks you for the name of the list and a password and does
the rest for you.  The problem is that the server the Mailman/List resides
on is not the server that houses the email server.  So i'm looking for a way
for the 2nd server to be able to monitor the emails from the email server.
I went into the panel and there's a place to alter the MX record - one
option is for "Remote Mail Exchanger" which I thought would work, but it
doesn't.  I'm not sure this is possible, but was hoping there'd be a way to
use Mailman when the emails are not on same server.
-Adam

On Tue, Jun 15, 2010 at 10:30 AM, Adam McGreggor
<adam-mailman at amyl.org.uk>wrote:

> On Mon, Jun 14, 2010 at 07:16:26PM -0400, Adam Parker, OD wrote:
> > I have a website abc123.com and it's hosted on Host A.  Host A does not
> > allow Mailman on cpanel.  Host B does.  I set up a list called "
> > bot at abc123.com" on Host B while also setting up abc123.com as an addon
> > domain.  Is there any way to make this work?
>
> Firstly, where you're using "abc123.com", I presume you don't actually
> mean "abc123.com"[1].
>
> Secondly, I know *nothing* about what cPanel offers, let alone how
> they've re-modified Mailman -- apart from what I've read in previous
> posts (and there are a few).
>
> Using a different name on "Host B" (differing to "Host A")
> might alllow, for say, <list-foo at hostb.example.com> something like
>
>    (a) ProxyPass and ProxyPassReverse /mailman/ (and /pipermail) to hostb
>
>    (b) forward the mails for the mailman parts (e.g,
>
>  <list-foo{admin,bounces,confirm,join,leave,owner,request,subscribe,
> unsubscribe}@example.com <unsubscribe%7D at example.com>>
>        ->
>
>  <list-foo{admin,bounces,confirm,join,leave,owner,request,subscribe,
> unsubscribe}@hostb.example.com <unsubscribe%7D at hostb.example.com>>)
>        to hostb
>
> in your scenario.
>
> It would almost certainly be easier/less hassle, to use a separate
> name for hostb (e.g., make hostb "lists.example.org", and then just
> use normal look-ups to point your lists (mail and web) to hostb),
> with all the Mailman stuff taking place on hostb
>
> [1] that is to say:
>    Domain Name: ABC123.COM
>    Registrar: TIERRANET INC. D/B/A DOMAINDISCOVER
>    Whois Server: whois.domaindiscover.com
>    Referral URL: http://www.domaindiscover.com
>    Name Server: NS1.DOMAINDISCOVER.COM
>    Name Server: NS2.DOMAINDISCOVER.COM
>    Status: clientTransferProhibited
>    Updated Date: 19-aug-2009
>    Creation Date: 19-aug-1995
>    Expiration Date: 18-aug-2010
>
>    >>> Last update of whois database: Tue, 15 Jun 2010 14:25:35 UTC <<<
>
> --
> ``Whether intentionally or not, fish control and potato control were
> billeted
>  together in St. John's College, Oxford, making this ancient seat of higher
>  learning the biggest fish and chip shop the world has ever seen.''
>  (Peter Hennessey, on the organisation of wartime rationing)
>



-- 
Adam P. Parker, OD, FVAO
Drs. Robinson & Parker
President, Richmond Optometric Society
(804) 595-2020