Aliases of mailing addresses. How to add email aliases

Any mailbox in The Bat! by default one email address is assigned, which you can configure in the menu Mailbox -> Mailbox Properties -> General information-> E-Mail address. Some service providers email allow users to add email aliases (pseudonyms), which are convenient to use for sorting incoming emails or sending emails from different email addresses.

In The Bat! There are several ways to add aliases to a mailbox.

1. Setting up folder personalities

If you are sorting incoming emails by aliases in different folders, you can add an email alias in the properties of the corresponding folder in the section Personalities. So, when you open a letter in this folder and click “Reply” or “Forward”, the program will automatically enter the alias of the email address in the field From.

Additionally, you can configure custom templates for new email, reply, forward, read confirmation and quick reply for each alias. The Bat! will use these templates if the appropriate folder is selected.

2. Quick templates

You can use quick templates to insert an email alias into a field From.

Go to menu Tools -> Quick Templates (Shift+Ctrl+Q) and create a new quick template. Specify Name And pseudonym template. You'll use this alias to insert a quick template into the body of the email, so it must be one word and contain no special characters.

Insert Macro %FROM="Address" into the template text, replace “Address” with your email address alias, and save the changes:

Open the email editor and enter pseudonym your quick template:

Press the keyboard shortcut Ctrl+Space to insert a quick template, or select it from the menu Tools -> Insert -> Insert Quick Template:

The Bat! will replace your email address in the field From alias of the email address you specified in the quick template.

You can create the required number of quick templates with email address aliases and insert them in the editor when you need to send letters using a different sender email address.

Having created “mail for a domain” for myself on Yandex, I decided to open free registration for third-party users of mailboxes on my “fashionable” domain. In addition to enabling the catch-all function, which directs all incoming mail from non-existent mailboxes on my domain to my main mailbox, I was faced with the need to reserve all the “standard” mailbox names so that there would be no misunderstandings when a name had already been filled in by someone else, and all “official” mail does not go to you at all. In P.D.D. You can, of course, expropriate any mailbox of a controlled domain at any time, but a residue remains. I was puzzled: What mailbox names are standard and system? Yandex technical support replied that they reserve for themselves only the postmaster@ name on each domain in order to track complaints and problems with mail, and that on at the moment The question of how to set reserved names remains open for them. Further, the result of an Internet search turned out to be a little predictable.
(in the picture: the famous black mailbox, a place of pilgrimage for amateur ufologists)

RFC

The first and most important thing I tried to find was an RFC, which turned out to be RFC 2142, MAILBOX NAMES FOR COMMON SERVICES, ROLES AND FUNCTIONS ( mailbox names for common services, roles and functions), last revised in 1997. I will provide only the information that interests us. Based on the document, the following mailboxes should exist and have the following purpose:

Business mailboxes:

info@ - Marketing Department, here you can find out brief information about the organization, products, services.
marketing@ - Marketing and sales interaction department.
sales@ - Sales department, product ordering and order information
support@ Customer support department, problems with the product or services.
abuse@ - Relationships with clients, the mailbox must always be working and valid, client complaints are sent here, including messages about "Inappropriate public behavior".

Working with the network:

noc@- Network Operations, network infrastructures.
security@ - Network security, notifications, alerts or queries.

Technical support for individual Internet services

postmaster@ - SMTP, ,
hostmaster@ - DNS,
usenet@ - NNTP,
news@ - NNTP, Synonym for USENET
webmaster@ - HTTP,
www@ - HTTP Synonym for WEBMASTER
uucp@ - UUCP,
ftp@ - FTP

Maillist service

(we won’t consider it, we’ll just list the main ones, there’s a whole galaxy of service names and a bunch of RFCs, for example RFC2369)
list@
list-request@

It seems to me that this RFC 2142 was approved during the heyday of the dot-coms, which means that the need for such agreements was very urgent. It was apparently assumed that employees should be able to automatically send mail to the corresponding well-known addresses and expect appropriate competent responses.

Thus, you should make aliases of these names to your “main” email, so that no one could, for example, open a usenet conference on your domain, or from the “sales department” bang with felt boots and subscribe system administrator entire network from the noc@ mailbox.

