1. Welcome to the feedback forum. Here's some tips for giving your suggestions the best shot:
    • Search before posting: See if someone else has already posted your suggestion. If you add your support to an existing, you're more likely to bubble up the request.
    • Keep one suggestion to one thread: Try not to club lots of different suggestions together in one thread. Otherwise, people will get confused about what they're voting for and we might miss your feedback.
  2. Kayako Download customers: we will continue to develop and support Kayako Download beyond July 2017, alongside the new Kayako for existing customers.

    Find out more.

  3. The forum you are viewing relates to Kayako Classic. If you signed up or upgraded to the new Kayako (after the 4th July 2016), the information in this thread may not apply to you. You can visit the forums for the new Kayako here.

Planned RFC 5965 compliance (ability to handle abuse reports in Kayako)

Discussion in 'Kayako product feedback and suggestions' started by Anthony Francis, May 4, 2012.

  1. This request is because we receive abuse complaints like:

    This report is in Abuse Reporting Format ("ARF", see RFC5965).
    As specified by this IETF standard, the complete headers and
    text are included in the message/rfc822 section of this email.
    Feedback-Type: abuse
    User-Agent: USFamilyReporting
    Version: 0.1

    This is an issue because kayako no longer has the ability to show you the entire email including headers, so we have to go dig through the parser logs to get the rest of the complaint.

    More and more I am feeling that while Kayako 3 was uglier, it was more functional, and that is sad because kayako 3 was broken in several ways as well.
  2. Drew Keller

    Drew Keller Just one person in a world of millions.

    I know this is not a full solution, but if you have a look at http://forge.kayako.com/screenshots/89/view on forge, you will see Gary has made some changes to allow the header from the Parser log to be displated on the ticket post.
  3. Thanks for the info!
  4. Turns out that this was not effective. Thanks anyway.
  5. Gary McGrath

    Gary McGrath Staff Member

    Hi Anthony,

    Why was it not effective?

  6. Ah sorry, Because it only shows the standard headers and still omits the message RFC822 headers. The old show headers function showed the entire raw email as it was received.
  7. Anadi Raj Tiwari

    Anadi Raj Tiwari Kayako Staff

Share This Page