Clayton wrote:
A few years ago I already gave up on using a dynamic ip even for a private server to tinker with. You are facing two problems with a dynamic ip:
- receiving: you have to rely on dyndns to switch fast enough to your current address AND rely on external clients not to cache the dns results too long.
I'm not having any problems at all with it for the webserver side. I've been using this for two years. External client caching has not (to my knowledge) been an issue at all. DynDNS takes care of the switching quite smoothly. I've tested several times right after an IP change and they've caught it right away.
- sending: if you don't use your isp mailserver as relay you might as well stop here. Most mailservers do not accept mails from clients with dynamic ip. Additionally, your reverse dns record does not match your dyndns name.
Doesn't the Mail Relay take care of that issue? They provide the MX linking direct to my domain name. The actual IP is irrelevant - that is, they take care that my domain and IP match between my machine and them... upstream, from them to the internet... that info should.. as I understand it be relayed invisibly.... maybe time to read more on the DynDNS side of things... and ask them a few questions.
C.
I've had this working reliably for a few years now. I'm certainly no expert on postfix, but it is doable. I use dyndns for 2 services. Their Custom DNS service will route mail to your dynamic IP address by maintaining your domain name to your changing IP address. Run a client like rundns or ddclient on your server to keep their service up to date with your current IP, or perhaps your router will do this but some linksys routers have broken ddclient configs. The second dyndns service I use is Mailhop Backup. This will catch your emails in the event your mail server is down or offline. When you get back online they will be forwarded to your server in a few hours. I actually added this service later just for reliability sake, I ran with out it for a few months. This will allow incoming email to find your server. Regarding sending email, strictly speaking you can send emails out directly from your server to each intended recipient thru their mail servers. But Sandy and Per are right. Practically speaking so many mail servers nowadays do not accept emails from mail servers running on dynamic IPs. This to cut down on spam, so you will need to set up a mail relay. But take this one step at a time. Make sure your mails are coming in. Then make sure they are being sent out, and received at at least one or some address. Then configure your mail relay. I use my ISPs smtp server to relay, which they allow from one of their IP addresses. Your still sending email from your server, just relaying it thru their server, which will probably be relayed thru one or more relays on its way to the various recipients. I never had any luck using the defaul $myhostname, or $myorigin, or $mydestination, I had to hard write these, but I could have had my machine configured incorrectly. Once you get your receive and send working, you can set up spamassassin, and amavis. And filters. Post back with your config info if you haven't gotten with working off list. The guys on this list really know their config file stuff. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org