/etc/aliases

De facto standard for * nix systems is an agreement on postal names contained in the file /etc/aliases. Which is de jure based on RFCs and other documents for each individual service.
The paradigm for assigning mailboxes to people in *nix goes something like this: each username gets mailbox on workstation with the same name as his login. After creating a username in the system, you can already send and receive mail to your account. (there will be a “but” here: if root allows and MX is registered correctly). If you want to get a fashionable alias, contact the administrator, he will register it in /etc/aliases or anywhere else in the postal system.
The same goes for system services. There are a lot of backup names like , clamav@, www-data@, which correspond to system service accounts, in real life are not used by anyone other than these corresponding services and are mail aliases of the system user root, so we will not take them into account, because all significant names We already learned about network service boxes from the previous paragraph. Let's just add
root@

Modern Internet and other unspoken conventions for mailbox naming.

Together with you, we will try to find the most common names that domain owners reserve for themselves and use as administrative, business and personal contacts.
admin@
administrator@ (those who know a lot about this can add localized admin names in Windows, like administrador, administrateur)
user@
mail@
blog@
office@
job@ (and sometimes resume@ and hr@) - for sending and receiving job applications and resumes.
spam@ - sometimes it is used as an alias to abuse@ or postmaster@, for complaints about spam, obviously.
billing@ - for billing. K.O.
account@ - for accounting and account support.
[email protected]- the name of the box repeats the domain, obviously for aesthetics.
alex@, boss@ - feel free to fill in your first and last names and nicknames to eliminate the factor of social engineering when, for example, your name is Alexey, and your wife, knowing full well that you bought vashdomen.ru, receives from the mailbox [email protected] a letter of dubious content means that the attacker will not be trusted.
You can add something to this sheet.

Other than that, I know almost nothing about mail naming conventions in Windows systems, do they really exist?

Thus, by reserving all these names as aliases for your main mailbox on the domain, you will protect yourself, including from mailbox squatters and malicious use of mailboxes with “system” names. Also, all “official” correspondence regarding your domain that may come to system names will not go unnoticed. If you organize mail for the office, then similar agreements can be just as useful to you.

For forwarding. If, for example, the user has an address [email protected], but he needs an address [email protected]. In this case, you can make this address an alias to the main one, and all incoming mail will be collected in one mailbox.

Term extension alias sometimes used to refer to specific modes of email forwarding, thereby implying more general meaning the term alias of the postal address, that is, the address to which the message is sent in a simplified mode.

Usage

An email address alias can be created on the mail server. Each email address alias simply forwards emails for each of specified addresses. Email aliases are often used to create aliases for long or difficult to remember email addresses. Aliases can also be used to create common postal addresses such as [email protected] or [email protected]. IN UNIX-like systems aliases of email addresses can be placed in an alias file and look like: local-alias-name: adifferentlocaluser, anotherlocaluser, [email protected]

Management issues

A message that is sent through an email address alias retains the original sender and recipient information. If the message is blind carbon copy, then the recipient can tell whether the message was sent through an alias by analyzing the message header. However, the standard does not require the recipient of the message to be mentioned in the header. Thus, message recipients may not be able to reconstruct which email address was ultimately used by the sender to deliver the message to the mailbox.

Recipients who cannot trace which sender addresses were used cannot ask the sender to stop sending, since the sender likely will not be able to associate their current email address with one of the addresses used for sending. Even if users are able to find out the exact address used for sending, their mail client cannot provide convenient way send a response using the sender's address. In other words, the use of email address aliases is not reversible. This is especially true in a situation where the sender does not provide a reliable mechanism for a response in the body of the message. So, for example, information messages can be sent to a list of recipients, which requires significantly fewer resources than sending a letter to each recipient individually.

See also

Shipping (forwarding)

Wikimedia Foundation. 2010.

For each verified domain, you can set up an alias (receive emails from an address on another domain), select a default address, and create an address book with common domain contacts.

Using the Mail for Domain API, you can also assign proxies to the domain administrator, who can manage mailboxes for the domain, but not general settings.

Domain alias

This feature is useful for those who have more than one domain at their disposal. You can add an alias for any of your domains.

What is it?

