Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a MOSS 2007 standard farm comprised of a WFE, an indexing server, and a SQL 2005 database server. The web app is being served on port 80 (http) to an ISA server where it is SSL'd. I have AAMs to change the URLs from http to https.

My problem is with the emails that are generated by lists within the MOSS farm. The urls inside the emails are random between http:// and https://. I can't find a pattern to figure out what the issue is. The same thing happens from different lists in different sites all over the farm. The majority of the emails sent out are incorrect.

Update: I figured out that the alerts are https://, which is correct, but the email notifications are wrong.

I may be using incorrect syntax, so what i mean by alerts is from a list when you click actions, alert me. And notifications are what gets sent when an item is assigned to you.

share|improve this question
up vote 0 down vote accepted


I believe that e-mails are sent with links that use the default zone URL of the associated web applicaiton housing the site collection ( -- see the section called "Configuration requirements of the Default zone").

You said you weren't seeing a pattern in the links. Are default zones consistent across web applications? Are you observing something different?

share|improve this answer
Currently I have a single web app. The only part that is wrong is the protocol. – Bob Sep 9 '09 at 15:40
This does seem to be the case. However it only works for lists created after the default was changed. The ones that existed previously still send assignment notifications with the wrong protocol and alerts with the correct protocol. – Bob Sep 14 '09 at 4:27
Ah, so if I'm understanding correctly ... the default zone was changed after some alerts had been setup? Since the two tables that contain alert information (in the content database) maintain URL references that are established at alert setup time, this makes sense. The alerts that were established prior to the change would be broken. This article may be of use to you: It talks about modifying alerts following a web application move; the situation is different, but the outcome matches your scenario. I hope it helps! – Sean McDonough Sep 14 '09 at 16:23

The URL that email Alerts from lists will use are stored at the time they are created and use the URL that you were browsing to at that time - it doesn't pick up the URL from a particular zone AFAIK.

(Administrative alerts such as quote ones do, but these are different to list notification alerts)

In your case I believe that because you are using ISA server to do the SSL 'termination' it looks like this :-

SharePoint <=== HTTP ===> ISA <=== HTTPS ===> User

Whilst the user see's HTTPS as far as SharePoint knows its using HTTP and that's the URL that gets assigned to the alert.

skelly's blog article that Sean ref's talks about how to change these URLs using code.

There is also a updatealert command added in to STSADM by the Administration Toolkit that can do this - perhaps you can run this (nightly as newly created alerts will be wrong also?) to update any alerts

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.