Re: Helo command rejected: need fully-qualified hostname being in a home network
Martin <[email protected]>
| Newsgroups | gmane.comp.jakarta.james.user |
|---|---|
| Message-ID | <[email protected]> |
It is still possible to run from a dynamic IP. I solved it by setting the helo domain to the domain of my ISP (<helloName autodetect="false">tx.res.rr.com</helloName>), which works fine for inbound connections, and using Google's SMTP service for outbound mail. Using this setup, I don't get any rejections, and virtually no spam ever gets through either. Using my own SMTP for outbound works for most, but is rejected by some (particularly Microsoft setups....). On 11/29/20 3:58 PM, David Matthews wrote: > hi Pablo > >> But this setup is in a home network. The setup uses Dynamic DNS where the james server is behind the router, and the router is forwarding ports 25, 587 to the james server. >> > I used to do something like that 15 years ago, but I wouldn't think of trying to run a mail server from inside a home network now. Even then a lot of mail got grey listed; I'm surprised you get gmail to accept mail at all now. > > I think that email servers in general do not like dealing with anything without a static ip address. I'm pretty sure that's the case if you're on the end of a broadband home connection and I'd guess the same applies if you try and use a dynamic DNS service. > > I'm not certain this is the problem you have just now (although I think it might be), but I don't think what you're trying to do is going to lead to a happy life. If you want to run an email server (an excellent idea!) I'd suggest getting a VM from someone like linode. > > -- > David Matthews > [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >