[SOLVED] Postfix/Dovecot email server - can't send emails
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
I'm running Ubuntu 8.10 server edition with postfix and dovecot handling my email duties. Currently, I can log in correctly and receive any mail/sync folder (IMAP) but I cannot send mail to any address I care to try.
Is this not the remote server telling you to get stuffed, possibly because you're coming from a dynamic IP? Generally you'd be better off looking to always relay outbound mail via your ISP's smtp relay, which hopefully exists. This means that email is directly passed from an official known ISP MTA, not you, meaning it won't be blocked (or at least much less likely). That rejected relay source is tiscali... your ISP I take it? Try making it smart relay through smtp.tiscali.co.uk.
That's how I read it at least, not 100% sure it's that, if not maybe you need to clarify the topology you're using... sending to your MTA over the net instead of locally? Hard to see where the internet domains in the log come into the equation.
Last edited by acid_kewpie; 11-09-2009 at 12:52 PM.
What's happening is I'm attempting to send any mail from my laptop at home (Tiscali being my ISP) through my mail client, connected to my linux server.
The linux server is a hosted machine with a static IP address. The IP address in the error message above is of my laptop, not the mail server.
The sending fails in my mail client and I get the error message above in my mail log.
Is it possible it's rejecting my laptop's IP, and not the actual server IP? and therefore that the relay source in my mails is incorrect?
Which leads me to believe that my postfix setting:
mynetworks = 127.0.0.0/8
may be the cause of my issue.
mynetworks apparently "lists all networks that this machine somehow trusts. This information can be used by the anti-UCE features to recognize trusted SMTP clients that are allowed to relay mail through Postfix."
It's almost 03:30 here though, so I shall try that in the morning...
well mynetworks will stop anything other than the machine itself sending, depending on how it's used, and normally that would be 127.0.0.1/8,192.168.1.0/24 or something similar to permit local clients. I'm still a bit confused then as to why the logs are reporting inet hostnames as opposed to local data though. If this is all on a home LAN, then mynetworks would want to change, otherwise with authentication (and where does auth come into this... unclear again) then I think you'd want to define smtpd_client_restrictions to cover permit_mynetworks and permit_sasl_authenticated to allow you to send remotely with a username and password and locally without.
It's still vague where you are doing what... don't permit internet ranges in mynetworks, instead you need to authenticate really. Note that the act of authenticating doesn't mean anything in itself, you still need to attach a significance of it having been successful, e.g. the smtpd_client_restrictions directive (as I read the docs at least)
I added the smptd_client_restrictions option as you suggested, but no luck.
There is no sign of authentication in the mail log (when sending a mail) - just an anonymous connection and a relay denial.
My email client is definitely set to send user/pass info, so I'm not sure why there isn't some sort of authentication in the log