>Dean Scott ([EMAIL PROTECTED]) wrote:
>> Although the documentation indicates that the mail attribute is not
>> multivalue, what breaks with qmail as a result of the mail attribute
>> being set to multiple values?
>
> The messages will bounce.
That's what I thought too, but having both [EMAIL PROTECTED] and
[EMAIL PROTECTED] seems to work fine. While I would prefer to "do the
right thing" and just have one, it seems to be difficult (see below).
>
>> I know about the mailalternateaddress field but that will not work in
>> this case. So, does setting this break anything or is it simply bad
>> grammar to do so?
>
>
> What are you attempting to do? Maybe if you explain your situation a
> little better, somebody can make a good suggestion.
Well, we want users to be able to log into their IMAP email using either
@bluefrognet.net or @bluefrog.biz; currently only bluefrognet.net works,
but if we add in a second one with @bluefrog.biz everything works fine
(at least on the accounts we've tried it on). My real concern is that if
we deploy this solution we might find it breaks elsewhere.
Currently we have the other extension (.biz) as a mailalternateaddress
and while receiving works fine, logging into IMAP does not.
Thanks,
Dean
>
> --
> mike
