|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
20 Apr 2007, 01:05 AM | #61 | |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
Enhanced account required for personal domain use
Quote:
Bill |
|
27 Apr 2007, 01:26 AM | #62 |
The "e" in e-mail
Join Date: Jan 2002
Location: San Francisco
Posts: 2,458
|
A good thing! The DNS is a great system - elegant, efficient, and multifunctional, but it's not something one can figure out without RTFM, and most folks refuse to RTFM. Not to mention there is no single FM (Fine Manual); I've learned one thing after another, over time. I expect it would be an expensive feature to support.
|
27 Apr 2007, 01:58 AM | #63 | |
Ultimate Contributor
Join Date: Dec 2001
Location: Canada.
Posts: 10,355
|
Quote:
|
|
27 Apr 2007, 02:02 AM | #64 | |
Cornerstone of the Community
Join Date: Mar 2004
Location: London, UK
Posts: 834
|
Quote:
Jason |
|
27 Apr 2007, 02:17 AM | #65 |
Ultimate Contributor
Join Date: Dec 2001
Location: Canada.
Posts: 10,355
|
Tuffmail are able to support custom DNS for all account levels, even the cheapest ones Jason.
|
27 Apr 2007, 03:21 AM | #66 |
Cornerstone of the Community
Join Date: Apr 2004
Posts: 812
|
Mx
Hi,
I have added one domain to my FM account. Now I want to change the MX of this domain and I have two MX records. So guide me, how can I change the MX of a domain ? |
27 Apr 2007, 05:13 AM | #67 | |
The "e" in e-mail
Join Date: Jan 2002
Location: San Francisco
Posts: 2,458
|
Quote:
Jason made a correct interpretation of what I said. |
|
27 Apr 2007, 05:55 AM | #68 |
Ultimate Contributor
Join Date: Dec 2001
Location: Canada.
Posts: 10,355
|
My remark was regarding your response to ao1's question who said:
>> Am I right to understand that this feature is only for "enhanced" users? >> Your reply was: >> A good thing! The DNS is a great system - elegant, efficient, and multifunctional, but it's not something one can figure out without RTFM, and most folks refuse to RTFM. Not to mention there is no single FM (Fine Manual); I've learned one thing after another, over time. I expect it would be an expensive feature to support >> Fastmail previously allowed lower account levels to host their virtual domain name (for email only) - as do Tuffmail. If Fastmail still allowed this, those account holders (other than enhanced account holders) would likely be able to take advantage of these new new custom DNS features - that is the point I was trying to make... |
27 Apr 2007, 06:01 AM | #69 |
The "e" in e-mail
Join Date: Jan 2002
Location: San Francisco
Posts: 2,458
|
David,
You confused hosting the DNS records for a domain with hosting just the email for a domain, and which providers offer which of these two things with which plan. (Oy, that's not helping clear things up, is it? I give up. Over and out.) |
27 Apr 2007, 06:22 AM | #70 | |
Ultimate Contributor
Join Date: Dec 2001
Location: Canada.
Posts: 10,355
|
Quote:
>> Tuffmail are able to support custom DNS for all account levels, even the cheapest ones Jason. >> The other points I mentioned, I agree are not at all to do with the subject of the thread, so I will not talk about them anymore |
|
27 Apr 2007, 09:51 AM | #71 | |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
Quote:
Read all of this FAQ for more details: Fastmail virtual domains But if your DNS is still hosted somewhere else -- in other words, if your domain name servers are not pointing to ns1.messagingengine.com and ns2.messagingengine.com -- then you must use your domain manager company's tools to change your domain's MX records. Bill |
|
27 Apr 2007, 08:15 PM | #72 | |
Cornerstone of the Community
Join Date: Apr 2004
Posts: 812
|
I want DNS with FM, but MX pointed to some one else... is it possible & how to change custom setting for this too ?
Quote:
|
|
27 Apr 2007, 09:13 PM | #73 | |
Senior Member
Join Date: Apr 2006
Location: London, England
Posts: 166
|
Quote:
Firstly you need to make sure that you point your name servers at fastmail, their name servers are ns1.messagingengine.com and ns2.messagingengine.com. Once the transfer is complete, go into the Custom DNS panel in your Fastmail account and select your domain from the domain popup and click select. In the DNS Mode section click Custom DNS and then click Change. The custom DNS area will become available, you will see two MX entries, one for your domain and one for any subdomain. Both these are currently set to STANDARD_MX, you will need to change them to the MX address that will accept mail for your domain. Fastmail's MX records are in1.smtp.messagingengine.com and in2.smtp.messagingengine.com, I assume that STANDARD_MX points to both of these, so you will need to add more MX records for your backup MX servers. One of my fastmail hosted domains shows the following for its MX records: xxx.co.uk. 3600 IN MX 10 in1.smtp.messagingengine.com. xxx.co.uk. 3600 IN MX 20 in2.smtp.messagingengine.com. And then it shows in the additional section: in1.smtp.messagingengine.com. 21110 IN A 66.111.4.72 in1.smtp.messagingengine.com. 21110 IN A 66.111.4.73 in1.smtp.messagingengine.com. 21110 IN A 66.111.4.70 in1.smtp.messagingengine.com. 21110 IN A 66.111.4.71 in2.smtp.messagingengine.com. 72385 IN A 66.139.75.100 So there are four addresses for in1.smtp.messagingengine.com and one for in2.smtp.messagingengine.com. Regards Alan |
|
3 May 2007, 03:59 PM | #74 |
Member
Join Date: Oct 2003
Location: USA - Boston
Posts: 54
|
Rob, I love the new feature you've added. I think that adding cloaking to it would be especially useful for some of us who are stuck behind restrictive firewalls—similar to how Fastmail's universal proxy already allows us to use IMAP/POP3/SMTP clients, even when the usual SMTP/POP3/IMAP ports are blocked, since normally at least 80/8080 are open (not to mention 22/23 and sometimes ports in the high thousands ranges).
In other words, if I could go to foo.example.com (my own domain), which would redirect with cloaking to fastmail.fm, and then if cloaking were enabled so that after logging into Fastmail it would still show foo.example.com, that would allow us to use our own domain for webmail from behind proxies & firewalls —at least from behind those proxies & firewalls which are not smart enough to do reverse lookups. At present I can already go to mail.example.com (my own domain), but after logging into Fastmail I'm then at fastmail.fm, which the evil proxy blocks.... |
3 May 2007, 05:28 PM | #75 |
Intergalactic Postmaster
Join Date: Oct 2001
Location: Melbourne, Australia
Posts: 6,102
Representative of:
Fastmail.FM |
We've implemented cloaking the way everyone else does it, which is to create a frame that takes the whole window and go to the URL in that. That means the URL of the page still looks like the URL you went to, and doesn't change, only the URL in the frame (that you can't see) changes.
What you're talking about is more "proxying". We thought about it, but didn't add it mostly because it uses bandwidth on our end, so we'd have to track all page loads and count that against the user. It's possible, but a pain to implement. Rob |