🚀 go-pugleaf

James R Grinter <jrg@blodwen.demon.co.uk> wrote in message
news:x7itwe5a0z.fsf@indy1.watching.org...

> Some musings..
>
> "Simon Child" <simon.child@nospam.demon.co.uk> writes:
> > My domain is w-c-f.org.uk, so probably I shall name my linux box as
> > w-c-f.org.uk and others on my lan as subdomains e.g.
simon.w-c-f.org.uk
> > (Or maybe the linux box should be somename.w-c-f.org.uk - I've just
>
> You could do this - but the existence of external DNS, unless you want
> to (are able to) list your internal hosts in that external DNS, might
> complicate things for you.

Hmm, good point. This is the sort of reason for my asking before I
leap...

> [I've genericised @w-c-f.org.uk to @your-domain in the following,
> strangely easier to type]

Of course I would have preferred wcf.org.uk but it had already gone :-(

> As I see it, there are two options for the mail:

> 1. Configure your system(s) to send out mail as @your-domain, (which
> doesn't necessarily mean that you have to receive mail locally as
> that. I'm not familiar with the clicknames nee gradwell.com service
> and so don't know if they offer you a POP3 mailbox to pick it up from,
> or whether they rewrite to another address/es of your asking?)

The latter, so in fact I'm not receiving mail as w-c-f.org.uk anyway...

> 2. Use mail aliases matching those you've deployed on the external
> mail-handling system so that you route @your-domain mail the same way
> as they would do, and accept anything else @your-domain for local
> delivery.

..so this doesn't apply

> and two seperate options for the hosts:
>
> A. Rename your hosts, run an internal DNS with the internal names, but
> containing identical host entries for those in the external DNS. You
> don't have to have a machine called 'your-domain', in fact for simple
> clarity/sanity reasons it's probably better that you don't.

Probably just using the hosts file would be enough, wouldn't it?

> B. Don't rename your internal hosts. Hostnames have actually no
> bearing upon mail addresses (if think about it - Demon don't actually
> have to have a machine called 'child.demon.co.uk' available to receive
> your mail at present.)
>
> > 2) Similarly what about majordomo? Currently majordomo runs as
> > majordomo@child.demon.co.uk with maillist-L@child.demon.co.uk  OK,
I'll
> > have to tell the list members the new address. Presumably if I name
the
>
> > will pick up whatever name I give the linux box? I think so, and
perhaps
>
> I think each majordomo list will pick up the name you tell them to
> pick up (the default is probably that returned by 'hostname', but
> there is a $whereami value in majordomo.cf, for 1.9x). In Majordomo
> 1.9x that seems to be controllable with 'resend_host' in the list
> config file, although it is possible that the host MTA will override
> any such value later on... Your skills with the MTA might influence
> your choices here.

I had forgotten about majordomo.cf, which seems to solve all this.

> You could accept the old names, but send out with the new, and send
> all subscribers a note asking them to send to the new address (noting
> that it will go away at some point in the future, etc.) You could even
> set the old address to auto-respond directing the sender to the new
> list address at a point before you turn off/lose it entirely.

Yes I had thought of that

> (So many ways...)

.. to get it wrong ;-)

Thanks to both of you, I'm clearer now:

I think there's no real need to rename. It would be a little tidier,
e.g. Outlook Express, as well as stripping the trailing space off my sig
separator :-(( gives email message id's of xyz@tower.localdomain instead
of 123@simon.w-c-f.org.uk, but it's only a nicety

Incoming and outgoing mail should work alright (indeed are doing already
as I haven't done any renaming)

A tinker with majodomo.cf and the associated aliases should sort out the
lists.

Might cause me dns work if I rename.

Cheers

--
Simon Child