-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 8 Feb 00, at 15:22, Jason Haar wrote:
> I've got Qmail on a DMZ host. No percenthack, good rcpthosts file/etc.
> Relaying of the form "user@remote" to "user@remote2" fails as
> expected. Mail from "user@remote" to "user@[EMAIL PROTECTED]" is
> accepted and passed onto our internal LAN Qmail server.
Why not? I mean, this address should mean "local user
user@remote2 at our.domain". Unless something is terribly
misconfigures, user@remote2 is a local username, not a remote
user at remote2 machine.
> Now the DMZ
> host is on a different subnet than our LAN - so the LAN Qmail server
> thinks the incoming SMTP session is from a foreigner - but it still
> accepts it...
OK, so it accepts it. Does it bounce it, or does it deliver it?
> If I connect from the DMZ host to the interal LAN Qmail server and
> attempt a manual "user@remote" to "user@remote2" - that fails with the
> "no relaying" error. However "user@[EMAIL PROTECTED]" is accepted and
> past onto the appropriate smtproute rule. End result, relaying does
> occur...
Does it really occur? If yes, we need to see how exactly you pass
the message from DMZ to LAN. Normal smtproutes forwarding
does not change the RCPT TO: address, ie. the local LAN server
still sees "user@[EMAIL PROTECTED]" and bounces it back
claiming "no such local mailbox user@remote2". Does that not
happen?
> Why does Qmail treat xxx@sss@ttt addresses differently than it treats
> xxx@sss addresses when it comes to relaying checks?
It does not.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBOJ/oDFMwP8g7qbw/EQKk+wCg4L8VHjBvBnP84gtGaY+T+ehWzY0AoM6u
LIi9vW1HbV2Hr4YWcG94L34P
=VGgB
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
