Undeliverable mail when sending from Windows Mobile 5 device

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

The problem is with WM5 devices connected to my SBS2003 server with Direct
Push email getting undeliverable error messages. When sending an email from
the Vario MDA PDA to mat.hadden@xxxxxxxxxxx I get this reply,

Your message did not reach some or all of the intended recipients.

Subject: test

The following recipient could not be reached:

mat.hadden@xxxxxxxxxxx on 19/08/06 21:10

The e-mail account does not exist at the organization this message was sent
to. Check the e-mail address or contact the recipient directly to find out
the correct address.
<mailhost.hadden-crespo.co.uk>

When I read the same NDR message on the PC inside the the SBS 2003 network,
the body reads differently, it says

Your message did not reach some or all of the intended recipients.

Subject: hello
Sent: 19/08/2006 22:30

The following recipient(s) could not be reached:

mat.hadden@xxxxxxxxxxx on 19/08/2006 21:30
You do not have permission to send to this recipient. For assistance,
contact your system administrator.
<mailhost.hadden-crespo.co.uk #5.7.1 smtp;554 5.7.1 Appears to be spam
(qid: k7JKUH8M007832, SPF: 0), caught on imbaspam-ss08>

When sending to the same email address from the office PC, it is received
without any problems (and no NDR's) It seems to think that when the message
is sent from the PDA it is spam, but when sent from the office PC it is OK.
Both methods are being sent from the same SBS user. When rolling out the
Windows Mobile 5 devices, I followed the document
"Deploying_WM5_with_SBS2003.doc" microsoft document to the letter.

As a test I have sent 2 emails from this same user, both to my private email
address, one via the PDa and one via the office PC. I can see from the
routing details that they look very different.

Here is the details of the mail sent from the office PC.

Return-Path: <trish.hadden@xxxxxxxxxxxxxxxxxxx>
Received: from aamtain03-winn.ispmail.ntl.com ([81.103.221.35])
by mtain06-winn.ispmail.ntl.com with ESMTP
id
<20060819215931.VRJE22629.mtain06-winn.ispmail.ntl.com@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
for <mat.hadden@xxxxxxxxxxxx>; Sat, 19 Aug 2006 22:59:31 +0100
Received: from mailhost.hadden-crespo.co.uk ([80.176.149.224])
by aamtain03-winn.ispmail.ntl.com with ESMTP
id
<20060819215931.JMIZ8509.aamtain03-winn.ispmail.ntl.com@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
for <mat.hadden@xxxxxxxxxxxx>; Sat, 19 Aug 2006 22:59:31 +0100
Content-class: urn:content-classes:message
Subject:
Date: Sat, 19 Aug 2006 22:59:27 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C6C3DA.BDC79407"
Message-ID:
<02E56FFBFA4BC3479B2D6623C7A19AA90286D0@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
X-MS-Has-Attach:
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-TNEF-Correlator:
thread-index: AcbD2r1r75+IQHfdSb+kSIwbxNi2hQ==
From: "Trish Hadden" <trish.hadden@xxxxxxxxxxxxxxxxxxx>
To: <mat.hadden@xxxxxxxxxxxx>

And here is the details of the email sent from the PDA.

Return-Path: <trish.hadden@xxxxxxxxxxxxxxxxxxx>
Received: from aamtain04-winn.ispmail.ntl.com ([81.103.221.35])
by mtain01-winn.ispmail.ntl.com with ESMTP
id
<20060819215831.SNTY22645.mtain01-winn.ispmail.ntl.com@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
for <mat.hadden@xxxxxxxxxxxx>; Sat, 19 Aug 2006 22:58:31 +0100
Received: from mailhost.hadden-crespo.co.uk ([80.176.149.224])
by aamtain04-winn.ispmail.ntl.com with ESMTP
id
<20060819215831.HKRB19622.aamtain04-winn.ispmail.ntl.com@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
for <mat.hadden@xxxxxxxxxxxx>; Sat, 19 Aug 2006 22:58:31 +0100
Received: from 192.168.16.2 ([192.168.16.2]) by server01.HaddenCrespo.local
([192.168.16.2]) with Microsoft Exchange Server HTTP-DAV ;
Sat, 19 Aug 2006 21:58:27 +0000
MIME-Version: 1.0
From: "Trish Hadden" <trish.hadden@xxxxxxxxxxxxxxxxxxx>
Subject:
Message-ID: <000501c6c3da$99a28d9d$0210a8c0@xxxxxxxxxxxxxxxxxx>
Content-Type: text/plain;
charset="iso-8859-1"
Date: Sat, 19 Aug 2006 22:58:26 +0000
Importance: normal
X-Priority: 3
To: <mat.hadden@xxxxxxxxxxxx>
thread-index: AcbD2pmiig5YBFNiRdKTyvfeGwmF5g==


Can you please help with this

Many thanks
.

Relevant Pages

  • Re: alias expansion problem?
    ... this is what transpires.. ... Connecting to angel.samoa.net.ws. ... 220-angel.samoa.net.ws ESMTP service ready ... 250, Recipient ok ...
    (comp.unix.solaris)
  • header ESMTP£ by m4/cfhead.m4
    ... one of his recipient didn't accept the e-mails, ... the header was not correct. ... sometimes there was also ESMTP? ...
    (comp.mail.sendmail)