Sam Varshavchik wrote:

Sam and Gordon,

I think it is understood that based on the current code in courier that, even if there is an aliased domain set in hosteddomains, that you must again explicitly state this aliasing in the aliases file for addresses that are not mailboxes.

The need to define the domain alias twice seems redundant and is a bit confusing:

1) hosteddomains sample

domainprimary.com domainalias.com<tab>domainprimary.com

2) aliases sample would need:

jo...@domainprimary.com: some...@gmail.com jo...@domainalias.com: some...@gmail.com

It would be much simpler from an administration perspective for the aliases file to follow the global setting for domain aliasing as set in hostedomains, thus only needing this in the aliases file:

jo...@domainprimary.com: some...@gmail.com

...

This same need for redundancy seems to also be necessary in regards to the global setting to be case-insensitivivty.

For mailboxes, they are case-insensitive, but for aliases... it seems to be necessary to include options for likely capitalization nuances. For instance some strange person my decide to send email to MrJ...@domain.com. If mrj...@domain.com is a mailbox it gets delivered fine, but if it is an alias you have to define both of these in the aliases file for delivery to succeed for the different capitalization nuances:

mrj...@domain.com MrJ...@domain.com

...

Now, what I truly wish is that I was educated in programming enough at this point to figure out how to update the code to do this... or whether it was just meant to run this way for some reason I'm not understanding and thus needing to deal with this redundancy is necessary.

Thanks,

Charles