Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Alert Email Problem

  Asked By: Willis    Date: Nov 23    Category: Sharepoint    Views: 1431

We are getting any error when our portal server tries to send email notifications. The Apl,llication event log shows:

Event Type: Error
Event Source: SharePoint Portal Alert Service
Event Category: None
Event ID: 155
Date: 7/6/2005
Time: 8:30:55 AM
User: N/A
Computer: [ServerName]
Corrupted Message: There may be a problem with one or more values of the email headers.

<More information is available in the diagnostic logs on the Configure
Diagnostic Settings page in SharePoint Portal Server Central Administration.>

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 41 00 70 00 70 00 44 00 A.p.p.D.
0008: 6f 00 6d 00 61 00 69 00 o.m.a.i.
0010: 6e 00 3a 00 20 00 53 00 n.:. .S.
0018: 50 00 53 00 4e 00 6f 00 P.S.N.o.
0020: 74 00 69 00 66 00 69 00 t.i.f.i.
0028: 63 00 61 00 74 00 69 00 c.a.t.i.
0030: 6f 00 6e 00 53 00 65 00 o.n.S.e.
0038: 72 00 76 00 69 00 63 00 r.v.i.c.
0040: 65 00 2e 00 65 00 78 00 e...e.x.
0048: 65 00 e.

When I look at the SPSNOTIFIICATIONSERVICE.Log it contains:

07/06/05 08:30:54:672 UNK 00000000 00000B8C The delivery channel:"Email" was unable to send the specific alert notification. Notification details:{Seed Owner=1608ab78-2688-4f62-b82d-68bdb1c2c417 TypeId=AlertResultNotification SeedValue=766;1;Jul 6 2005 12:30:01:830PM Tag=1} Portal site details:{site=ATSC Test id=b95de23d-10a5-48b7-9960-732b6893fbe4} Exception information: Microsoft.SharePoint.Portal.Alerts.CorruptedMessageException: Channel:Email failed to send the message:There may be a problem with one or more values of the email headers. Email Headers: X-AlertTitle = =?utf-8?B?QXJlYTogU3VwcG9ydCBEaXJlY3RvcmF0ZW==?= ; X-AlertWebSoap = =?utf-8?B?aHR0cDovL2V1c3RhMDI3MjAwNDoxMDIvX3Z0aV9iaW4vb3V0bG9va0FkYXB0ZXIuYXNteH==?= ; X-AlertWebUrl = =?utf-8?B?aHR0cDovL2V1c3RhMDI3MjAwNDoxMDIv?= ; X-AlertServerType = SPS ; message-id = <3BD50098E401463AA22837784849392741@...........> ; Reply-To = .....................; To = ............................. ; X-AlertId = b95de23d-10a5-48b7-9960-732b6893fbe4:b95de23d-10a5-48b7-9960-732b6893fbe4:1 ; From = =?utf-8?B?QVRTQyBUZXN0?= <.................................> ; ---> System.Web.HttpException: Could not access 'CDO.Message' object. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x8004020F): The server rejected one or more recipient addresses. The server response was: 550 Relaying is prohibited --- End of inner exception stack trace --- at ............

I replaced the identifiable parts of the message-id, Reply-To =, To =, and From = fields with ................... in this posting. The key thing I see is the 'The server response was: 550 Relaying is prohibited' I have added the portal server to the 'Grant relay list' on the SMTP server but still no luck.

Any ideas?



3 Answers Found

Answer #1    Answered By: Horace Coffey     Answered On: Nov 23

You need to also make sure the mailhost you’re connecting to allows the domain of the recipient. The error  specifically mentions that.

The server  rejected one or more recipient addresses. The server response was: 550 Relaying is prohibited

So check your config files that A) it will relay for your portal  server and B) it will relay for the domain of the recipient.

In sendmail/postfix this is done in mailertable and access files. What MTA is your mailhost?

Answer #2    Answered By: Rigoberto Beard     Answered On: Nov 23

Based on your comments we discovered that the mail server  at the receiving end was blocking any mail from the our specific SMTP server even though the users are valid on that server. We solved the problem  by using one of our other SMTP servers until we can resolve why the destination is refusing to accept traffic from the other server.

Answer #3    Answered By: Alphonso Mckay     Answered On: Nov 23

One other thing you might check about your MTA is anti-spam features where it does a reverse lookup and it checks that the server  sending the mail as a domain actually reverse-lookups as that domain. For example, you might be company.com on the outside, but your internal domain is company.local or company.biz, and you’re sending email  as spsadmins@... but your internal sps server reverse lookup is company.local and your MTA sees that as spam.

Or maybe you have SPF (sender policy framework) enabled and haven’t specified your SPS server as being allowed to send  mail as your domain.

Didn't find what you were looking for? Find more on Alert Email Problem Or get search suggestion and latest updates.