MSExchangeTransport error 7519

  • Thread starter bGh1ZmY
  • Start date Views 2,307
B

bGh1ZmY

#1
I get several of these errors per day. Uising SBS 2003/Exchange with SP2 IMF

installed.

Event Type: Error

Event Source: MSExchangeTransport

Event Category: SMTP Protocol

Event ID: 7519

Date: 5/3/2009

Time: 1:05:53 AM

User: N/A

Computer: NETSERVER

Description:

The originating IP address of message with ID

<523A85E1A7634FA394E02A567AE8E7C8@EMS.local> could not be determined based on

its Received headers.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.
 
E

Ed Crowley [MVP]

#2
See if anything here can help you.

http://eventid.net/display.asp?eventid=7519&eventno=7958&source=MSExchangeTransport&phase=1

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"lhuff" <lhuff> wrote in message

news:AD0AC654-3961-4F46-8E69-D30CF362DBF7@microsoft.com...
> I get several of these errors per day. Uising SBS 2003/Exchange with SP2
> IMF
> installed.

> Event Type: Error
> Event Source: MSExchangeTransport
> Event Category: SMTP Protocol
> Event ID: 7519
> Date: 5/3/2009
> Time: 1:05:53 AM
> User: N/A
> Computer: NETSERVER
> Description:
> The originating IP address of message with ID
> <523A85E1A7634FA394E02A567AE8E7C8@EMS.local> could not be determined based
> on
> its Received headers.

> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
 
B

bGh1ZmY

#3
Yes the correct server IP and 127.0.0.1 are in the list.

"Ed Crowley [MVP]" wrote:


> See if anything here can help you.
> http://eventid.net/display.asp?eventid=7519&eventno=7958&source=MSExchangeTransport&phase=1
> > Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..

> "lhuff" <lhuff> wrote in message
> news:AD0AC654-3961-4F46-8E69-D30CF362DBF7@microsoft.com...
> >I get several of these errors per day. Uising SBS 2003/Exchange with SP2
> >IMF
> > installed.
> > Event Type: Error
> > Event Source: MSExchangeTransport
> > Event Category: SMTP Protocol
> > Event ID: 7519
> > Date: 5/3/2009
> > Time: 1:05:53 AM
> > User: N/A
> > Computer: NETSERVER
> > Description:
> > The originating IP address of message with ID
> > <523A85E1A7634FA394E02A567AE8E7C8@EMS.local> could not be determined based
> > on
> > its Received headers.
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >


>
 
R

Rich Matheisen [MVP]

#4
On Sun, 3 May 2009 07:31:01 -0700, lhuff

<lhuff> wrote:


> I get several of these errors per day. Uising SBS 2003/Exchange with SP2 IMF
> installed.

> Event Type: Error
> Event Source: MSExchangeTransport
> Event Category: SMTP Protocol
> Event ID: 7519
> Date: 5/3/2009
> Time: 1:05:53 AM
> User: N/A
> Computer: NETSERVER
> Description:
> The originating IP address of message with ID
> <523A85E1A7634FA394E02A567AE8E7C8@EMS.local> could not be determined based on
> its Received headers.

> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.


So what's in the "Received:" header?

-
Rich Matheisen

 
B

bGh1ZmY

#5
Not sure how to the email or the recieved header

"Rich Matheisen [MVP]" wrote:


> On Sun, 3 May 2009 07:31:01 -0700, lhuff
> <lhuff> wrote:
>
> >I get several of these errors per day. Uising SBS 2003/Exchange with SP2 IMF
> >installed.
> >Event Type: Error
> >Event Source: MSExchangeTransport
> >Event Category: SMTP Protocol
> >Event ID: 7519
> >Date: 5/3/2009
> >Time: 1:05:53 AM
> >User: N/A
> >Computer: NETSERVER
> >Description:
> >The originating IP address of message with ID
> ><523A85E1A7634FA394E02A567AE8E7C8@EMS.local> could not be determined based on
> >its Received headers.
> >For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.


> So what's in the "Received:" header?
> -> Rich Matheisen
>
>
 
R

Rich Matheisen [MVP]

#6
On Mon, 4 May 2009 11:00:11 -0700, lhuff

<lhuff> wrote:


> Not sure how to the email or the recieved header


You have the Message-ID in the loged event. If it was delivered to a

local mailbox you'd look there for the message. Once you find it, if

you use Outlook, right-click the message and select "Message Options".

-
Rich Matheisen

 
B

bGh1ZmY

#7
OK, I used Exchange Message Tracking Center.

They are system messages sent to local and internet mail.

Microsoft Mail Internet Headers Version 2.0

Received: from netserver ([127.0.0.1]) by tvems.com with Microsoft

SMTPSVC(6.0.3790.4334);

Mon, 4 May 2009 13:08:45 -0600

thread-index: AcnM6772RokwPuPnSkyWdLbMMdr24g==

