"Mike Hall" <Mike.Hall@NOSPAMPLEASEMachine-IT.Com.invalid> wrote in message
news:444b6963@newsgroups.borland.com...
> I have an application, which has been running sucessfullt for
> around 18 months, which accepts files by e-mail and uploads
> an XML attachment to a DB.
You did not say which version of Indy you are using.
> Suddenly, the application has stopped working, and this is due
> to the attachment not being decoded by Indy, but saved to disk
> in MIME format; just the attachment that is, not the whole file.
Did you change anything in your code lately? Did you upgrade Indy recently?
If not, then the only explanation is that messages have started arriving to
your application in a different format that your version of Indy can't
handle.
> the sending client's format has changed a little and I presume that this
> has caused the problem.
Very likely, yes. What EXACTLY has changed? Which portions of the message
are not being parsed correctly?
> I have upgraded it to the latest version 9 and the latest 10 (not the
> development one).
Why not the latest snapshot of Indy 10?
> Return-Path: *****@*****.com
The "Return-Path" header appears twice in the message. Although that has no
effect on Indy's parsing, it is an indication of a malformed message from
the client's end. That header should appear only once.
Gmbit
