Hi
I’ve been searching mailinabox.email and github issues for information concerning the rationale behind the “box” hostname recommendation if there is any. Why “box” when perhaps “email” or “webmail” would be better from user perspective when the mail-in-a-box scripts use it to set up the URI?
Of course usually the hostname is service agnostic and you point cnames like “webmail” to a specific hostname but advanced configurations like that is out of scope for this project afaik.
Just curious if there is any rationale behind it, no big deal.
Any subdomain can be used — this is just what’s recommended for the purpose of making the documentation/setup easy. (You probably don’t need to use a subdomain at all, but I haven’t tested that in ages and I think using a subdomain is more flexible.)
I chose “box” because it’s a mnemonic for “Mail-in-a-Box.” And it’s shorter than “mail.”
I am inclined to say that mail as the default subdomain would be preferable to “box”, as many email clients default to mail.domain.tld when guessing mail server name. I was under the impression from the installer that I should not choose another name, until I saw this.
Would it by possible to create an alias ‘mail’ for ‘box’? Or is there a way of “renaming” a box.xxx.tld MIAB server to mail.xxx.tld (at the cost of re-issuing existing SSL certifcate(s)?
I’d also prefer to have mail.xxx.tld instead of box.xxx.tld to access email-server - but that’s just my personal preference…
I’m using puck.nether.net as secondary DNS server. Would adding a CNAME require to be added to the secondary DNS too (which isn’t possible with puck.nether.net from what I could figure out…)?
Cheers,
Andy
P.S. Adding only a CNAME in the DNS on the MIAB doesn’t work though…
Ok, I figured it out, that a CNAME works. Only thing is import to add the “dot” at the end of the MAIB address (e.g. box.yyyyy.tld. <- the dot is the important thing!)
Did they tell you that or are you just assuming it? Also, if it is because of the domain name, it’s much more likely because of the TLD, not the subdomain.
Btw. Your IP (you revealed it by posting your PTR record) is still blocked by Proofpoint, and according to MX Toolbox your mail.xxxx.email domain is on two blacklists, while the box.xxxx.top domain looks fine.
So if I had to guess, the Proofpoint block probably has nothing to do with your domain name, but it’s more likely that either the entire IP range is blocked (this is often done for VPS providers such as Vultr, DO, Linode, etc. that are or were frequently used by spammers), or maybe the previous user of your IP was using it for sending spam.
It is a vultur US IP. Proofpoint seems to be obsessed with these IPs. Write them, they might delist you. Explain that you not sending unsolicited mail and your server is for personal use and is configured correctly. Otherwise the IP seems perfectly fine.
Then Proofpoint outright lied to you in the email that they sent you which clearly stated that they could NOT remove the block because of your rDNS, or lack of in this case.
rDNS was fully validated, it was for 3 weeks. I tested it many times.
They could possibly do that to get you as a customer, but what can you do to get unlocked? After 3 weeks of not being able to reach my customers on icloud.com, att.net, etc… I decided to try to do what they are asking, what else can I do?
