>From FAQ 2.5:

Answer: The SMTP standard does not permit aliased hostnames,...

I'm trying to do something with DNS alias involved, but I think it should
still work.  If someone could just sanity check me here, I'd appreciate it.

The base:

I have a machine search.scansoft.com.  It is a web server, and has many
aliases (www, beta, etc. etc.).  I am installing mailing list services on
this web server.  As their use grows, we'll probably want to move them off,
so I'm setting the list server as 'list.scansoft.com' and have created an
alias in DNS pointing 'list.scansoft.com' to 'search.scansoft.com'.  Now, as
I understand it, that won't work, in and of itself, as per FAQ 2.5.  But
I've also requested an MX record pointing 'list.scansoft.com' to
'search.scansoft.com' (the A record for this machine) with an MX value of
10.

Currently, when I mail to this system through my qmail relays, I get:

<[EMAIL PROTECTED]>:
4.17.150.115 does not like recipient.
Remote host said: 553 sorry, that domain isn't in my list of allowed
rcpthosts (
#5.7.1)
Giving up on 4.17.150.115.

Is that because the MX record isn't working  yet, or is it because of
something more complicated?  Let me explain the rest of my mail setup.

Aside from this mail server, I have two mail relays (hunin.scansoft.com MX
10, and munin.scansoft.com MX 20) which accept mail for "scansoft.com".
They then pass it along to the actual mail store via smtproutes.  Is it
possible that, because they accept mail for "scansoft.com", they're not even
looking further for "list.scansoft.com"?  (4.17.150.115 above is
munin.scansoft.com, the outgoing mail relay).  Or will it start working as
soon as that MX record for list.scansoft.com gets installed on the DNS
servers?

Any thoughts you have on this are appreciated!

--
    gowen -- Greg Owen -- [EMAIL PROTECTED] -- [EMAIL PROTECTED]

    Please note my new [EMAIL PROTECTED] address which will
    become my default address in March, and which works now.

Reply via email to