Pages: 1
RSS
How to get ICS files read by The Bat?, ICS calendar files are getting converted to TXT files
 
Emails with .ICS attachments (outlook calendar entries) are getting converted to .TXT files, which would then take a few more steps to rename and input into Outlook.

The ICS files are are correct on Gmail, and work with another email client, so it is something with The Bat.

I've tried tinkering with File extensions, to put ICS in as trusted extension, but that makes no difference.

I can't find anything in the help that deal with decoding mime types, other than email encryption/decryption.  And switching the MIME certificate to Microsoft did not help either.

Any other ideas?


BTW I did see that this was asked a few months ago, but no answer...
 
AFAIK TB doesn't support ICS as it doesn't ave any calendar functionality.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
I'm not looking for The Bat to support ICS any more than it does TXT, DOC, or XLS files.  Than is.. just get the file as an attachment and let me open it with some other application.

What it appears to be doing it not handling them in as a standard MIME attachment, and not creating the ICS file. Perhaps it IS trying to do something with it, and I'd like to put a stop to it.
 
From what source are you getting ICS files?
Till now I've only got them from Outlook users and those messages don't have an .ICS file attached, but they've got the ICS info in the message body. It's not unlikely that ICS-compatible clients will translate that, but non-ICS-compatible clients won't do that.
In order to see whether the ICS stuff is actually sent as attachment or as contents of the body, you can check the message source. Simply press F9 while viewing the message. If the ICS stuff is attached then there ought to be a separating line between body and file, something this:
------=_NextPart_000_003F_01CDE09C.5864BF50
If there's no separating line then there's no attachment.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
The ICS files are separate, and there is separating line like
--_000_5C7B78E27A8D9245B79142214F489940102BB3Exchange10
Content-Type: text/calendar; charset="utf-8"; method=REQUEST
Content-Transfer-Encoding: base64

In gmail, they do show up as an attachment with a .ics extension

In The Bat, I am now seeing some ICS files, but they are called part.txt, and they are in a the system temp folder, not the attachment folder.  I am pretty sure this was not the case before I started tinkering with options, but not sure all what I changed since I first started looking at this.

Yes, I know I can rename the files, etc, but there must be some reason that they are being mishandled, and I'd like to fix it so they work as expected.
 
It's easy to explain why TB doesn't give the an ICS extension.
TB needs info about the file name, that's supposed to be given in the file header like:

------=_NextPart_000_0007_01CE0E2A.18A53AA0
Content-Type: application/vnd.ms-excel;
       name="info.xls"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
       filename="info.xls"

If the header doesn't mention that it's supposed to be an attachment or gives a filename then TB thinks it's a message part. If it isn't an attachment, it won't appear in the attachment folder.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
Pages: 1