# Supported file type .asice

**URL:** <https://community.hubspot.com/t/supported-file-type-asice/49469>\
**Category:** HubSpot Ideas\
**Tags:** sales-email\
**Created:** [January 10, 2022, 9:20am UTC](https://community.hubspot.com/t/supported-file-type-asice/49469 "2022-01-10T09:20:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![A-Purve](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@A-Purve](https://community.hubspot.com/u/A-Purve)\
**Post date:** [January 10, 2022, 9:20am UTC](https://community.hubspot.com/t/supported-file-type-asice/49469/1 "2022-01-10T09:20:24Z")

</div>

We are not able to send out “. **asice** ” files through the email aliases we set up in HubSpot as it states that " **this file type**  **is not supported"**.  
We need this because our platform is built on this file type for e-signatures and sometimes these files need to be shared via email as an attachment. In my mind, it is a very basic feature that you can add whatever file you need in the attachments of an email.

The whole of Estonia is using this file type for e-signatures plus Latvia, Lithuania and Finland and probably others in the EU as well…

More info on that: [ID-ee | 404](https://www.id.ee/en/article/what-is-the-difference-between-digitally-signed-documents-with-bdoc-and-asice-extensions-2/)

How can we resolve this?

---

<div class="post-metadata">

**Author:** ![A-Purve](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@A-Purve](https://community.hubspot.com/u/A-Purve)\
**Post date:** [January 27, 2022, 11:08am UTC](https://community.hubspot.com/t/supported-file-type-asice/49469/2 "2022-01-27T11:08:20Z")

</div>

up

---

<div class="post-metadata">

**Author:** ![A-Purve](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@A-Purve](https://community.hubspot.com/u/A-Purve)\
**Post date:** [March 30, 2022, 8:42am UTC](https://community.hubspot.com/t/supported-file-type-asice/49469/3 "2022-03-30T08:42:13Z")

</div>

up

---

<div class="post-metadata">

**Author:** ![A-Purve](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@A-Purve](https://community.hubspot.com/u/A-Purve)\
**Post date:** [April 19, 2022, 9:11am UTC](https://community.hubspot.com/t/supported-file-type-asice/49469/4 "2022-04-19T09:11:35Z")

</div>

up

---

<div class="post-metadata">

**Author:** ![A-Purve](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@A-Purve](https://community.hubspot.com/u/A-Purve)\
**Post date:** [November 15, 2022, 7:44am UTC](https://community.hubspot.com/t/supported-file-type-asice/49469/5 "2022-11-15T07:44:42Z")

</div>

up

---

<div class="post-metadata">

**Author:** ![A-Purve](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@A-Purve](https://community.hubspot.com/u/A-Purve)\
**Post date:** [April 19, 2023, 8:45am UTC](https://community.hubspot.com/t/supported-file-type-asice/49469/6 "2023-04-19T08:45:13Z")

</div>

That is very embarrassing HubSpot – over a year and not even an answer.