Hmm, not sure.
Got an MX record for domain.com.
So I assume it works for sub.domain.com.
Mon Jun 30 2008 07:08:41 EDT from [EMAIL PROTECTED]
Subject: Re:sending from a sub domain needs auth.
Hmm, not sure.
Got an MX record for domain.com.
So I assume it works for sub.domain.com.
if you want sub.domain.com to receive mail on another Server, you need to add
an MX for it.
Mon Jun 30 2008 08:10:06 AM EDT from [EMAIL PROTECTED] (Uncensored)
Subject: Re:sending from a sub domain needs auth.
Got an MX record for domain.com.
So I assume it works for sub.domain.com.
if you want sub.domain.com to receive mail on another Server, you need to
add an MX for it.
Citadel, by design, prevents unauthorized relay, as an anti-spam
feature. Logging in is Citadel's way of providing authenticated SMTP.
What we probably need, in this case, is functionality to whitelist specific
IPs or IP ranges to allow unauthenticated relay, a la Postfix's
mynetworks variable
Hang on.
I think everyone keeps getting the wrong end of this.
I am NOT relaying.
I am simply DELIVERING direct and because the machine trying to deliver
is a
peer in the domain it needs to auth. I argue it shouldn't.
I'll recap again.
Hang on.
I think everyone keeps getting the wrong end of this.
I am NOT relaying.
I am simply DELIVERING direct and because the machine trying to
deliver is a
peer in the domain it needs to auth. I argue it shouldn't.
I take this back, for the moment.
What mail server software is www.domain.com running?
If it's Citadel, shouldn't it be using the normal Citadel protocols, rather
than SMTP, anyhow?
It is Citadel and its now getting roots mail to the main mail server by
sharing the Aide
