Hello, all:
Hopefully this is worthy of a post to the wonderful qmail mailing list.
I have a machine that is behind a transparent proxy/firewall. The
address space behind the firewall is a class C private (192.168.) and
the machine in question (call it "hotcube") has a bogus hostname
("hotcube").
The firewall is port-forwarding to some internal services. At the moment
SMTP is not forwarded internally, but it will be when the MX records are
modified.
I am running qmail on hotcube in addition to Oracle Application Server.
The box is to provide e-mail for an office of perhaps 20 employees, so
it won't be pushed very hard. It will provide full e-mail service for
two domains:
originaldomain.com
and
virtualdomain.com
Here is where the problem starts.
The hostname is bogus. I cannot assign the firewall's true FQDN of
external.originaldomain.com to hotcube because the firewall cannot
forward internal requests through its external interface, which is where
the DNS record of external.originaldomain.com is pointing. So, I have
made /var/qmail/control/me be the FQDN of the firewall and added an
entry to /etc/hosts like so:
192.168.0.102 hotcube external.originaldomain.com
and added all of
originaldomain.com
external.originaldomain.com
hotcube
to /var/qmail/control/locals and /var/qmail/control/rcpthosts.
Okay?
Here's what I can and cannot do:
I can send mail to the big bad world.
I can send mail to local users using their actual usernames.
I *cannot* send mail to local users using their aliases (defined in
/var/qmail/alias). Even though the domain name is correct, the mail ends
up in the queue and an examination of /var/log/maillog reveals that the
qmail-send's attempts to make an SMTP connection are failing. So what
gives?
Why would
[EMAIL PROTECTED]
work, but
[EMAIL PROTECTED]
not work? The alias exists (/var/qmail/alias/.qmail-aliasuser).
If you need any more information... I'm sure you'll let me know =)
Thanks,
Stephen Bosch
