It's not that difficult. A painting by numbers task. rather than requiring you to know what you are doing.
It's not that difficult. A painting by numbers task. rather than requiring you to know what you are doing.
I have added a side box with some details of how the domain bit can be used or not with ISP email provisions depending whether they let you use subdomains.
You sometimes see that kind of thing used when configuring email as a way of naming mailboxes that belong to one customer, but are tied to multiple email addresses.
So with plusnet for example they give you a "catch all" style mail setup
- so all mail sent to any address on your username gets delivered to the same mailbox. To collect mail you have your mail software login with a username that just matches the account name. So say your account was "artichoke" you would login to mail.plus.net with the username "artichoke". They also create a "catch all" mail setup by default. So you could advertise the email addresses " snipped-for-privacy@artichoke.plus.net" and " snipped-for-privacy@artichoke.plus.net". However both addresses would receive email and that would all go to the one mailbox.
If you want you can configure multiple mailboxes so they go to their own mailbox. When configuring your mail software you then need to manipulate the login username to identify which mailbox you want if you don't want the catch all one. So you would have your email client login with "artichoke+sales" or "artichoke+jeff"
Other mail systems also have some foibles... like gmail will allow the insertion of a "." in an email address anywhere you like. So snipped-for-privacy@gmail.com and snipped-for-privacy@gmail.com are to gmail, the same user (even though to the outside world, they are different email addresses)
Let me know if you want more stiff expanded in what is there so far.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required