GFI Software

Welcome to the GFI Software community forum! For support please open a ticket from https://support.gfi.com.

Home » Product Feedback » Kerio Connect Feedback » Text encoding (Possibility to send text attachements encoded (for example base64))
Text encoding [message #146609] Mon, 16 September 2019 08:52
vanWezel is currently offline  vanWezel
Messages: 1
Registered: September 2019
Hello everybody,

We send orders by mail to one of our suppliers in EDI format. This means we send a text file as attachment with data such as article number, quantity and requested delivery date. Our supplier imports this attachment in their ERP system and send us a confirmation in return.

Using Kerio Connect our suppliers software can't import the attachments in their ERP system. When we send the same attachment using Exchange or Gmail they have no difficulties at all.

Programmers of our supplier reported that the cause of this is the text encoding of the e-mails.

When I mail the EDI-attachment from my Kerio mail address to myself (the same Kerio mail address) and view the source of the e-mail in Kerio Webmail, I'll get this:

--=-AcdFdek3sGCSQ65eibH1
Content-Type: text/plain; name="icm_10092019.txt"
Content-Disposition: attachment; filename="icm_10092019.txt"

SE
90214-038-SE
90214
0305405000
B
000
10-12-2019
005
0000010
08963
90214-EDISTORING *000119832
000028.90
0000005
08875
90214-EDISTORING *000119833
000040.15
0000010
04200
90214-EDISTORING *000119834
000126.50
0000005
01017
90214-EDISTORING *000119835
000115.15
0000005
03220
90214-EDISTORING *000119836
000014.35
--=-AcdFdek3sGCSQ65eibH1--


When I mail the same mail from Gmail, I'll get this:

--0000000000004d768e05926adc06--
--0000000000004d769205926adc08
Content-Type: text/plain; charset="US-ASCII"; name="icm_10092019.txt"
Content-Disposition: attachment; filename="icm_10092019.txt"
Content-Transfer-Encoding: base64

Content-ID: <f_k0huk0h20>
X-Attachment-Id: f_k0huk0h20
U0UNCjkwMjE0LTAzOC1TRQ0KDQo5MDIxNA0KMDMwNTQwNTAwMA0KQg0KMDAw DQoNCg0KDQoNCg0K
DQoNCjEwLTEyLTIwMTkNCg0KDQoNCjAwNQ0KMDAwMDAxMA0KMDg5NjMNCjkw MjE0LUVESVNUT1JJ
TkcgICAgICAgICAqMDAwMTE5ODMyDQowMDAwMjguOTANCjAwMDAwMDUNCjA4 ODc1DQo5MDIxNC1F
RElTVE9SSU5HICAgICAgICAgKjAwMDExOTgzMw0KMDAwMDQwLjE1DQowMDAw MDEwDQowNDIwMA0K
OTAyMTQtRURJU1RPUklORyAgICAgICAgICowMDAxMTk4MzQNCjAwMDEyNi41 MA0KMDAwMDAwNQ0K
MDEwMTcNCjkwMjE0LUVESVNUT1JJTkcgICAgICAgICAqMDAwMTE5ODM1DQow MDAxMTUuMTUNCjAw
MDAwMDUNCjAzMjIwDQo5MDIxNC1FRElTVE9SSU5HICAgICAgICAgKjAwMDEx OTgzNg0KMDAwMDE0
LjM1DQo=
--0000000000004d769205926adc08--


It doesn't matter which client application we use in combination with Kerio Connect Server. The result is the same with Outlook as with Kerio Webmail.

Our supplier needs the content to be encoded. (base64 for example works)

I submitted a request ticket, but your support team advised me to request this as a new feature.

Will it be possible for you to create different options for text encoding. Might be useful as well to be able to put a conditional rule. So you can change the text encoding when you send mail to address X.
Previous Topic: Requests
Next Topic: Password retreival/reset
Goto Forum:
  


Current Time: Sun Mar 26 10:56:47 CEST 2023

Total time taken to generate the page: 0.04774 seconds