Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[9.5] - Missing information in some tickets when creating with mailgate #8383

Closed
andrepetinga opened this issue Dec 4, 2020 · 9 comments
Closed
Labels

Comments

@andrepetinga
Copy link

andrepetinga commented Dec 4, 2020

Describe the bug

We have noticied that some information is missing in some tickets, when created from mailgate.
We don't know why this is happening.

Here is an example. This is the end of the created ticket

image

And this is the end of the email present in the server

image

Notice that the text "jumps" from the signature of one person's email to the previous one

image

Expected behavior

Ticket should be created with all email information.

If you want, I can forward the email to your system configuration, so that we can check if it's created the same way.

@OscarBeiro
Copy link
Contributor

Olá André,

GLPI sanitizes emails before ticket been created. This is a complex subject as every email client has its own quirks.
For instance: Signatures (not always as you see) and especially on email replies, quoted text like the one on your example.

So, some elements are been removed, this is the default behaviour and I think it is OK.

Regards,

@andrepetinga
Copy link
Author

Yes, I understand there are several email clients... But this cases are complicated, because we may lose important information for the ticket. Of course if it says something like "according to the info below" and there is nothing below, we know something went wrong. But this is not always the case...
And we have many, many emails similar to this one, so I tried to understand what was the difference, but with no luck...

@tomolimo
Copy link
Contributor

tomolimo commented Jan 4, 2021

Hello @OscarBeiro
I totally agree with @andrepetinga: GLPI sanitize process must not delete content!
Thank you,
Regards,
Tomolimo

@FrankGraux
Copy link

We're experiencing the same issues with some e-mails. This is very annoying since now we cannot rely on the tickets to be complete.

@RodolpheLP
Copy link

Hello @OscarBeiro
I totally agree with @andrepetinga: GLPI sanitize process must not delete content!
Thank you,
Regards,
Tomolimo

Hello,
I'm agree with that you said : GLPI sanitize process must not delete content!
Some important information is missing regulary from mails integtrated by GLPI and technicians missed useful elements by this way.

Thanks if you could undone that, it'll be usefull.

Regards

@PatrickSiIva
Copy link

Hello there!

Under no circumstance mail content should be deleted or truncated.
I’ve upgraded from 9.4.5 to 9.5.3 and all seemed fine. Only a few weeks later down the road we noticed this issue because of costumers and technicians getting upset with the missleading info in the ticket.
I guess this is quite an issue. Anyone who relies on mailgate should not use version 9.5.2 or higher (I tested from 9.4.5 to 9.5.5). I’m amazed that there isn’t many complains about this issue here, maybe many others will only notice it when a customer reaches out.
I want to provide a mail for testing, but it’s gona take time to get rid of all sensitive info in it.

This is how I’m working around this for now….
We've turned off the mail gate and all tickets are been created manually by our N1 staff.
Since it’s hard to spot this issue in a timely manner and we’ve a considerable volume of tickets daily, backup doesn’t matter. I cannot just get rid of thousands of tickets =/
I’m trying to downgrade back to version 9.5.1 as there wasn’t a lot of changes in the database schema according with the migration log.
Migration to 9.5.2
glpi_appliancerelations (We have no management of appliances on glpi)
glpi_mailcollectors (I’m worried but it’s working on test environment)
glpi_appliances (We have no management of appliances on glpi)
glpi_states (We do not use the “ASSETS” module)
Migration to 9.5.3
Nothing

Just use the 9.5.1 app version and alter in the database glpi_config version and dbversion to 9.5.0. Yep, 9.5.ZERO.

@github-actions
Copy link
Contributor

There has been no activity on this issue for some time and therefore it is considered stale and will be closed automatically in 10 days.

If this issue is related to a bug, please try to reproduce on latest release. If the problem persist, feel free to add a comment to revive this issue.
If it is related to a new feature, please open a topic to discuss with community about this enhancement on suggestion website.

You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly.

@github-actions github-actions bot added the Stale label Sep 20, 2021
@andrepetinga
Copy link
Author

Hello.
This week I tried out 9.5.6 version of GLPI and the tickets were created with all the text original text!
So I guess this problem is fixed.
I've tested with all the problematic emails I've had (around 15 to 20) and all OK now.

@cedric-anne
Copy link
Member

Hi,

I guess it has been fied by #9251.

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants