Thanks for the answers, I agree that imap may be right, but my dns supplier has a quota at 40MB. I like to keep my mails, additional to my privat I am following several mailing list, separated, so the quota is way to small. I feel like the best for me is to move my domain here, setting up my own server. I have been using djbdn and qmail earlier, but would like to change to something more standard, I should manage though, but I am a little afraid of the work load setting things up.
So my question at the moment boils down to, witch supplier of dynamic dns service to use, that also mx forward without to many restrictions.
Thanks Kai
On Sep 6, 2006, at 10:49 AM, kai wrote:
I've had very good experiences with ZoneEdit (http:// www.zoneedit.com/). They give you up to 5 domains at no charge with a reasonable array of services, their web interface is simple and straightforward, and I haven't been unable to do something DNS- related that I wanted to do. Their DDNS update mechanism can be implemented with a one-line invocation of wget, suitable for running via cron; no special client is necessary.
I would also recommend looking into Rollernet (http://rollernet.us/) for secondary DNS and secondary MX service. They also provide a reasonable range of service at no charge (though, as with ZoneEdit, you need to pay for some of the advanced functionality). It's a great relief to know that if I have to take my mail server down for maintenance I won't miss any mail.
Finally, if you want to run your own server, I recommend the Qmail Toaster (http://www.qmailtoaster.com/). It's a turnkey solution that runs perfectly on CentOS and provides far more capabilities than the stock packages do.
-steve
-- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
kai wrote:
I use dyndns for my free domains.
I don't use secondary MXes because 1. Legitimate senders should queue when I'm down 2. I don't control what mail someone else accepts for me 3. Spammers rely on 2 to inject spam into my system. When I had a secondary MX, almost all the mail I got through it was spam. 4. In practice ou can't reject incoming mail your sendondary because, if you do, you will contribute to the enormous backwash of bounces to innocents.
Before I implemented this, I ran the idea past an antispam list; there seemed no cons, and some of the others also didn't have secondaries for the above reasons.
kai spake the following on 9/6/2006 7:49 AM:
You could set up your own server, and fetchmail all the mail from your providers pop server. Then you could access your own server through IMAP and you would have control over how much space you would need. This will get past the possibility of your "here" (I'm assuming at home) server being port blocked at mail delivery. On my home cable connection, I can send and receive on port 25, but dns and http are "blackholed". Since I administer the mail at work, I haven't worried about it. All my home system does is send logwatch reports to me at work, and all the other sundry things you might expect a home system to do. ;-)
kai wrote:
What does your DNS supplier have to do with your mail delivery? If you own the domain name, you can have anyone you choose to host it, and if they provide a mail service, you don't have to use it. If they host our DNS, the IP addresses they point to should be the ones you tell them to point to.
If, as Scott surmises, your home systems smtp port's blocked, that's a different, unrelated issue. If your Internet Access Provider requires you to send outgoing email via his server, that's fine - it helps cut down spamming rogues, and can help you with quicker delivery, especially where you have multiple recipients, or you like to turn your internet off when not in use and some recipient's mx is down.
If you do host your mail service, you can have as many email addresses as you like.
-
John Summerfied -
John Summerfield
-
kai -
Scott Silva -
Steve Huff