• Deutsch
  • English
  • Anmeldung OTOBO Community
+49 (0)9427 68 39 000
OTOBO
  • SOFTWARE
    • Software | Überblick
    • IT Service Management
    • Customer Service Management
    • Enterprise Service Management
    • Demo
    • Download
    • Dokumentation
  • SERVICES
    • Überblick Services
    • Beratung
    • Training
    • Entwicklung
    • OTRS Migration zu OTOBO
    • Support
    • Managed Service
    • Support-Portal
  • UNTERNEHMEN
    • Über uns
    • Karriere
    • Partner
    • Kontakt
    • Newsletter
  • RESSOURCEN
  • COMMUNITY
    • Open Source
    • Community Forum
    • Download
    • Dokumentation
    • OTOBO übersetzen
  • Click to open the search input field Click to open the search input field Suche
  • Menü Menü
Ansicht von 0 Antwort-Threads
  • Autor
    Beiträge
    • 12. August 2021 um 11:44 Uhr - Views: 748 #11816
      Antoine Lacroix
      Teilnehmer

        Hello everyone,

        I already posted about this problem some months ago, haven’t got a precise answer because the said issue is closely related to our company AD but I was able to patch it up. Now I’m back with the same question as my fix doesn’t work anymore with the new updates and I’m back with the same problem.

        To put it in a nutshell, when we (the agents) reply to a customer ticket, the „To“ field is supposed to autofill itself(with something like „Firstname Lastname <firstname.lastname@companymail.com>“). However that’s not exactly what happens, as for some reasons the first name is also added within the email address at the end like such : <firstname.lastname@companymail.com firstname>, thus making our mail server deny any ticket answer that has the „To“ field autofilled and forcing us to retype the address of every customer we answer to. What’s really weird is that when we go to the customer screen, the mail field is registered correctly for everyone. The problem only appears when we answer a ticket or select a customer from the agenda. My guesses would be that for some obscure reason the Mail::Address parse function doesn’t work properly with our AD linked customer objects but I might be wrong.

        My main question here isn’t how to solve the problem (well it is but we already tried it and it’s unlikely you’ll find the cause of it without having the whole architecture under you sight), I’m just wondering where and how does the autofill get the (wrong) informations it has ? My guess is that it just convert the Customer object into a HTML data object then use the Mail::Address parse() function to extract the address but I may be wrong. Does anyone knows precisely how that autofill works ?

         

        Thanks in advance to anyone that read that whole post or that’ll try to help.

    • Autor
      Beiträge
    Ansicht von 0 Antwort-Threads
    • Du musst angemeldet sein, um auf dieses Thema antworten zu können.

    Foren durchsuchen

    Anmeldung

    Anmeldung

    Konto erstellen
    Passwort vergessen?

    Login via Social

    Profil

    Bitte vervollständigen Sie nach der Registrierung Ihr Profil, das vereinfacht die spätere Kommunikation enorm. Ihre Profileinstellung finden Sie, wenn Sie auf Ihr Avatarbild klicken.

    Sie können Ihren Avatar ändern, indem Sie sich mit Ihrer E-Mail-Adresse unter gravatar.com registrieren.

    Letzte Aktivitäten

    • Dynamische Felder in AgentTicketNote mit ACL verstecken
    • FAQ: kaputtes Copy & Paste von Bildern zwischen Artikeln
    • Benachrichtigung „Ticket wurde mir entzogen“ möglich?
    • Statistik Anzahl Tickets pro Agent
    • Docker: Ändern des redis Hosts

    Unternehmen

    Über uns
    Karriere
    Stellenbörse
    Partner werden
    Kontakt
    Newsletter

    OTOBO | Simplify work and create exceptional service experiences.

    Die Source Code Owner und Maintainer hinter OTOBO.

    Software

    Service Management-Plattform
    OTOBO Demo
    OTOBO Download
    OTOBO Dokumentation

    Security-Problem melden:
    security@otobo.org

    Services

    Support-Portal
    Beratung
    Training
    Support
    Managed Services
    Erweiterung
    OTRS Migration
    Partner finden

    Community

    Open Source
    Community Forum
    Mitmachen
    OTOBO Developer
    OTOBO@GitHub

    © 2026 Rother OSS GmbH | All rights reserved.
    • Cookie-Einstellungen
    • Impressum
    • Datenschutz
    • Haftungsausschluss
    Nach oben scrollen Nach oben scrollen Nach oben scrollen