WAI, Webmail, and xmail, attachments and webmail problem

I have installed the latest version of WAI .NET from altair. Works great except for adding attachments to emails composed in the webmail. When the emails are received the attacments are not recognised as that and are included in the body of the email (as all sorts or characters). Any ideas please.

I think there maybe a general question about HTML emails and MIME parsing here but I don't know enough about it at the moment to ask the right questions.

Thanks in Advance.

Andy.

I think you should ask at Altair for a webmail problem.

I have tried to contact Altair, I have had no response so I wondered if anyone here can help!

Andy.

Then try at the xmail mailing list. I am sure that Valasek will answer you there because he is one of the subscriber.

Make sure you are using the latest WAI.NET version. I have not had any reported problems with attachments since using it.

There is a problem but only with .txt attach.
We are waiting for the next version !

I tried attaching a zip file - this is what I get: (I receive the mail in Outlook XP)

******************************************************

This message is in multi-part MIME format. If you're reading this text, your mailer probably does not understand MIME - we're sorry.

--AltairCom_kevinstone_71d80409d7264df89c014d532f6e86a9
Content-Type: text/plain; charset=utf-7
Content-Transfer-Encoding: 7bit

dffgd
--AltairCom_kevinstone_71d80409d7264df89c014d532f6e86a9
Content-Type: application/x-zip-compressed
Content-Disposition: attachment; filename='hmm.zip'
Content-Transfer-Encoding: Base64

UEsDBBQAAAAIAB20UCﮪ꾄砀찀ᰀ
ꆵ뒹퇡턭⒭㤤갘䲂倉躘反쯅전撀ରņhŁⰄࡐP v텀뻻ꪯ葸Ì€˚Ѐơ떴맑䄬ᐘЀЀ퐀
ఀ==
--AltairCom_kevinstone_71d80409d7264df89c014d532f6e86a9--

******************************************************

I have checked it is the latest version - any further help will be greatly appreciated.

Andy.

I could really do with some help on this. Can anyone even point me in the right direction to examining the problem. Is it the MIME parser, or something else?

Any Ideas?

Andy.

The characters following the line
>Content-Transfer-Encoding: Base64
are no encoded ones. Something is working not correctly and trashes the mail's format. You should rollback to a prior version of WAI.

At my sistem spec all working well except .txt files!
Do you have .NET 1.1 install ?
All patches from Microsoft ?

Yes fully patched 2003 server with 1.1 .net

It all seems to work fine, can compose new mail and send and even attach a file, the problem is just when the email is received the attachment is not recognised!

What happens with your txt files? Same effect?

I think it must be the mime parser, or the way it is ending mail through XMAIL
Does anyone know if it uses sendmail exe or spools the mail locally??

Andy.

it spools email local !
the problem is when you send the email, the mime parser is the problem, when you send the email the mime parses break the message !

Xmail places the file into the spool folder without doing any changes to its content. It only adds 5 lines spoolfile header. I had a similar problem on Outlook approx. 2 years ago. A reinstall fixed it. Must have bin some MIME .dll used by Outlook ...

I propose the following:
- Send an attached zip file to non-existing address, e.g. @aol.co (not .com).
- The mail will be frozen in the queue.
- Now you can use XQM to locate and examine the file.

If it is crippled, then the problem is the sender. If not, it might be the recipient's mailer.

I have been doing more tests. It happens with all attachments! It is must be spooling it wrong because I have tried receiving it on many different computers through many different email accounts all with the same results. I shall keep looking t it and I am going to try and setup a another complete system to see if the same happens. Then I can mess around with it without worrying about destroying anything. Below is another example of the problem incase any one has more ideas:

This message is in multi-part MIME format. If you're reading this text,
your mailer probably does not understand MIME - we're sorry.

--AltairCom_kevinstone_971b0d37085e491da5dfd1440a48acc2
Content-Type: text/plain; charset=utf-7
Content-Transfer-Encoding: 7bit

fdsfsdf
--AltairCom_kevinstone_971b0d37085e491da5dfd1440a48acc2
Content-Type: application/x-zip-compressed
Content-Disposition: attachment; filename='Ddd.zip'
Content-Transfer-Encoding: Base64

UEsDBBQAAAAIAAVBXCꤌ懜　䀀ᰀ
醑邹퇡턭┭㴥Ⲿᮊ큐ŁⰄࡐP հ뺩ౡ�@€˚ЀƑ醐맑䄬ᐘЀЀ퐀쐀==
--AltairCom_kevinstone_971b0d37085e491da5dfd1440a48acc2--

Thanks

Andy.

I don't know that there is a problem. After creating a test system I have discovered it works fine when using webmail to read the emails. The only problem is when the email is received in outlook or outlook express!! Is this a known issue with webmail? Outlook and Outlook express don't seem to accept the way the emails are encoded? Any ideas will help greatly!

Andy.