Jason L Tibbitts III wrote:
> I'm having some trouble explaining in a succinct manner how aliases (not
> MTA aliases) work. I don't suppose the concept is terribly complicated,
> but if I'm having trouble explaining it then you can be sure that users are
> going to be bewildered.
>
> So, how would you describe this to a user?
I would explain it as a secondary address. Perhaps with a simple example of
why it would be useful.Something like...
Aliases are a way to register a secondary email address with the majordomo
server. This allows the server to identify you from all your email addresses.
> Notes: aliases are a per-list concept. This really simplifies things
> because aliases go away when you unsubscribe, and there are very delicate
> restrictions on when you can alias and when you can't. Chains of aliases
> are absolutely not allowed, and you cannot alias one subscriber to another.
> You cannot add an alias to an address which is not subscribed, nor can you
> alias away from an address that is subscribed (else you couldn't
> unsubscribe without first removing the alias).
>
> I have tried to come up with a way to make aliases global, but I just can't
> find a way to do it that even approximates the clean solution I use now.
> At this point I don't plan on worrying about it any longer.
It depends on how you are storing list/user information. Unfortunally, I
havent been able to check into that was well as I want. The only way I could
think of presently is to save user-specific information in a seperate db
somewhere. But Im not sure how well that would work for you. I plan to really
get into the info storeing scripts soon as I work on my Majordomo LDAP
project, so if someone can come up with a better idea, let me know.
-Jeff
References:
|
|
