[SOLVED] Mail Server - Relay access denied - What on earth is this?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
So how do I go about making this work using postfix
You don't want to. You really, really, don't want to.
In that test mxtoolbox.com is testing whether or not it can send email to example.com via your MTA. "Relay access denied" is what you want to see. If it was successful you'd quickly find your server being used to relay large volumes of spam. Open mail relays are one of the things that bot's search for across entire IP ranges.
What are you actually trying to achieve? Being able to send mail from that machine? use it as a relay on an internal network? Let selected outside users relay email through it? Or allow the whole world and it's dog to be able to relay mail through it?
Last edited by redgoblin; 01-18-2011 at 06:44 AM.
Reason: Spelling, syntax
1) My wife and I to be able to receive email from the outside world
2) My wife and I to be able to send email from the inside to the outside world
3) To have it secure using whatever means and to have a working spam program that will pick up the nasty stuff
As I said in my previous mail (link above) I already had a setup but my ISP decided to go out of business so I had the idea of starting the "whole" email process myself instead of using the ISP's smtp servers to connect fetchmail/postfix/dovecot etc etc.
As for your other questions they might require individual threads (if any of them aren't working the way you want) a long with setup, etc. Start from the bottom up; get mail working between accounts on the server, within the LAN, going out, then comming in.
Having a static IP is a very good start. You might need to have reverse DNS set up for your IP address as well as many mail servers are very strict about these things. I've been running my own mail server on a UK DSL line for several years and it's proven to be fast and secure.
In relation to your original post (on this thread) I think you've got your answer; refusing to relay is a good thing! Does that cover your original question?
Do you have a fixed IP for your mailserver?
If not, your mail will be refused by other smtp servers.
what has a dynap to do with not being able to send out mail.. (the MTA won't mind which ip it has, as long as it can find the destination) (and the receiving mta won't mind either for that matter)
only BAD configured smtp's do that. PBL blocking e.g. (spamhaus)
PBL is not a blacklist, although some lame ass mta administrators think so (because they block every IP in the PBL, thus lots of problems for their customers).
An MTA purely by itself would not know if the IP of the sender is Dynamic or static.
Secondly, infact each IP is dynamic in technical terms, since each netblock can be revoked, used as the LIR wants etc..
Can change as see fit...(thus dynamic)