Custom DNS on beta server

[eggman]

Originally Posted by thelanboy

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....

This seems to be because using the secure login button causes redirection to https://fastmail.fm Probably to avoid certificate errors i imagine

Its not ideal but a way around this is to login insecurely which circumvents the proxy problem you describe - the url then stays as mail.example.com after login

hope that helps someone anyway.... (sorry for the off topic)

[robmueller]

Yes, a secure login always has to redirect to www.fastmail.fm to avoid certificate problems.

There is one way around this. Instead of going to www.fastmail.fm, go to:

https://mail.messagingengine.com/?UDm=49

And do a Secure Login there. It will keep you at https://mail.messagingengine.com

For the curious. So that different brands could support secure logins, we went with two solutions.

1. Provide your own cert for your domain (eg www.fastmail.fm)
2. Use our "generic" mail.messagingengine.com cert

FastMail uses 1, but the mechanism that makes 2 work can also be made to work for fastmail, if you use the URL mentioned above.

Rob

[bblount]

I noticed we can't add TXT records with the Custom DNS. Is this a planned feature? Seems like it would be fairly easy to implement? SPF would be great.

[Isegrimm]

Hi, I'd also like to have the TXT record added.

I'm currently using an emailaddress in the form of firstname@surname.com. The DNS for the domain surname.com is handled by Fastmail.
I also have an Outlook account with 4Smartphone.net to send and recieve mail on my smartphone. With that account I can send mail from the outlook client on my windows mobile smartphone using my emailaddress first@surname.com.

All goes well, but when I send mail to Google (Gmail, etc), my mail gets rejected with this error:
Received-SPF: neutral (google.com: 66.45.56.150 is neither permitted nor denied by best guess record for domain of myname@surname.com)

I think the ability to specify an SPF-record would solve this problem.

Thanks in advance!

[digitalranger]

Please make all this available for Full Account holders.

Thanks.

[n5bb]

Originally Posted by bblount

I noticed we can't add TXT records with the Custom DNS. Is this a planned feature? Seems like it would be fairly easy to implement? SPF would be great.

Originally Posted by Isegrimm

Hi, I'd also like to have the TXT record added.
...
I think the ability to specify an SPF-record would solve this problem.

For the benefit of those reading this old thread, TXT and SPF records were added to the Fastmail Custom DNS screen sometime before July 26, 2007.

Originally Posted by digitalranger

Please make all this available for Full Account holders.

It wouldn't be of any use for Full accounts, since you can only use your own domain with Fastmail if you have an Enhanced account. These Custom DNS features only affect domains you own.

Bill

[hadaso]

Originally Posted by brong

That and every MTA in existance will rewrite your email from:

foobar@example.com to foobar@me_at.dyndns.org, completely ignore the "MX" record above and deliver to the MX record for me_at.dyndns.org and, um - steal your lunch.

Seriously.

We rolled out a change that used CNAME records for our domains once. For about 12 hours. We had a zillion emails to username@web.messagingengine.com. Some clients had even rewritten mentions to the old address in the body of the email when they quoted because they were online and they could do an MX lookup.

Yeah.

Just don't do it if you're using the domain for email.

I was wondering whether CNAME might work for email if one just want to duplicate a domain.
Specific scenario: I have mydomain.net and I got mydomain.com which I don't like as much as the .net one but I am worried that some correspondents mught just type ".com" instead of ".net". I what I want to do with mydomain.com is just make sure that if someone uses localpart@mydomain.com it would be delivered as if localpart@mydomain.net were typed. So using CNAME to point mydomain.com to mydomain.net might do the job since any MTA would rewrite localpart@mydomain.com to localpart@mydomain.net (or perhaps any MTA except spambots ). This would eliminate the need to have every alias defined twice (once for each domain) and the nuisance of having to verify that everything is properly duplicated. But then there are probably some complications?

Suggestion: having an option in the "Virtual Domains" screen to "duplicate" a virtual domain as a copy of another one might be useful.

[beq]

I would normally said don't do that as it's asking for trouble -- just avoid creating a CNAME for any domain/subdomain that you will receive mail on. I had read that you get non-guaranteed behavior (most mailers will resolve to the target of the CNAME before MX lookup, but not all).

So I'm guessing you have to worry about formmailers, legitimate mailing lists, and other stuff in addition to standard MTAs?

Why not just add yourdomain.com as a second virtual domain in your FM account, and alias it to yourdomain.net? Create a catchall virtual alias *@yourdomain.com -> *@yourdomain.net.