# Ignore BOM on CSV when sending bulk invitations

**URL:** <https://meta.discourse.org/t/ignore-bom-on-csv-when-sending-bulk-invitations/62332>\
**Category:** Bug\
**Created:** [9 Mayo, 2017 04:30 UTC](https://meta.discourse.org/t/ignore-bom-on-csv-when-sending-bulk-invitations/62332 "2017-05-09T04:30:40Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![barryvan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barryvan/32/82635_2.png) [@barryvan](https://meta.discourse.org/u/barryvan)\
**Post date:** [9 Mayo, 2017 04:30 UTC](https://meta.discourse.org/t/ignore-bom-on-csv-when-sending-bulk-invitations/62332/1 "2017-05-09T04:30:40Z")

</div>

When creating a CSV in Excel, it by default includes (what I think is) a BOM marker at the top of the file, to ensure that it’s parsed as UTF-8. Unfortunately Discourse doesn’t handle this (and doesn’t read the file as UTF-8!) so the first email address always fails with an error like this:

![](https://global.discourse-cdn.com/meta/original/3X/c/5/c52e974399dfcb42f37ac1101bab929d3c49ff2f.png)

(Note that the “j” is the first letter of the actual email address.)

I think Discourse should strip/ignore the BOM on CSVs – it’s probably pretty common that people would put these together in Excel, after all. 😉

---

_[View the full topic](https://meta.discourse.org/t/ignore-bom-on-csv-when-sending-bulk-invitations/62332)._
