I am reaching out to inquire about any potential limitations on the utilization of special characters and Unicode in the “from” and “subject” fields. Could you kindly provide clarification on this matter?
Hey there @kindhearted-deer, thanks for posting. Please read the “Troubleshooting” and “How to Ask for Help” buttons below. If you would like a 1:1 support session from the KumoMTA team, details are at the “Book a Support Session” button below.
None that I am aware of. Is there a specific concern?
Please check this error. this is http injection api response
200 OK {"success_count":0,"fail_count":1,"failed_recipients":["aru******@gmail.com"],"errors":["aru******@gmail.com: callback error\nstack traceback:\n\t[C]: in method 'from_header'\n\t[string \"/opt/kumomta/etc/policy/init.lua\"]:168: in function <[string \"/opt/kumomta/etc/policy/init.lua\"]:165>\ncaused by: invalid header: 0: at line 1:\nSure! Here's a Japanese name: Hikari Yamamot <info@kumo.domain.com>\n ^\nexpected ';', got end of input\n\n1: at line 1, in group:\nSure! Here's a Japanese name: Hikari Yamamot <info@kumo.domain.com>\n^________________________________________________________________________\n\n2: at line 1, in Alt:\nSure! Here's a Japanese name: Hikari Yamamot <info@kumo.domain.com>\n^________________________________________________________________________\n\n3: at line 1, in address:\nSure! Here's a Japanese name: Hikari Yamamot <info@kumo.domain.com>\n^________________________________________________________________________\n\n4: at line 1, in Many1:\nSure! Here's a Japanese name: Hikari Yamamot <info@kumo.domain.com>\n^________________________________________________________________________\n\n5: at line 1, in obs_address_list:\nSure! Here's a Japanese name: Hikari Yamamot <info@kumo.domain.com>\n^________________________________________________________________________\n\n6: at line 1, in Alt:\nSure! Here's a Japanese name: Hikari Yamamot <info@kumo.domain.com>\n^________________________________________________________________________\n\n7: at line 1, in address_list:\nSure! Here's a Japanese name: Hikari Yamamot <info@kumo.domain.com>\n^________________________________________________________________________\n\n"]}
posting “Sure! Here’s a Japanese name: Hikari Yamamot” as sender name . but got error
below golang code used for sent email using kumomta
m.SetAddressHeader(“From”, “info@domain.com”, “Sure! Here’s a Japanese name: Hikari Yamamot”)
My guess is that it does not like the single quote (apostrophe) or the colon
if you are injecting using content: "message body here", rather than using the content: { .. builder stuff here .. } mode of the API, then you are responsible for the content string being a proper RFC compliant message.
When you need to use non-ASCII characters in an email header you need to ensure that it is using RFC2047 encoding.
If you use the builder mode of the API, we will generate the appropriate encoding for the various receipient related headers in the email automatically
Is there any option to get message body ? currently iam posting content as msg:get_data()
Yes. That will do it too f you capture it after the body is injected and before it is delivered. I shared a sample at some point using that to replicate the message for BCC
@faithful-ostrich @yearning-hyena help me to solve this issue https://discord.com/channels/1072980126737907824/1206926125154967562/1207540526623105076 . This is not fixed.
You have our responses, you won’t get more responses without making more of your own. You have provided no new context to respond to.
Ojk
@yearning-hyena @faithful-ostrich “While posting ‘Sure! Here’s a Japanese name: Hikari Yamamoto’ this text as sender name. Here, colon is not supported. Removing the colon makes it work. We encountered issues with the colon during development because we plan to use different languages. How can we deliver this with different languages?”
Error occurred while running the code msg:from_header().domain. Removing this code also works fine.
@faithful-ostrich @yearning-hyena please give me proper guidance to solve this issue
Sorry, I thought I answered this last week.
And Wez actually answered it above here: Discord
If you manually build the message, you are responsible for making sure it is RFC compliant (RFC 2821 - Simple Mail Transfer Protocol)
We recommend using the builder mode.
https://docs.kumomta.com/reference/http/api_inject_v1/#content
Recipients shoudl be defined like this:
https://docs.kumomta.com/reference/http/api_inject_v1/#recipients
OK @faithful-ostrich Thanks the reply.