That appears to be a linguring email address policy, possibly from an Exchange migration from an earlier version. Two things you can do here, you can either add the SMTP address of what is in your default policy or delete this entry within ADSIEdit. I would use the later as a last resort and make sure you copy or screen shot all the attributes that have values in case you need to replace this.

One of the warning messages you received earlier suggests this policy has other things wrong with it than just the gatewayProixy address missing. But lets start with adding the gatewayProxy address and go from there.

I am trying to figure out how to 'FIX' the 'primary SMTP E-mail address' for the 'template'.

The exchange server didn't even list anything for 'Get-EmailAddressPolicy'. I added one - thinking the 'default' had somehow been deleted/corrupted or missed, but it had no effect on the error.

The information I have read says I need the 'Accepted Domain' 1st, before I can assign an 'EmailAddressPolicy', but I'm in a catch-22 (and really frustrated and ticked off after 3 days of useless searching.

My experience with Exchange 2010 has been horrible, I feel like I get kicked everytime someone mentions anything about email.

In that location of ADSIEdit, you are looking in the "Default Policy" properties (double click default policies) correct?

If so click the "Filter" button and then uncheck the "Show only attributes with values". Then scroll through the list to "gatewayProxy" and double click that. This will show you the values for that property.

'..correct for our environment' - well, no. We use [firstname][lastname]@domain.com; with no '.', so there wasn't a selection for that in the WIZARD. I just picked the %m so there would be A policy, so I could add the 'Accepted Domain'; I didn't 'apply' the policy.

My understanding is that by not applying the policy, no existing addresses will be changed or added.

So you have two that are in bold? This is an issue as the bold defines the default, if two of them are selected in bold then it means two are default which can't happen. You may need to remove one of them in bold, save the template (through the wizard) and then try to add the additional one.

I don't really give a rats-behind about the email policy - it is all about the 'ACCEPTED DOMAINS'.

The Exchange Server will not allow me to add an Accepted Domain. The error message says that "The e-mail address policy object doesn't have a primary SMTP E-mail address specified in the template.", so I went to see what the 'policy' was, and there wasn't a policy at all.

I created a policy called 'Default Policy' and assigned 'All Recipient Types', and the %m@[companydomain].com as the email address.

None of this has had any affect on the Accepted Domain, and I continue to receive the same error message.

OK, I understand, but I first need to get a feel for your environment, and without the policy, you can't add the accepted domain. So, now that you have added the policyu, try to restart the Exchange management console and then try to add the accepted domain again. If it gives the same error, navigate to the location in ADSIEdit from above, open the "default policy" and then scroill down to the gatewayProxy. Double click that and see what is listed in there.

That appears to be a linguring email address policy, possibly from an Exchange migration from an earlier version. Two things you can do here, you can either add the SMTP address of what is in your default policy or delete this entry within ADSIEdit. I would use the later as a last resort and make sure you copy or screen shot all the attributes that have values in case you need to replace this.

One of the warning messages you received earlier suggests this policy has other things wrong with it than just the gatewayProixy address missing. But lets start with adding the gatewayProxy address and go from there.

The default policy is created when you install Exchange. The question is, who deleted the default policy, and why is the "

E-mail Address Policies" not showing in the exchange management console or the management shell. Unless adding the address did in fact now cause it to show up. If it did, then great we know the issue was the missing gatewayPolicy address. If it didn't, then I suspect more may be wrong with that policy than meets the eye.

If you are comfortable deleting the default policy you created then by all means do so, but if there are other issues, you could use the default policy against your email address policies do do a comparison side by side in ADSIEdit. Open both in ADSIEdit, then change the filter to "Only attributes that have values". This will give you a glance of anything default in Exchange that might be missing in the one that wasn't showing up and give you a chance to correct them before it causes more issues down the road.

No problem, and it might be better to eliminate the one that doesn't show up, taking note of all settings and then creating a new default policy as you already did with the wizard and entering in the proper information. The wizard will make sure all the proper attributes for Exchange 2010 are added. Like I said, the one that doesn't show up will continue to give you headaches, such is the error you received earlier for,

That warning is telling you there are missing attributes in that policy.If you do decide to eliminate the none existant one from ADSIEdit and make a new one that mimics that one, I would do this after hours, as you are essentially going to have to make a new 'interim' policy with bogus info you don't want to take over before you can eliminate the bad one, then add a new default policy with the proper settings you do want. When you do this, it applies the policy to all email recipients which will more than likely cause major issues until the process is complete (new default, then eliminate the interm policy).Hope that makes sense, it's a bit confusing and will probably take some investigating on your end to determine how to exactly tackle the issue, but I wouldn't let it sit by the wayside on this one.

Good luck!-Jay

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.