In <[EMAIL PROTECTED]">mid:[EMAIL PROTECTED]>, Eddy [E] wrote:'
E> Allie, it shouldn't matter what client the senders are using. I know it shouldn't. However, with buggy behaviour, something that shouldn't happen is happening. This corruption has happened to me before. Yes it has! It happened with one person on three separate occasions. No one else. That person uses Outlook Express. On all these occasions, multiple image files were attached. Both of us were mystified about what happened. I can't find the messages to forward the attachments back to myself. This is not necessarily an OE vendetta. Not at all. This is just the only odd thing out that I can think of. The knowledge of the client may point to encoding methods. I don't know if the type of encoding used by the sender's client triggers the problem. If this doesn't happen to everyone then there is something that causes and we have to find that cause. It does seem to be TB! but it doesn't do this corruption all the time. E> - In any event, TB! should never corrupt an attachment, E> regardless of what MUA is used. No one is saying it should. It's just that it may be doing this and it needs to be fixed. -- Allie C Martin \ TB! v1.62/Beta5 & WinXP Pro (SP1) List Moderator / PGP Key - http://pub-key.ac-martin.com ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
