The only issue I have with running my own mail server is that I can receive e-mails, but for whatever reason I cannot send out e-mails. I'm assuming it's because mail servers are denying e-mails from my IP or something since I'm on a residential connection. It doesn't even reach the Spam box, just doesn't show up at all even though a test with telnet says the mail was successfully sent out.
I believe it's an issue with DNS records. If I recall correctly, you need to ask your ISP to change some DNS records. I don't recall what needs to be done, perhaps somebody else can clarify this. At the risk of sounding like an advertisement, dyndns.com's "outbound mailhop" service gives you an SMTP server you can send email from: it's the one I use and I've so far had no problems sending email. Patsy
The problem isthat you won't pass muster when you're checked for a reverse IP lookup. It's highly unlikely you'll want to use as your hostname the alphabet soup your ISP assigns whatever machine is on your current IP, and even if you do, your machine won't be delegated to handle mail within that domain.
> Received: from [96.250.43.19] # host 96.250.43.19 19.43.250.96.in-addr.arpa domain name pointer pool-96-250-43-19.nycmny.fios.verizon.net. 1. verizon blocks outgoing port 25 2. your ip range is shitlisted in most dnsbl 3. your reverse lookup matches the "dynamic ip"-match a lot of mx simply wont accept mail from. X. if you want to host the mx on your residential line, get a static ip with your own domain/reverse. Y. switch providers, oh, that is a nogo in most parts of amerika, sorry u'r fkd. Z. rent a server to host your mx on. :)
Two things are probably occurring: 1) Many ISPs block outbound email on port 25 to prevent SPAM abuse. 2) You will not be able to send email directly to most email servers because your server identify cannot be verified. The best solution is to forward your SMTP traffic trough your ISP. Lee