If one of your domains is already connected to Mail for a Domain and has mailboxes on it, you can make the second domain its alias. This means that the mailbox of the main domain will also receive letters sent to a mailbox with the same name in the alias domain.

Example

If you make the domain yourdomain2.tld an alias to the domain yourdomain1.tld, to the address [email protected] you will also receive emails sent to [email protected].

How to connect a domain alias?

1. Go to page.
2. Select required domain from the list

Select an alias from the Domain Alias ​​list.

An alias can only be a domain without mailboxes that is already connected to Mail for the domain. If you do not have such domains, the drop-down list will be empty.

You can add an unlimited number of aliases for one domain.

Default address

You can make any of the mailboxes on the domain the default address. Letters sent to any non-existent mailbox in your domain will be sent to this address.

To make one of the mailboxes the default address:

1. Go to page.
2. Select the desired domain from the list (if several are connected).
3. Click the Set up domain link.
4. On the list Default address select the desired box.

General domain contacts

Email addresses belonging to the same domain can be combined into a common address book. When you fill out the To field, these addresses will be displayed as tooltips.

Note. Domain email addresses combined into a common address book are only available as tooltips. They will not be visible in address book with the user’s personal contacts in the Mail web interface.

To create general contacts, go to the domain settings and click the enable link next to the corresponding item:

Deputy administrators

Deputies can manage mailboxes and their settings, but do not have access to the domain settings and DNS records.

Substitutes can be added using .

Mail for a domain - beautiful e-mail address, indicating that it belongs to your domain. We can say that mail for a domain gives you individuality, since not everyone can create mail on a specific domain, for example site.ru, but only its owner. This article will discuss the process of registering and setting up this service.

Step 1. Connecting a domain

How to set up email for a domain?

First of all, you must create an account on Yandex. If you already have it, then go straight to the section. Enter your domain in the field and click on the button Connect domain.

Step 2. Confirm domain ownership

You will be given several options to verify domain ownership:

Choose the first, easiest option. You need to create a .html file with specified name and content and upload it to the root directory via FTP. Read more about ways to confirm domain ownership.

We are waiting for domain ownership verification.

Yandex does not scan domains instantly, so you will have to wait. The settings page will indicate what time the following check will take place:

If you did everything correctly, then after specified time you will see a message indicating that domain ownership has been successfully verified, and the domain status will change to Pending MX Records Installation.

Step 3: Set up MX records

In Yandex, you can configure MX records in two ways:

1. Delegate the domain to Yandex - in this case, setting up MX records will happen automatically, but the domain will be linked to Yandex, and not to hosting, so we use option 2:
2. Create a new MX record yourself through the control panel of your registrar/hosting provider with the following parameters:

• Subdomain name - @
• Record type - MX
• Data - mx.yandex.ru. (necessarily with a period at the end!)
• Priority - 10

With some domain registrars and hosting providers, for example 2domains, you can configure MX records automatically in your personal account/control panel.

If you did everything correctly, after a while your domain will connect and you will see the following message: Domain connected.

Step 4: Create a mailbox for the connected domain

After we have connected our domain to Yandex, we can create up to a thousand mailboxes!

In the My domains section, under our domain, select Add a mailbox

We register the mailbox login, set a password for it and click Add.

After adding there will be a message stating that new box added successfully.

Select our created mailbox and select Configure:

The following options are available to us:

• Change password,
• Block your mailbox
• Delete mailbox,
• Add a mailbox alias.

Let's take a closer look at the mailbox alias. Alias ​​is an alternative e-mail address for a specific mailbox. You can create an alias for a previously created mailbox. For example, you created [email protected], and added an alias to it [email protected]. Thus, if you send emails to [email protected], then they will still arrive at the address [email protected]. I think everything is clear.

And the last thing you need to do is complete pre-registration. Click at the very top of the Login to mail page, enter your login (you can do it without @domain.ru) and the password for the mailbox, the following page will appear:

Fill in all the data (First Name, Last Name, Gender, password recovery question and answer, e-mail to contact support (optional), Date of birth), enter security code from the picture and click Complete registration.

All! Now the mailbox is accessible through the Yandex.Mail web interface. And you can also mail program. It's very convenient!