Hi All,
I need help, I have look in the forum and have come across similar issues but I still can not resolve, I have used an example that I found, but I even get it if I do not use any tags. I am stumped and do not know what else to try.
Thank you for your help.
Regards,
Tosh.
Version
OTRS - 4.0.8
Postgres - 9.4
Centos 7
Admin - NotificationEvent
Name: Default Close Ticket Notification
Valid: Valid
Recipient: Agent (Owner) and Customer
Event: TicketStateUpdate
State: closed successful and closed unsuccessful
Subject: Closed (<OTRS_TICKET_Title[100]>)
Text:
This ticket <OTRS_TICKET_Title[100]> has been closed.
Please don't reply to this message unless for some reason you do not feel this ticket needs to be closed.
You can track your ticket here:
<OTRS_CONFIG_HttpType>://<OTRS_CONFIG_FQDN>/<OTRS_CONFIG_ScriptAlias>customer.pl?Action=CustomerTicketZoom&TicketID=<OTRS_TICKET_TicketID>
Logs.
admin - syslog
Sent customer 'Default Close Ticket Notification' notification to
ERROR: invalid byte sequence for encoding "UTF8": 0xa0, SQL: 'INSERT INTO article (ticket_id, article_type_id, article_sender_type_id, a_from, a_reply_to, a_to, a_cc, a_subject, a_message_id, a_message_id_md5, a_in_reply_to, a_references, a_body, a_content_type, content_path, valid_id, incoming_time, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
ERROR: invalid byte sequence for encoding "UTF8": 0xa0
Moderator: crythias
Re: ERROR: invalid byte sequence for encoding "UTF8": 0xa0
Hi all,
I got it to work using the following:
--------------------------------------------------
Hi <OTRS_CURRENT_UserFirstname>,
there is a new ticket in "<OTRS_TICKET_Queue>"!
<OTRS_CUSTOMER_FROM> wrote:
<OTRS_CUSTOMER_EMAIL[16]>
<OTRS_CONFIG_HttpType>://<OTRS_CONFIG_FQDN>/<OTRS_CONFIG_ScriptAlias>index.pl?Action=AgentTicketZoom;TicketID=<OTRS_TICKET_ID>
-----------------------------------------------------
But when I change it to the following:
-----------------------------------------------------
Hi <OTRS_CURRENT_UserFirstname>,
Please do not reply to this email, as this is to confirm that your support ticket has been closed. If you still consider the case open please email address@something.com and in the Subject field quote Ticket#<OTRS_TICKET_TicketNumber>.
<OTRS_CUSTOMER_FROM> wrote:
<OTRS_CUSTOMER_EMAIL[16]>
Your reference number is Ticket#<OTRS_TICKET_TicketNumber>
Your OTRS Notification Master
This may be a bug, because I don't understand why; when you change some text you get the UTF8 error.
Thank you for your help.
Regards,
Tosh.
I got it to work using the following:
--------------------------------------------------
Hi <OTRS_CURRENT_UserFirstname>,
there is a new ticket in "<OTRS_TICKET_Queue>"!
<OTRS_CUSTOMER_FROM> wrote:
<OTRS_CUSTOMER_EMAIL[16]>
<OTRS_CONFIG_HttpType>://<OTRS_CONFIG_FQDN>/<OTRS_CONFIG_ScriptAlias>index.pl?Action=AgentTicketZoom;TicketID=<OTRS_TICKET_ID>
-----------------------------------------------------
But when I change it to the following:
-----------------------------------------------------
Hi <OTRS_CURRENT_UserFirstname>,
Please do not reply to this email, as this is to confirm that your support ticket has been closed. If you still consider the case open please email address@something.com and in the Subject field quote Ticket#<OTRS_TICKET_TicketNumber>.
<OTRS_CUSTOMER_FROM> wrote:
<OTRS_CUSTOMER_EMAIL[16]>
Your reference number is Ticket#<OTRS_TICKET_TicketNumber>
Your OTRS Notification Master
This may be a bug, because I don't understand why; when you change some text you get the UTF8 error.
Thank you for your help.
Regards,
Tosh.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: ERROR: invalid byte sequence for encoding "UTF8": 0xa0
it's likely a copy/paste error.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: ERROR: invalid byte sequence for encoding "UTF8": 0xa0
Thanks crythias,
Not sure as the original message was cut & paste - worked ok sending closed email messages. Then I started to hand craft the message using "please do not reply .etc." and started getting the errors.
I have noted that the Notification event - notification article type has been set to email-notification-ext.
When I c&p the message first, when I closed the message I did not change the note type (note-internal - Defaults) and the message would email the customer. But once I changed the message it would error with the UTF8 issue.
So I tried again with note-external and it sent the message:
-------------------------------------------------
Hi Agent,
Please do not reply to this email, as this is to confirm that your support ticket has been closed. If you still consider the case open please email othername@some.company and in the Subject field quote Ticket#000180.
"Somename" <name@some.company>, wrote:
test
test
Your reference number is Ticket#000180
Your OTRS Notification Master
-------------------------------------------------------
So it sends but why did it work with the original message then when I change it, I would get and UTF8 error. maybe a small bug?
Regards,
Tosh.
Not sure as the original message was cut & paste - worked ok sending closed email messages. Then I started to hand craft the message using "please do not reply .etc." and started getting the errors.
I have noted that the Notification event - notification article type has been set to email-notification-ext.
When I c&p the message first, when I closed the message I did not change the note type (note-internal - Defaults) and the message would email the customer. But once I changed the message it would error with the UTF8 issue.
So I tried again with note-external and it sent the message:
-------------------------------------------------
Hi Agent,
Please do not reply to this email, as this is to confirm that your support ticket has been closed. If you still consider the case open please email othername@some.company and in the Subject field quote Ticket#000180.
"Somename" <name@some.company>, wrote:
test
test
Your reference number is Ticket#000180
Your OTRS Notification Master
-------------------------------------------------------
So it sends but why did it work with the original message then when I change it, I would get and UTF8 error. maybe a small bug?
Regards,
Tosh.