Bugzilla

OK, but then this bug is really invalid, and the mail server config wrong.
If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

So, either uberspace needs to change their server names or their Public Domain Suffix registration. The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end. This is the end of this bug.

-> INVALID

OK, but then this bug is really invalid. If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

So, either uberspace needs to change their server names or their Public Domain Suffix registration. The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end. This is the end of this bug.

-> INVALID

OK, but then this bug is really invalid. If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

So, either uberspace needs to change their server names or their Public Domain Suffix registration. The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end.

-> INVALID

OK, but then this bug is really invalid. If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

So, uberspace needs to change either their server names or their Public Domain Suffix registration. The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end.

-> INVALID

OK, but then this bug is really invalid. If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.
So, uberspace needs to change either their server names or their Public Domain Suffix registration.

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end.

-> INVALID

OK, but then this bug is really invalid. If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.
So, uberspace needs to change either their server names or their Public Domain Suffix registration. It should be trivial for them to create an `imap.server.harrison.userspace.de` DNS A record and use that, whereby `server.harrison.userspace.de` is the domain name (according to their own registration choice) and `imap.server.harrison.userspace.de` is the hostname.

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end.

-> INVALID

OK, but then this bug is really invalid. If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.
So, uberspace needs to change either their server names or their Public Domain Suffix registration.
It should be trivial for them to create an `imap.server.harrison.userspace.de` DNS A record and use that.

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end.

-> INVALID

OK, but then this bug is really invalid. If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.
So, uberspace needs to change either their server names or their Public Domain Suffix registration.
It should be trivial for them to create an `imap.server.harrison.userspace.de` DNS A record and use that, whereby `server.harrison.userspace.de` is the domain name, according to their own choice in Public Domain Suffic list.

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end.

-> INVALID

OK, but then this bug is really invalid. If `customer1.foo.uberspace.de` is the customer domain, then `foo.uberspace.de` is really like `co.uk`. In fact, that's *precisely* what their Public Domain Suffic registration says, that `harrison.uberspace.de` is explicitly *not* a server, but on the same level as `co.uk`. Just as there cannot be a server or mail server with the hostname `co.uk`, there cannot be a mail server with the hostname `harrison.uberspace.de`, given the current registration.

The behavior of Thunderbird and of the Effective TLD service is completely correct here. `co.uk` is not a valid hostname.
So, uberspace needs to change either their server names or their Public Domain Suffix registration.
It should be trivial for them to create an `imap.server.harrison.userspace.de` DNS A record and use that (whereby `server.harrison.userspace.de` is the domain name, according to their own choice in Public Domain Suffic list).

Please note that this bug has cost me a lot of time to investigate, and it turns out to be a bug in uberspace.de, so please do not continue to argue this here, but take it up with uberspace.de, as they need to fix this on their end.

-> INVALID