tmboyington wrote:
I wanted to avoid having exim4 listen for SMTP connections for security concerns. Am I just being paranoid?
No, I think that's a good policy - no reason to accept inbound connections if you don't need to.
Quote:
Is there a way to compose my outgoing messages (perhaps by adding a reply address in the header) so I won't get the error message if I set exim4 to only listen on 127.0.0.1?
It's up to the receiving system, but given the error in this case, I suspect it is always going to validate the envelope from address, independent of any reply-to header. But that doesn't mean you have to have exim receive connections - just have mail for your domain received somewhere else (like, for example, Google Apps).
The error, and what Stever was saying, is that you can't make up a domain for your sending address that can't itself receive mail, at least for that recipient server. But that inbound mail doesn't have to be sent to the same host doing the sending.
In other words, if you're using the domain imperiumreclaimed.com on your outbound mail, just make sure that mail sent to imperiumreclaimed.com goes somewhere valid. Otherwise, your mail just looks forged - well, and without a valid receiving system, arguably is forged - and will likely be rejected in a variety of ways.
Quote:
I'm mostly interested in receiving error notifications and to eventually use an email verification during account creation. The messages aren't intended to be replied to but having a reply-to address for abuse and other issues is a good idea.
Unfortunately, in today's spam-filled world, many systems are not going to be happy if you try to make up a domain for your sending address (even if not intended to be replied to) that has no facility for receiving mail. Different systems may impose different rules to try to isolate spamming/forgery - the one you ran into seems to specifically require the ability for the domain to receive mail.
-- David
FAQ
Search
Members
Register
Login [ Anonymous ]
