double primary SMTP Adress in proxyAddresses
bbab
Some of our students use their own external mailaccounts instead of our
exchangemailboxes. So first, we forwarded their mails by the mailNickname and
the targetAddress attribute to teir external addresses. Because of some
problems and our decision to be more flexible, we removed the targetAddress
attributes and created mailboxes on one of the two exchangeservers for all
students. We told our students, how to create a rule within the OWA, to
forward mails to their external mailboxes (if neccesary).
This seemed to work fine, but several students told us, that they dont get
mails in their external mailaccounts. I checked the accounts of these
students and found, that these accounts now have two primary SMTP addresses
in their proxyAddresses attribute, the regular one (by RUS) and the
forwarding address is set as a primary address, too.
So the external address is treated as if it was local and the mails are
stored in their exchangeservermailbox instead of being forwarded to the
external mailaccounts of these students. Wiered.
Any ideas, what could have happened?
Rich Matheisen [MVP]
[ snip ]
>This seemed to work fine, but several students told us, that they dont get
>mails in their external mailaccounts. I checked the accounts of these
>students and found, that these accounts now have two primary SMTP addresses
>in their proxyAddresses attribute, the regular one (by RUS) and the
>forwarding address is set as a primary address, too.
The only way I've ever seen a user get two (or more) primary SMTP
proxy addresses is when someone uses a tool like ADSIEDIT, LDP,
LDIFDE, or some script thy've written. It has notheing to do with any
Outlook rules.
To fix the problem, use ADSIEDIT. Edit the proxyAddresses property of
the user and set one (or more) of the SMTP proxy addresses to use a
lower-case "smtp:" type. Then you can use ADUC to make whatever other
changes you want to make.
My guess is that when you changed the account(s) from a mail-enabled
user to a mailbox-enabled user you didn't use the ADUC to do the work.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.p...@getronics.com
Or to these, either: mailto:h.p...@pinkroccade.com mailto:melvin.mcp...@getronics.com mailto:melvin.mcp...@pinkroccade.com
bbab
"Rich Matheisen [MVP]" wrote:
> The only way I've ever seen a user get two (or more) primary SMTP
> proxy addresses is when someone uses a tool like ADSIEDIT, LDP,
> LDIFDE, or some script thy've written. It has notheing to do with any
> Outlook rules.
thank you for your quick response.
I removed the targetAddress attribute with ADSIEDIT. Then i used the ADUC to
create the mailboxes, no script and no ADSIEDIT.
The problem occured to only some of our 1500 Students (~10) and only to some
of the students with external mailboxes. The second primary addresses are the
external targetaddresses, so i thougt, that something with the rules could be
the cause of this wierd problem. Or, maybe, something leftover from the
targetAddress attributes creating the trouble.
I will remove the faulty primary addresses with ADSIEDIT, but i fear, that
they will come back.
Rich Matheisen [MVP]
>
>
>"Rich Matheisen [MVP]" wrote:
>
>> The only way I've ever seen a user get two (or more) primary SMTP
>> proxy addresses is when someone uses a tool like ADSIEDIT, LDP,
>> LDIFDE, or some script thy've written. It has notheing to do with any
>> Outlook rules.
>
>thank you for your quick response.
>
>I removed the targetAddress attribute with ADSIEDIT.
Which doesn't remove the primary SMTP proxy address from the
multi-valued proxyAddresses property or from the mail property. Using
ADSIEDIT is a lot like using Regedit or writing a program in the C
language -- it does exactly what you tell it to, even if it's wrong.
>Then i used the ADUC to
>create the mailboxes, no script and no ADSIEDIT.
>
>The problem occured to only some of our 1500 Students (~10) and only to some
>of the students with external mailboxes. The second primary addresses are the
>external targetaddresses,
That's correct.
>so i thougt, that something with the rules could be
>the cause of this wierd problem. Or, maybe, something leftover from the
>targetAddress attributes creating the trouble.
"Left over" is correct. But it was you that left it over. :-)
>I will remove the faulty primary addresses with ADSIEDIT, but i fear, that
>they will come back.
If they do then it's another manual activity that caused it to.