1

Topic: Email tag

It would be good if in I will bake added such possibility: name#project_a@mail.com or name@mail.com/company/project_a where project_a and company are set by the user arbitrarily in soot-vii with that where soap is used now one and too soap can be used on different resources and dispatching of arrived mail will be fulfilled strictly on tags, without any unreliable analyses of the sender and a subject in general it would be possible to generate so to say unique addresses necessarily at the same time if your soap flows away to spamers will know from what server, it solves nothing but it is possible to scold them

2

Re: Email tag

Hello, Kingofastellarwar, you wrote: K> it would be good if in I will bake added such possibility: K>name#project_a@mail.com K> at the same time if your soap flows away to spamers will know from what server, it solves nothing but it is possible to scold them It and now it is possible, use a plus: ` name+project_a@mail.com `: https://gmail.googleblog.com/2008/03/2- … -your.html

3

Re: Email tag

Hello, Kingofastellarwar, you wrote: K> or K> name@mail.com/company/project_a In XMPP peeped?

4

Re: Email tag

Hello, DOOM, you wrote: DOO> Hello, Kingofastellarwar, you wrote: K>> or K>> name@mail.com/company/project_a DOO> In XMPP peeped? Not, itself invented not to suffer with sorting of letters more precisely to organize strict sorting first of all for potential  managers into which it would be possible to integrate mail and to have accurate  arriving letters with to the specific project

5

Re: Email tag

Hello, Kingofastellarwar, you wrote: K> Hello, DOOM, you wrote: DOO>> Hello, Kingofastellarwar, you wrote: K>>> or K>>> name@mail.com/company/project_a DOO>> In XMPP peeped? K> not, itself invented not to suffer with sorting of letters But there really such is. One measurement truth... Type user/home@jabber.ru, user/work@jabber.ru

6

Re: Email tag

Hello, Kingofastellarwar, you wrote: K> it would be good if in I will bake added such possibility: K>name#project_a@mail.com K> or K> name@mail.com/company/project_a K> where project_a and company are set by the user arbitrarily in soot-vii with that where soap is used About "+" in mail already Qbit86 wrote. I will add that it twenty not less exists years in implementations sendmail, exim and many other things. In a case sendmail, ~/.forward + defines rules for  the receiver, ~/.forward + $ {tag} for a specific tag, and after them ~/.forward - default if any of previous did not work. Happen and the parametrized circuits (for example, in qmail) - the type address $ {const} - $ {var} turns to search of the forward for $ {const}, and by its call value $ {var} is transferred through a process surrounding. In qmail it is actively used (though and restrictedly) for VERP. K> now one and too can be used soap on different resources and dispatching of arrived mail will be fulfilled strictly on tags, without any unreliable analyses of the sender and a subject Here with implementation of it on big  already problems. In case of mailings titles do not change more often. The real address of the receiver is only in an envelope, and it is necessary, that means allowed the filter on an envelope. And with it at the majority the strong problems - filters are projected counting on the full teapot, instead of the clever user. Gmail the last some years the filters only spoiled, breaking already working. K> in general it would be possible to generate so to say unique addresses necessarily K> at the same time if your soap flows away to spamers will know from what server, it solves nothing but it is possible to scold them Here from it protection very feeble - spamers learned to cut off for a long time tags from such address and to substitute at random the arbitrary. Rescues only rare application of this feature but if will apply is more often again recall old abilities. Absolutely different names of boxes - are more effective.

7

Re: Email tag

Hello, Qbit86, you wrote: Q> It and now is possible, use a plus: ` name+project_a@mail.com `: https://gmail.googleblog.com/2008/03/2- … -your.html Only at Google, maybe, at some providers. It not a standard functional.

8

Re: Email tag

Hello, Baudolino, you wrote: B> Only at Google, maybe, at some providers. It not a standard functional. In spite of the fact that the behavior "+" in a local part email is not standardized RFC, almost all modern mail servers process it was uniformly. If any server processes it not so it is occasion to ask system administrator to correct similar behavior.  on Yandex. A disk