I’m able to receive email, but, sending fails with “relaying denied IP name lookup failed [192.168.0.69].”
As you can see, I’m trying to send from a computer on the dmz part of the lan through the public facing server.
In any case, I don’t want Sendmail to make this check AT ALL regarding client ips. I want to base relaying strictly on user authentication, but this is trickier than I thought it would be - either that or I simply can’t find that one lucky checkbox!
Is there a convenient "click here to ignore client ips and relay any mail that comes from a valid user" button somewhere?
I’d be more than willing to use PostFix, in fact I tried shutting down the sendmail server then starting postfix. But, I always get an “unable to connect to server” from whatever client I try it with… so, seems like Sendmail may be the least problematic.
So, you’ve just described the default configuration in a Virtualmin system, if you used install.sh.
I don’t actually know how to setup SMTP authentication in Sendmail. It’s been years since I’ve managed a sendmail server. Maybe somebody else knows how and will chime in. You’re going to need saslauthd up and running, and you’ll need to tell sendmail to relay when saslauthd authenticates someone. I don’t think it’s possible to make that into a simple button…SMTP authentication is actually quite challenging to setup.
Unfortunately this box has Fedora installed on it. Do you suggest I go download some other distro and rebuild the box? If so, which? AAARGH.
In any case, I used yum install postfix.
If I shut off sendmail and start postfix, it appears to be running in webmin, but, I can’t actually connect to it… so far, I haven’t actually been able to find the page where the listening port is set, but I assume that’s 25.
Any ideas why I might not be able to connect to it - but I CAN connect to sendmail when it’s up?
Yeah, it’s been years since I’ve dealt with Sendmail, so I probably won’t be able to help much in getting that working
If you were using Postfix, what I would do is fire it up – and then look in /var/log/maillog when you launch the daemon, and when the client connects, to see what sort of error is in there.
However, Fedora is troublesome for a server-distro. It’s life cycle is a bit short. Moving to a Virtualmin-supported distro would solve a few problems, including giving you longer support for your server, as well as allowing you to get everything working using the install.sh script.
The install.sh gets everything setup for you out of the box. If you’re familiar with Fedora, I might suggest CentOS 5 as a server distro. But Debian 5 and Ubuntu 8.04 are good too.
-Eric
Fine, I guess I'll be up all night installing CentOS and giving it another shot if it's gonna save me some headaches down the road.
If it’s taking you all night, you’re doing it wrong.
You generally only need the first CD for a minimal install; and it should only take 20-30 minutes. install.sh will take care of installing the extra stuff over the network using yum, and can be left unattended.
I’m confused why the internal IP of the client computer is listed, since it’s connecting to a public facing computer, and I’d suspect I would see the router’s address as the client, but, in any case, I’m still getting the relay access denied…
I’ve followed step by step the installation instructions from a blank slate.
Now we have a common starting point to work from, we know how the system looks and is configured ATM, so that’s good.
Assuming you’ve created that email account in Virtualmin, the most common reason you’d get that is if the client weren’t sending it’s login info when sending the email.
The email client needs to be configured to authenticate outgoing SMTP messages. For example, Outlook is like that – you have to check a box in the settings in order to get it to attempt authentication for outgoing SMTP connections.
There’s a few other possibilities, but let’s see if this does the trick first
If it doesn’t, do you see any errors in the mail log if you log in over SSH, and type:
