Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Order notifications are not internet standard (MIME) compliant
Folks,
Netsuite's order confirmations seem to be arriving as MIME email messages, but there seems to be a fairly major problem with them. The top-level content-type is multipart/alternative, which is fine. There are two alternatives, as follows:
------=_Part_12580_16012420.1223388600378
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
------=_Part_12580_16012420.1223388600378
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
The first issue I have here is minor - the MIME-Version header should not appear in the parts, it is already defined in the main message header and having it here is out of spec.
That's just a minor niggle for the MIME nerds in the audience. The real problem though is that the text/plain part is garbage. It looks like:
Netsuite's order confirmations seem to be arriving as MIME email messages, but there seems to be a fairly major problem with them. The top-level content-type is multipart/alternative, which is fine. There are two alternatives, as follows:
------=_Part_12580_16012420.1223388600378
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
------=_Part_12580_16012420.1223388600378
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
The first issue I have here is minor - the MIME-Version header should not appear in the parts, it is already defined in the main message header and having it here is out of spec.
That's just a minor niggle for the MIME nerds in the audience. The real problem though is that the text/plain part is garbage. It looks like:
0