Email Enabled Document Library Doesn't Work When "Accept e-mail messages based on document library permissions" is selected

Question

I have created a document library and enabled it to recieve email.  If I have accept from any sender it works fine, but if I change that to accept based on permissions it never gets the email.

To try and figure out why this is not working, I went to the drop folder and captured the email that I was trying to send.  I have noticed that for some reason "prvs=<RandomNumber>=" is being added to the x-sender field.  so it looks like:

x-sender: prvs=0498381afe=[e-mail]

if I remove that and make it look like:

x-sender: [e-mail]

Then drop the eml file back in the drop folder it works. Does anybody have any ideas?

Thanks,

Matt

Answer 1

Hi Matt,

More than likely you may have an e-mail server modifying the x-sender header of the mail that is causing the issue. When MOSS receives an email, it takes the whole x-sender value when attempting to resolve the sender account. When you configure the incoming e-mail to use "Accept e-mail messages based on document library permissions", SharePoint sends an LDAP query to the DC to attempt to resolve (mail=prvs=<RandomNumber>=[e-mail]) as well as perform a SQL query against the content database to locate a record that matches up with the email address. If you analyze the ULS logs or capture netmon trace when the timer service processes the incoming email, you should be able to see this and see an exception that it cannot resolve the user. This is why when you configure incoming email to accept e-mail from any sender you do not encounter this issue.

I would suggest start looking at each of the mail servers that are responsible for the delivery of the email to determine which one might be modifying the x-sender header. In case of Exchange 2007 servers  the pipeline tracing can help to determine which server is responsible for the issue. (This way we can catch and examine the letters as received by the server, thus can be determined at which server the x-sender value gets changed)

How to Enable Pipeline Tracing

http://technet.microsoft.com/en-us/library/bb125018.aspx

Using Pipeline Tracing to Diagnose Transport Agent Problems

http://technet.microsoft.com/en-us/library/bb124238.aspx

---

Adam Rudell | Technical Support Lead | SharePoint Technologies | Microsoft Corporation

Answer 2

Arudell,

Thanks for the reply.  After I posted this I finally got in touch with the exchange server admin and had him take a look at it.  It turns out we have a virus scanner (Proof Point) that was adding this to the x-sender field. 

Thanks,

Matt

Answer 3

Good to hear! Glad you were able to get it resolved!

---

Adam Rudell | Technical Support Lead | SharePoint Technologies | Microsoft Corporation