Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Incoming Email Issue

  Asked By: Santosh    Date: May 22    Category: Sharepoint    Views: 3596

I have a medium level farm where i have enabled a basic incoming email
functionality. An SMTP send connector has been setup and an MX entry has also
has been setup to route email traffic for my domain to my web front end server.
I have done the following configuration -

* I have created a local alias in the SMTP virtual directory of the WFE to
match the domain name.
* My mailroot and drop folder in the WFE has appropriate permissions. My
central admin and sptimer service runs under the same account which is an admin
account and have full control access to this folder.
* The drive has 96 GB of free space.
* Port 25 is open, I have checked using Telnet. (Though i was not able to
send an email)
* I have enabled SMTP logging.
* Incoming emails are enabled at the farm and the list/library level.

I am unable to send email to my email enabled lists. The error that I get is
error code 429 in my system logs that say - "Virtual Server Invalid Mail Queue
Directory: The specified mail queue directory is not valid. Cannot start the
SMTP Service."

In my SMTP log I see the following group of errors -

22:50:58 EHLO - 250
22:50:58 MAIL - 250
22:50:58 RCPT - 250
22:50:58 BDAT - 452
22:50:58 QUIT - 240

Can anybody help me understand what I might be doing wrong?



8 Answers Found

Answer #1    Answered By: Alan West     Answered On: May 22

Have you confirmed that the incoming  mail items are actually appearing
in the dropbox location for incoming email  you setup  in Central
Administration? Have you checked  the ULS log for an errors/warnings?

Answer #2    Answered By: Maribel Todd     Answered On: May 22

What email  system do you have?

I have had no issues with Exchange but have come across a few quirks
when trying to get it to work with Notes/Domino

With Exchange I had the same problem until I allowed sharepoint to
create contact objects on the fly in AD. Once that was configured
the mail would actually go into the library. (before I was just
getting it in the drop  box and it would sit there)

Answer #3    Answered By: Akshara Negalur     Answered On: May 22

We have exchange as the email  system. I have a basic  option without configuring
the AD container to hold the contacts. The drop  folder is configured in my
central admin  and I have verified that it has enough disk space  and all
authenticated users have full  control over the folder.

The emails  are not appearing in the drop folder. Please see the SMTP logs below
- I get an error  452, indicating bad data. I tried to send  an email telnet
<server> 25, but even that failed - error code  452 4.3.1 "Out of memory" error.

Answer #4    Answered By: Timothy Davis     Answered On: May 22

Did you manage to get this to work? Let me know and we can deal with
this accordingly. There is a permission that needs to be added to the
OU containing the contacts and requires delegation.

Answer #5    Answered By: Adya Deshmane     Answered On: May 22

Also, does IIS SMTP coexist with Exchange on the same box?

Answer #6    Answered By: Siobhan Waller     Answered On: May 22

No, IIS SMTP is unavailable on machines running Exchange.

Answer #7    Answered By: Lorenzo Steele     Answered On: May 22

That all depends doesn't it? Say you install the IIS SMTP service  for
email functionality of a SharePoint site and then later install Exchange
on the same box. That could cause a conflict of the two SMTP services
in that scenario right? I know I have encountered this in the past and
knew IIS SMTP could be a problem on the same box as Exchange in that
scenario as mentioned here
/92f4d389-f30e-4e4a-a14a-bb5122ad71bf/> . The post is as follows:

Maybe to late but i have an idea of the problem.

When installing Exchange server  it takes control  over and reconfigures
the SMTP service installed by IIS.
the reconfigured version doesn't work with MOSS.

If you reinstall the IIS SMTP service over the Exchange version than
Exchange will not work properly because it needs the reconfigured

Only solution i know to this problem (if you reinstalled IIS SMTP
service over Exchange SMTP service) is to reinstall Exchange

Step by step guide:

It seems like MOSS and Exchange needs to be on separate servers to use
all SMTP functions.

Answer #8    Answered By: Divakar Naik     Answered On: May 22

There is only a conflict if you manually install IIS SMTP over the top
of Exchange which is unsupported for the reasons in that post. It's not
recommended that you run both MOSS and Exchange on the same machine in
general for a variety of reasons, but it is possible. What you end  up
needing to do is use Exchange for everything and skip IIS STMP
completely. It's possible using Exchange 2007, but it involves setting
up the appropriate send  connector rules to allow anonymous sending from
SharePoint, and a receive connector  to drop  mail intended for Incoming
Email to a dropbox location. Exchange 2003 is only capable of the
sending portion, it doesn't have the necessary pieces for dropping
incoming email  in a dropbox format that MOSS/WSS3 understand.

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