Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 779
  • Last Modified:

User not receiving pxt/mms messages in their Inbox

We are having issues receiving pxt/mms messages from mobile phones. The messages are being received by the SMTP server (verified by enabling logging) and thus passed onto Exchange. After turning on the message archive feature and pointing it to the Administrators mailbox we sent another message. The message did not show up in recipients Inbox but did come to the Administrators mailbox. This has been tested with both Outlook XP and Outlook 2003 so I don't think it is related to the client? Anyone seen this before?

The configuration is as follows:
W2K Standard Server - SP4 and up-to-date with Windows Update patches.
Exchange Server 2000 SP3

TIA,
Bart


0
Bart van der Wee
Asked:
Bart van der Wee
  • 6
  • 5
1 Solution
 
What90Commented:
Did you receive an NDR with the email?

Are the email addresses correct, is the phone adding any extra chanracters to the email address?
0
 
Bart van der WeeAuthor Commented:
Everything appears to be as it should be - the 'archive' message that the Administrator received but never turned up in the original recipients Inbox appears to be vaild, there is nothing 'funny' in the headers either.
Got me beat that's for sure.
The only thing I can put it down to is maybe a permissions issue or even a information store corruption?

Bart
0
 
What90Commented:
Could the user's mail box be corrupt?

Have you tried a couple of other users?



Or have you check the user's Outlook is thinking it spam and moving it to a junk folder.

Check the user's mailbox for rules too!
0
Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

 
Bart van der WeeAuthor Commented:
Hi What90,

There are several users that are not receiving these type of messages. All using Oulook 2003.

I have gone over one users Outlook 2003 on their PC and also used Outlook 2002 on the server and the message isn't on either and there are no rules running - server or client side and they are not using any scripting.

An identical message was sent to another Ex2000 server where I work (different domain etc.) and that came through fine.
Would it help if I posted the mail message headers? It is certainly a very perplexing problem.

Bart.
0
 
What90Commented:
Bugger.

I would have thought that if it turned up in the archive store, then it was a Outlook rule for sure.
If the thing's going to your Exchange server (proved by the appearance in the archive store) then it has to be something in the message store or on the client's mail box ....

Is there any mailbox limits set on those accounts?
Have you also tried turning on message tracking as seeing what happens to the incoming message?

If you can, then I'd run an offline database check, as you've mentioned, just to get rid of that option.
0
 
Bart van der WeeAuthor Commented:
We are working at replicating the fault in another Ex2000 environment before we go down the database check - there has to be a simple explanation so will keep you posted with progress.
Bart.
PS - Just for your interest here are the mime headers etc from the email message:

Received: from opwvsmtp ([xx.xx.xx.xx]) by mms1-rme.xtra.co.nz with SMTP
          id <20040427225704.BBED20381.mms1-rme.xtra.co.nz@opwvsmtp>
          for <Bxxt@xxxxxxx.co.nz>; Wed, 28 Apr 2004 10:57:04 +1200
X-Priority: 3
Content-Type: multipart/related; boundary="408ee53f4e4fqwerty_0000"
Date: Tue, 27 Apr 2004 22:57:03 GMT
From: +6427xxxxxxx@mms.xtra.co.nz
MIME-Version: 1.0
Sender: +6427xxxxxxx@mms.xtra.co.nz
To: Bxxt@xxxxxxx.co.nz
Message-Id: <20040427225704.BBED20381.mms1-rme.xtra.co.nz@opwvsmtp>
Return-Path: +6427xxxxxx@mms.xtra.co.nz
X-OriginalArrivalTime: 27 Apr 2004 22:57:20.0123 (UTC) FILETIME=[FEA0CCB0:01C42CAA]

--408ee53f4e4fqwerty_0000
Content-Type: multipart/alternative; boundary="prez_1234567890_ldksjfa"

--prez_1234567890_ldksjfa
Content-Type: text/plain; charset="utf-8"

--prez_1234567890_ldksjfa
Content-Type: text/html; charset="utf-8"


--prez_1234567890_ldksjfa--
--408ee53f4e4fqwerty_0000
Content-Disposition: inline; filename="photo_0004.jpg"
Content-ID: <image_0>
Content-Transfer-Encoding: base64
Content-Type: image/jpeg; name="photo_0004.jpg"


--408ee53f4e4fqwerty_0000--
0
 
What90Commented:
The header seems fine.

Could you try to get the user to send a standard text, follow by an email followed by a Pxt/MMS.

I'm just wondering if the Exchange server or user's mailbox is blocking the MMS code?
0
 
Bart van der WeeAuthor Commented:
I am going to test it using a POP client to 'look' in the mailbox that way.
Might make a copy of their information store and run an integrity check on the copy before proceeding with anything more drastic.

The MMS mime headers don't look all that different from standard email headers, I am also going to give the user concerned Domain Admin rights and test wether or not it is ACL related.

0
 
Bart van der WeeAuthor Commented:
This problem gets stranger:
I enabled message tracking and also a forward from the affected recipient to my work email. A pxt was sent and duly received by the SMTP server, the message trace advised that it was delivered to the Message store and forwarded to my work mail server. The message arrived at work all ok. The message does not appear in the Inbox of the intended recipient! The recipient has been given Domain Admin rights.

I also had a friend pxt via a different provider - Vodafone GSM - and that message cam through all ok. (The customer is using the local monopoly telephone provider Telecom and their non-GSM network.)  

I have setup a Public folder and this received a PXT ok but when that was forwarded directly to the user it did not show up!

Tomorrow (NZ time) I will be back there and will setup a new user and see how wide-spread the problem is. I will also connect using a POP client.
Any other ideas?

Bart.
0
 
What90Commented:
You must have a security setting somewhere doing this on the outlook client ....


Here's a thought, go to OWA open the mailbox of the Pxt receipant and see if it's there?

Very weird, but interesting!
0
 
Bart van der WeeAuthor Commented:
After deleting and re-creating the user's mailbox all is working ok now.
Thanks What90

Bart
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now