|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
6 Dec 2021, 02:49 PM | #16 |
Senior Member
Join Date: Jan 2010
Location: Melbourne, Oz
Posts: 133
|
Is there a difference between the username parts of your Fastmail and Google email addresses?
For example, are you using something like 'name@gmail.com' and 'name+somethingelse@domain.tld'? I have encountered services that won't accept symbols like '+' in an email address (despite it being valid) and record the email address as 'name somethingelse@domain.tld' (ie replacing the '+' with a space) which doesn't work but is not necessarily detected as the reason for failing. That's just an example. Maybe it's worth testing an alternative if you are using different usernames? (Unrelated but similar issue: this service doesn't seem to consider 'name+somethingelse@domain.tld' to be a valid email address but it automatically converts 'somethingelse@domain.tld' to display as an email link above.) Last edited by pjroutledge : 6 Dec 2021 at 02:59 PM. |
6 Dec 2021, 02:55 PM | #17 | |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
TTL (Time To Live) is crucial
Your DNS records include a TTL (Time To Live) field for each record. The TTL value specifies the requested time (in seconds) that DNS entries (such as MX) are cached. See:
https://en.wikipedia.org/wiki/Time_to_live So if your old TTL value for the email related records (MX, SPF TXT, DMARC TXT) was 86,400 (one day), then over one day (maybe two days) before the changeover date you would change those TTL values to something small (such as 600 for 10 minutes). Then after the original TTL delay has passed (with some additional delay for good measure), you can change the DNS records (and their TTL values) to the new values. Some servers may check your DNS records sooner than the TTL value specifies. But you can't depend on them using the new DNS record values until after the TTL-specified delay expires. This also depends on when the servers happened to have a need to check your DNS records. This is why some email servers may use the old MX value and others the new value. Your sites should be:
Quote:
Bill |
|
6 Dec 2021, 03:29 PM | #18 | |
The "e" in e-mail
Join Date: May 2003
Location: mostly in Thailand
Posts: 3,095
|
Quote:
Those suggesting TTL and email address issues have presumably not considered the tests you have done switching back to Google and then to Fastmail again. The sending side (if the narrative so far is accurate) simply cannot reach the Fastmail MX servers. |
|
6 Dec 2021, 10:25 PM | #19 | |
Junior Member
Join Date: Dec 2021
Posts: 15
|
Quote:
It's hard to test using alternatives as I can't easily reproduce the problem except with Paybright - because with Paybright I can actually trigger an email to my address anytime I want. Thing is, since I don't get the emails so i can't login.. catch 22. |
|
6 Dec 2021, 10:27 PM | #20 | |
Junior Member
Join Date: Dec 2021
Posts: 15
|
Quote:
|
|
6 Dec 2021, 10:29 PM | #21 | |
Junior Member
Join Date: Dec 2021
Posts: 15
|
Quote:
I'll give you a good example - my Sales advisor from Tesla can email me directly from his Tesla account and it works fine. When he uses his "system" which sends from Tesla.com as well, but shows his address - I don't get it and their system shows the email as "Undeliverable". It's definitely, almost certainly, related to something about mass-email systems. Tesla, Shopify, some of my newsletters, Paybright, all use mass email systems to send email. Individual emails from people - no problem. |
|
6 Dec 2021, 10:40 PM | #22 | |
Member
Join Date: Apr 2007
Posts: 72
|
Quote:
|
|
6 Dec 2021, 11:44 PM | #23 |
Junior Member
Join Date: Dec 2021
Posts: 15
|
|
7 Dec 2021, 02:31 AM | #24 |
The "e" in e-mail
Join Date: May 2003
Location: mostly in Thailand
Posts: 3,095
|
Possibly, but why then do the messages not arrive in the Google mailbox? Does Google reject mail for active accounts if it detects that its MX servers are not in the current DNS? That would be a bit surprising because we tend to rely on the fact that messages may arrive at either the old or new mail server, for a limited time, when migrating from one system to another.
|
7 Dec 2021, 03:55 AM | #25 |
Junior Member
Join Date: Dec 2021
Posts: 15
|
Here's the answer one of the providers I'm unable to receive messages got as a bounce.
Recipient address rejected: User unknown in virtual mailbox table Which makes absolutely no sense since as I said I get 99+% of my email so obviously the address exists. |
7 Dec 2021, 04:01 AM | #26 | |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
Quote:
Bill |
|
7 Dec 2021, 04:42 AM | #27 | |
Junior Member
Join Date: Dec 2021
Posts: 15
|
Quote:
I'm trying to get them to send me the full message (they only sent me the copy and paste of the error). If I can get that I can send it to Fastmail support. |
|
7 Dec 2021, 09:27 AM | #28 |
The "e" in e-mail
Join Date: Jul 2002
Location: VK4
Posts: 3,029
|
check that you have in1-smtp.messagingengine.com and not fastmail.com
|
7 Dec 2021, 12:38 PM | #29 |
Junior Member
Join Date: Dec 2021
Posts: 15
|
|
7 Dec 2021, 04:23 PM | #30 |
The "e" in e-mail
Join Date: Oct 2002
Location: Holon, Israel.
Posts: 4,857
|
This feels like a greylisting issue: normal mail gets through. Systems that send bulk mail and are configured not to retry sending do not get through (e.g. a system that sends a code that's valid for the next five minutes might be configured not to resend after more than five minutes have passed if the first try fails. So it fails greylisting and after repeatedly failing greylisting might be automatically added to a local blacklist).
|