Your problem is not actually a majordomo problem, but an MTA/DNS
problem. Some MTAs require reverse DNS resolution as an attempt
to fight spam and prevent mail relay theft.
When you send mail from your server(s) to the internet, are you
delivering through a smarthost, or using NAT to translate your
non-routable private net into a real, routable IP?
Do you maintain your own DNS? If so, you never want to expose your
internal non-routable IPs to the outside world (internet). Just imagine
if I also use 10.10.x.x on my (personal|company) network, and after
my MTA looks up your domain it finds one of my 10.10.x.x IPs as the
MX record for delivery. Now you see why this is a bad idea.
Dan Liston
jmail@delpro.com wrote:
>
> Ok, majordomo works great. Buy I'm having a problem, and am not sure
> what it is.
>
> I have it setup on foobar.com, and everything works great from the
> internet. The problem is when I send a message from the intranet
> (dec2.lns.foobar.com) It actually works fine, and majordomo sends out
> the message just fine. However, one of my clients mail server refuses
> the email because it is trying to resolve the domain name
> dec2.lns.foobar.com, which isn't registered on the internet (it is at ip
> 10.10.1.34)
>
> I'm sorry that I probably don't have enough information here, but I feel
> like I could go on describing things for another couple of pages and not
> hit on the relevent information.
>
> Thanks,
> Paul
Follow-Ups:
References:
|
|
