Update problem from .179 --> .203 (outgoing email)

Discussion in 'Installation and setup (Kayako Download)' started by Mart Dirks, Mar 25, 2011.

  1. Mart Dirks

    Mart Dirks Member

    Hi,

    after the upgrade from .179 -> .203 I have problems with the outgoing e-mail.
    1. SMTP outgoing email is broken
    2. With PHP I got the old MIME problems.

    After replcing the new files in /__swift/thirdparty/XPM/PHP5 thru the files from .179 the SMTP problem is gone.

    Have someone else seen this problem?
     
  2. Jamie Edwards

    Jamie Edwards Chief Limey Staff Member

    Hi Mart,

    How is SMTP outgoing mail broken? Any errors in your error logs, is it a formatting issue?
     
  3. Ryan Lederman

    Ryan Lederman Kayako Guru

    Can you please let us know what OS your server runs, and if you know what vendor makes your SMTP server that as well?

    Thanks
     
  4. Mart Dirks

    Mart Dirks Member

    Sorry, on debugging are none errors found in logs.
    And none e-mail was send out on new tickets and replys on it.
    So i switched (back) to PHP-email and I become the old problem.:(
    Server config (is a internal test server)
    CentOs 5.5 (64 bits) (patchlevel: fully up-to-date) with Interworx Controlepanel (up-to-date) as VM on VMWare 4.0 ESXi
    PHP 5.2.17 / MySQL 5.0.77
    QMail 1.03
     
  5. David H

    David H Established Member

    I'm seeing the same thing. Upgraded last night and didn't realize none of the replies we've been sending since then were going anywhere. I just tested and it doesn't even make an SMTP connection. No errors in the error log.
     
  6. pcmnetmanage

    pcmnetmanage Member

    Mail on my system is functioning properly after the upgrade to .203.

    Server 2008
    IIS 7
    PHP 5.2.17
    MySQL 5.5.9
    SMTP Server: Exchange Server 2007
     
  7. David H

    David H Established Member

    Oh; forgot, I'm php 5.2.17 on centos 5.5 x86_64
     
  8. Mart Dirks

    Mart Dirks Member

    I changed in mime5.php

    PHP:
    class MIME5 {
        const 
    LE PHP_EOL;    // Line end sequence
    to
    PHP:
    class MIME5 {
        const 
    LE "\r\n";
    and outgoing SMTP is working.

    Start testing again.
     
  9. Mart Dirks

    Mart Dirks Member

    E-mail using outgoing SMTP:
    Code:
    Beste heer/mevrouw,
    
    Hierbij bevestigen wij dat u, als nieuwe klant of met een nieuw e-mailadres, succesvol bent aangemeld in onze helpdesk.
    
    Uw aanmeldgegevens zijn:
    E-mailadres: info@gewoon-it.nl
    Wachtwoord: **************
    
    U kunt onze helpdesk te allen tijde bezoeken op https://support.gewoon-it.nl/
    
    Mocht u nog vragen hebben, laat het ons dan a.u.b. weten.
    
    Met vriendelijke groet,
    
    Gewoon IT
    ________________________________________
    Helpdesk: https://support.gewoon-it.nl/index.php?
    
    Using PHP (direct):
    Code:
    X-MSMail-Priority: normal
    X-MimeOLE: Produced By Kayako Resolve v4.01.203
    X-Mailer: Kayako Resolve v4.01.203
    Reply-To: support@gewoon-it.nl
    Date: Sat, 26 Mar 2011 22:46:33 +0100
    Content-Type: multipart/alternative;
        boundary="=_1.0c213fbd238fb34c2d74e734306a67f5"
    MIME-Version: 1.0
    
    This is a message in MIME Format.
    If you see this, your mail reader does not support this format.
    
    --=_1.0c213fbd238fb34c2d74e734306a67f5
    Content-Type: text/plain;
        charset="UTF-8"
    Content-Transfer-Encoding: base64
    Content-Disposition: inline
    
    QmVzdGUgaGVlci9tZXZyb3V3LCAKCkhpZXJiaWogYmV2ZXN0aWdlbiB3aWogZGF0IHUsIG
    FscyBuaWV1d2Uga2xhbnQgb2YgbWV0IGVlbiBuaWV1dyBlLW1haWxhZHJlcywgc3VjY2Vz
    dm9sIGJlbnQgYWFuZ2VtZWxkIGluIG9uemUgaGVscGRlc2suCgpVdyBhYW5tZWxkZ2VnZX
    ZlbnMgemlqbjoKRS1tYWlsYWRyZXM6IGluZm9AZ2V3b29uLWl0Lm5sCldhY2h0d29vcmQ6
    IHVpcnF1NjI3OHkKClUga3VudCBvbnplIGhlbHBkZXNrIHRlIGFsbGVuIHRpamRlIGJlem
    9la2VuIG9wIGh0dHBzOi8vc3VwcG9ydC5nZXdvb24taXQubmwvCgpNb2NodCB1IG5vZyB2
    cmFnZW4gaGViYmVuLCBsYWF0IGhldCBvbnMgZGFuIGEudS5iLiB3ZXRlbi4KCk1ldCB2cm
    llbmRlbGlqa2UgZ3JvZXQsCgpHZXdvb24gSVQKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
    LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCkhlbHBkZXNrOiBodHRwczovL3N1cH
    BvcnQuZ2V3b29uLWl0Lm5sL2luZGV4LnBocD8=
    --=_1.0c213fbd238fb34c2d74e734306a67f5
    Content-Type: text/html;
        charset="UTF-8"
    Content-Transfer-Encoding: base64
    Content-Disposition: inline
    
    PGZvbnQgZmFjZT0iQ2FuZGFyYSwgVmVyZGFuYSwgQXJpYWwsIEhlbHZldGljYSIgc2l6ZT
    0iMyI+QmVzdGUgaGVlci9tZXZyb3V3LCA8YnIgLz4KPGJyIC8+CkhpZXJiaWogYmV2ZXN0
    aWdlbiB3aWogZGF0IHUsIGFscyBuaWV1d2Uga2xhbnQgb2YgbWV0IGVlbiBuaWV1dyBlLW
    1haWxhZHJlcywgc3VjY2Vzdm9sIGJlbnQgYWFuZ2VtZWxkIGluIG9uemUgaGVscGRlc2su
    PGJyIC8+CjxiciAvPgpVdyBhYW5tZWxkZ2VnZXZlbnMgemlqbjo8YnIgLz4KRS1tYWlsYW
    RyZXM6IGluZm9AZ2V3b29uLWl0Lm5sPGJyIC8+CldhY2h0d29vcmQ6IHVpcnF1NjI3OHk8
    YnIgLz4KPGJyIC8+ClUga3VudCBvbnplIGhlbHBkZXNrIHRlIGFsbGVuIHRpamRlIGJlem
    9la2VuIG9wIGh0dHBzOi8vc3VwcG9ydC5nZXdvb24taXQubmwvPGJyIC8+CjxiciAvPgpN
    b2NodCB1IG5vZyB2cmFnZW4gaGViYmVuLCBsYWF0IGhldCBvbnMgZGFuIGEudS5iLiB3ZX
    Rlbi48YnIgLz4KPGJyIC8+Ck1ldCB2cmllbmRlbGlqa2UgZ3JvZXQsPGJyIC8+CjxiciAv
    PgpHZXdvb24gSVQ8YnIgLz4KPEhSIHN0eWxlPSJtYXJnaW4tYm90dG9tOiA2cHg7IGhlaW
    dodDogMXB4OyBCT1JERVI6IG5vbmU7IGNvbG9yOiAjY2ZjZmNmOyBiYWNrZ3JvdW5kLWNv
    bG9yOiAjY2ZjZmNmOyIgLz4KSGVscGRlc2s6IGh0dHBzOi8vc3VwcG9ydC5nZXdvb24taX
    QubmwvaW5kZXgucGhwPzxiciAvPgo8L2ZvbnQ+
    --=_1.0c213fbd238fb34c2d74e734306a67f5--
    
     
  10. Viscott

    Viscott Established Member

    All my outgoing email is now broken as well with 4.01.204.
    Also after upgrading to 4.01.203 "Closed" tickets are now appearing in the inbox. Right now it should only be showing a total of 5 tickets.
    I upgraded to 4.01.204 as there was supposed to be a fix for that bug. Still broken :(
    Current Support Ticket: HYW-205-80166
     
  11. Mart Dirks

    Mart Dirks Member

    Even the update to .204 don't solved my e-mail problem.
    Again the workaround from post #8 solved this problem for SMTP.
    The problem from post #9 is still present (Html emails broken 4.01.139).

    Do you need more info on this?
     
  12. Ryan Lederman

    Ryan Lederman Kayako Guru

    The issue here is that a different line ending sequence needs to be used for PHP mail and for SMTP. For now, here's what I'd recommend:

    If you're using SMTP on any platform, set LE = "\r\n"

    If you're using PHP mail on *nix, set LE = "\n"

    If you're using PHP mail on Windows, set LE = "\r\n"
     
  13. ERIK TRUNKL

    ERIK TRUNKL Member

    Both, SMTP and PHPMail, not works editing the file as you said.

    I've got the same problem, until now unresolved.

    Not works. I can't understand how it could happen. Think with me, if it woks in all of verion 3, why not works in version 4 after many releases?

    ...
    Anyway, thank you so much...

    The same Ryan... Nothing...
     
  14. Ryan Lederman

    Ryan Lederman Kayako Guru

    Something else is going on with your installation; there are only two possible settings that work for this value, one is \n and one is \r\n. What happens when your desk should send mail? Does it silently fail? Do you have errors in your PHP log? This began happening when precisely?
     
  15. Ryan Lederman

    Ryan Lederman Kayako Guru

    @ERIK,

    Let's try this... in __swift/thirdparty/XPM/PHP5/MIME5.php, change

    PHP:
    const FOLD "\r\n\t";    // Header folding sequence
    to

    PHP:
    const FOLD "\n\t";    // Header folding sequence
    Viola?
     
  16. ERIK TRUNKL

    ERIK TRUNKL Member

    Hello Ryan,

    When I sent type a message with HTML tags, in StaffCP and Customer Ticket View OK either HTML either CRLF, but, Customer E-mail don't.

    If I use editing the file class.Controller_Ticket.php editing line 3131 it works, but WITHOUT CRLF.

    If I use without editing class.Controller_Ticket.php line 3131, it works, but customer's email, don't.

    I can't do the both, CRLF and HTML.
     
  17. ERIK TRUNKL

    ERIK TRUNKL Member

    Hm, I really would like to say viola, but, don't. Still the same.

    Note: I'm using the class.Controller_Ticket.php edited line 3131 - Not Works, but e-mail got HTML without CRLF
    Note: I'm using the class.Controller_Ticket.php ORIGINAL - Not Works, with CRLF, but without HTML and showing the Code, including AdminCP config right.

    Regards,
     
  18. Ryan Lederman

    Ryan Lederman Kayako Guru

    @ERIK, oh we must be talking about two separate things. We haven't offered an official patch to allow HTML tags to be typed in the reply box yet. Is that what your issue all boils down to?
     
  19. ERIK TRUNKL

    ERIK TRUNKL Member

    Yeah,

    As we talking about it in http://forums.kayako.com/threads/html-emails-broken-4-01-139.25384/. Mark told there here appears to be the solution for "HTML Emails Broken...". But isn't.

    I just understand how Kayako 3 works and 4 don't... =(
     
  20. Ryan Lederman

    Ryan Lederman Kayako Guru

    @ERIK, unfortunately, Mark was talking about a separate issue that other customers are experiencing with their outgoing mail. I'll take a look at your issue later this evening. Cheers.
     

Share This Page