wiskbr...@hotmail.com:
> >> I have an outsourced IM archival system, data from IM sessions
> >> are sent to this system for archive via email. We select an IM
> >> message for un-archival, which is then emailed to us. The problem
> >> I am having is that even prior to arrival at the IM archiving
> >> vendor, my IM message has already had its DATA munged by our
> >> outbound server, whereby our outbound SMTP relay has appended our
> >> domain to an IM screen-name. In other words, the DATA within the
> >> IM message is being read as a message HEADER, and the "To" field
> >> within the IM message is being re-written and appended with my
> >> own domain.
> >>
> >> As you can see from my capture below, "screen-name" is within the
> >> message DATA, yet when arriving at the archive site, has already
> >> been re-written to be "screen-n...@my.example.com".? My deliminator
> >> in my main.cf is :, and needed that way for my AV.? Is my problem
> >> a result of my deliminator setting?
> >
> > According to RFC 5322, the body of a message is separated from
> > the header by an empty line.
> >
> > To send the IM message in the body of an RFC 5322 message, the
> > retrieval system must prepend an RFC 5322 header and empty line
> > before the IM message.
>
> Thank you Wietse, how can I tell if this is actually happening,
> based on my tcpdump output?
I suppose you overlooked this detail in my response:
To send the IM message in the body of an RFC 5322 message, the
retrieval system must prepend an RFC 5322 header and empty line
before the IM message.
In case you wonder, RFC 5322 is the official definition of the
Internet message format.
Wietse
