mrspeaker@gmail.com
Guest
|
 Posted:
Sun Aug 21, 2005 2:17 pm Post subject:
Keeping a message-id during routing for an SMTP sink |
|
|
I dont know if anyone can help out on this one, but here goes:
As a development environment I had set up an exchange server with an
SMTP outbound event sink. For certain outbound mails, a message was
added to a MSMQ queue containing the TO, RECIPENTS and the Rfc message
Id.
The queue was then processed by another program, and the messages are
identified by the urn:schemas:mailheader:message-id property - which
matches the SMTP sink message id.
The problem is that the live environment routes outbound messages
through another exchange server, then to a disclaimer machine which
also contains the SMTP event sink.
When the message hits the 2nd exchange server, it seems to get a new
message id. So the message id the event sink grabs is the new id, and
does not match the origninal id.
I am unsure how to handle this situation. My idea is to move the SMTP
sink to the first exchange server, but I am unsure if this will work,
as the first server is just routing messages, and probably will not
trigger the outbound event (maybe?)
Is it possible to trap routed messages in a manner similar to outbound
events?
Thanks for your help!
|
|
mrspeaker@gmail.com
Guest
|
| Posted:
Mon Aug 22, 2005 8:58 am Post subject:
Re: Keeping a message-id during routing for an SMTP sink |
|
|
Yes, the server will fire the smtp outbound events. I bit the bullet
and just tested it on a production server :)
Can anyone lend an insight as to why the message Id gets changed, and
any other solution that would have allowed be to keep the SMTP sink on
the outbound disclaimer box? |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in