Remy Lebeau (TeamB) schrieb:
>> the story continues ...
>
> Why are you starting a new thread then?
I didn't. Just replied to my own post.
Never minnd. Thank you again for jumping in.
> If you read the API documentation, you will see the following
> description:
>
> WSAECONNRESET (10054)
>
> Connection reset by peer.
>
> A existing connection was forcibly closed by the remote host. This
> normally results if the peer application on the remote host is
> suddenly stopped, the host is rebooted, or the remote host used a
> "hard close" (see setsockopt for more information on the SO_LINGER
> option on the remote socket.)
>
>> A ISP host-reset or failure could be exclude as it's one of the
>> biggest ISP in Germany.
>
> That doesn't exclude anything. Even the largest networks have
> problems occasionally.
Ok. I agree. It doesn't exclude anything.
But it's *not* occasionally on *every* machine in the same network -
which would proof your idea - it's occasionally on *some* machines.
I observed that a mail with a PDF attachment which is more than about
300 kB will fail. Smaller attachments or mails without attachment always
work. As said before Thunderbird/Outlook handle large attachments quite
well on the "defective" machine.
I adjusted my code to save the problematic mail as plaintext just before
it is send and it seems (in my eyes) to be correct.
I couldn't post it here due to privacy issues - it's financial/insurance
data. The mail and attached PDF are shown correctly if I open the
(plaintext) e.g. in Outlook.
I'm really lost.
Some more ideas - I just ran out of fresh ones :-(
Stephan
--
Logik ist die Kunst, zuversichtlich in die Irre zu gehen.
Stephan Jaschke - EDV-Beratung und Softwareentwicklung
Mail: support@stj-software.de - ICQ: 361511624
