tonix (Antonio Nati) wrote:At 25/07/03 25/07/03 -0400, Jeff Hedlund wrote:Today it is alias-bypass-the-processing-for-that-account.An alias is another name for that account, therefore it should be processed as if it were that account. It's not an alias-bypass-the-processing-for-that-account. :)
The personal interpretation of what is an alias is personal, so I appreciate your opinion, but mine is different.
I have customers with [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] as "real" users, and an alias like [EMAIL PROTECTED] that writes directly in the Maildir of the before said "real" users.
So if user name1 wants to forward his mail to a wireless device, he won't get any sales@ mail, which is inconcistent.
If they needed that, they would use a forward.
Aliases should follow the same rules as the end account, they are _aliases_ -- different names for the same account(s).
Again, this is your opinion. And you cannot make an opinion a forced choice in a project wide as vpopmail/qmailadmin.
Each one of them receives a copy of the message, and no "personal" autoresponders are sent back to messages going to [EMAIL PROTECTED]
Actual way aliases work for them is very good.
What would be more appropriate in this situation is to create a mailing list called sales@ that is closed to subscription and anyone can post to. Subscribe name1, name2, etc to that list. They will receive all mail to [EMAIL PROTECTED]
Wow, such complication for a so simple situation!
If one needs to set a vacation reply, it won't go out on the list (because the autorespond program will not deliver with a mailing list header is present). If they need to forward their mail, they will get the mail as they should.Simply, if you don't want your customers using aliases, put "maxaliases 0" in .qmailadmin-limits, and they will always use forwards.I think it would be enormously confusing for users if they had an alias setup for there account, and later decided to forward their email to a remote account, only to find that emails sent to the alias are not forwarded.
You already have an option, why cutting that possibility to other people who want "true" alias and "true" forwards?
I think your definition of a "true" alias is skewed.
Question of preferences...
Anyway, I'ld like that "elimination" of aliases would be made on a parameter base, the best would be to have one line in .qmailadmin-limits, to be added if alias has to change behaviour.
Jeff --
/\ /\ .. .. .. [EMAIL PROTECTED] / \/ \ a t r i x . . . . . . . (770) 794-7233 s o f t w a r e i n c .. .. .. http://www.matrixsi.com
------------------------------------------------------------
[EMAIL PROTECTED] Interazioni di Antonio Nati
http://www.interazioni.it [EMAIL PROTECTED]
------------------------------------------------------------