Han is correct. This part differs Mercury from some other products, that in my view have misunderstood the negative impact a direct association with a maildrop and just one e-mail address. Defining the maildrops apart from the addresses has the following benefits out of a server standpoint:
- makes it much harder to try and harvest maildrop/password pairs as the maildrop name isn't public
- eases the teaching that a maildrop is a "box" that can be associated with more than just one address
- is syntactically correct in correlation to most e-mail clients, that state Username as the equivalent for a maildrop, and hold separate settings for name and address.
The only thing I think is missing, is, that since the association with an alias and a maildrop is possible, it would have been nice to, via a setting, allow or disallow authentication in all modules between aliases and their direct associated maildrop passwords - as well as a setting enforcing strong maildrop passwords. Hopefully that will come true some day for both NetWare, Windows integrated and stand alone operations of Mercury.
<P>Han is correct. This part differs Mercury from some other products, that in my view have misunderstood the negative impact a direct association with a maildrop&nbsp;and just one e-mail address. Defining the maildrops apart from the addresses&nbsp;has the following benefits out of a server standpoint:</P>
<UL>
<LI>makes it much harder to try and harvest maildrop/password pairs as the maildrop name isn't&nbsp;public</LI>
<LI>eases the teaching that&nbsp;a maildrop is a "box" that can&nbsp;be associated with more than just one address</LI>
<LI>is syntactically correct in correlation to most e-mail clients, that state Username as the equivalent for a maildrop, and hold separate settings for name and address.</LI></UL>
<P>The only thing I think is missing, is, that since the association with an alias and a maildrop is possible, it would have been nice to, via a setting, allow or&nbsp;disallow&nbsp;authentication in all modules between aliases and their direct associated maildrop passwords - as well as a setting enforcing strong maildrop passwords. Hopefully that will come true some day for both NetWare, Windows integrated and stand alone operations of Mercury.</P>