Thread-Topic: World Wide Web Publishing Alert on NETSERVER

From: "NETSERVER" <Administrator@tvems.com
To: <lhuff@tvems.com>,

<lyle35204@hotmail.com
Cc:

Bcc:

Subject: World Wide Web Publishing Alert on NETSERVER

Date: Mon, 4 May 2009 13:08:44 -0600

Message-ID: <CDE6C78499B142DAABCD497899B5BDA4@EMS.local
MIME-Version: 1.0

Content-Type: text/plain

Content-Transfer-Encoding: 7bit

X-Mailer: Microsoft CDO for Exchange 2000

Content-Class: urn:content-classes:message

Importance: normal

Priority: normal

X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325

Return-Path: Administrator@tvems.com

X-OriginalArrivalTime: 04 May 2009 19:08:45.0089 (UTC)

FILETIME=[BF047110:01C9CCEB]

"Rich Matheisen [MVP]" wrote:


> On Mon, 4 May 2009 11:00:11 -0700, lhuff
> <lhuff> wrote:
>
> >Not sure how to the email or the recieved header


> You have the Message-ID in the loged event. If it was delivered to a
> local mailbox you'd look there for the message. Once you find it, if
> you use Outlook, right-click the message and select "Message Options".
> -> Rich Matheisen
>
>
 
B

bGh1ZmY

#8
Here is the same header on webmail account.

X-Message-Delivery: Vj0xLjE7dXM9MDtsPTA7YT0xO0Q9MTtTQ0w9MQ==

X-Message-Status: n:0

X-SID-PRA: NETSERVER <Administrator@tvems.com
X-Message-Info:

JGTYoYF78jGEhCL50HbvXIeHDNti2RrVsEhaixQRs+X+oKY5zk0BijQWNjSm/YiZE5X7/EyF9HMDjkCt8+iol+cYHG54xobj

Received: from tvems.com ([67.134.170.122]) by coL0-mc3-f43.Col0.hotmail.com

with Microsoft SMTPSVC(6.0.3790.3959);

Mon, 4 May 2009 12:08:46 -0700

Received: from netserver ([127.0.0.1]) by tvems.com with Microsoft

SMTPSVC(6.0.3790.4334);

Mon, 4 May 2009 13:08:45 -0600

thread-index: AcnM6772RokwPuPnSkyWdLbMMdr24g==

Thread-Topic: World Wide Web Publishing Alert on NETSERVER

From: "NETSERVER" <Administrator@tvems.com
To: <lhuff@tvems.com>,

<lyle35204@hotmail.com
Cc:

Bcc:

Subject: World Wide Web Publishing Alert on NETSERVER

Date: Mon, 4 May 2009 13:08:44 -0600

Message-ID: <CDE6C78499B142DAABCD497899B5BDA4@EMS.local
MIME-Version: 1.0

Content-Type: text/plain

Content-Transfer-Encoding: 7bit

X-Mailer: Microsoft CDO for Exchange 2000

Content-Class: urn:content-classes:message

Importance: normal

Priority: normal

X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325

Return-Path: Administrator@tvems.com

X-OriginalArrivalTime: 04 May 2009 19:08:45.0089 (UTC)

FILETIME=[BF047110:01C9CCEB]

"lhuff" wrote:


> I get several of these errors per day. Uising SBS 2003/Exchange with SP2 IMF
> installed.

> Event Type: Error
> Event Source: MSExchangeTransport
> Event Category: SMTP Protocol
> Event ID: 7519
> Date: 5/3/2009
> Time: 1:05:53 AM
> User: N/A
> Computer: NETSERVER
> Description:
> The originating IP address of message with ID
> <523A85E1A7634FA394E02A567AE8E7C8@EMS.local> could not be determined based on
> its Received headers.

> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
 
R

Rich Matheisen [MVP]

#9
On Mon, 4 May 2009 12:15:01 -0700, lhuff

<lhuff> wrote:


> Received: from netserver ([127.0.0.1]) by tvems.com with Microsoft


Are you running whatever application is sending those messages on the

Exchange server?

You might want to try adding 127.0.0.1 to the perimeter and internal

IP address set (Global Settings | Message Delivery | general |

Add...").

-
Rich Matheisen

 
B

bGh1ZmY

#10
Yes, 127.0.0.1 is in the list. I think it may be related to the the webmail

account being read through outlook.

"Rich Matheisen [MVP]" wrote:


> On Mon, 4 May 2009 12:15:01 -0700, lhuff
> <lhuff> wrote:
>
> >Received: from netserver ([127.0.0.1]) by tvems.com with Microsoft


> Are you running whatever application is sending those messages on the
> Exchange server?

> You might want to try adding 127.0.0.1 to the perimeter and internal
> IP address set (Global Settings | Message Delivery | general |
> Add...").
> -> Rich Matheisen
>
>
 
Top