Autoresponder failure

  • Today i made an upgrade from 1.3.8 to 1.3.16 on Debian Jessie.


    A customer got a bounce-mail after sending an email to a forward-address with autoresponder. The email got correctly forwarded, but the autoresponder failed:


    Code: /var/log/mail.log
    1. Jan 19 18:34:57 hosting5 postfix/pipe[25797]: A542960B75: to=<[email protected]>, orig_to=<[email protected]>, relay=imscp-arpl, delay=0.38, delays=0.16/0.01/0/0.22, dsn=5.3.0, status=bounced (Command died with status 255: "/var/www/imscp/engine/messenger/imscp-arpl-msgr". Command output: [_[0;31mFATAL_[0m] main: Can't call method "isa" on an undefined value at /usr/share/perl5/MIME/Parser/Reader.pm line 186, <STDIN> line 1. [_[0;31mERROR_[0m] Could not to open log file `/var/log/imscp/imscp-arpl-msgr:imscp-arpl-msgr.log' for writting: Permission denied )
    2. Jan 19 18:34:57 hosting5 postfix/pipe[25799]: A542960B75: to=<[email protected]>, orig_to=<[email protected]>, relay=imscp-arpl, delay=0.38, delays=0.16/0.01/0/0.21, dsn=5.3.0, status=bounced (Command died with status 255: "/var/www/imscp/engine/messenger/imscp-arpl-msgr". Command output: [_[0;31mFATAL_[0m] main: Can't call method "isa" on an undefined value at /usr/share/perl5/MIME/Parser/Reader.pm line 186, <STDIN> line 1. [_[0;31mERROR_[0m] Could not to open log file `/var/log/imscp/imscp-arpl-msgr:imscp-arpl-msgr.log' for writting: Permission denied )

    I could not reproduce the error. Autoresponder and forwarding seems to work (no errors while testing)...

  • Tagged as "not a bug".

    Simply because I cannot reproduce.


    Customer reported another error.


    Without further information, we cannot help, nor reproduce your problem.

    • What was the content of the forwared mail? Any attachment? Message size? What was the error? What about log? Any special character?
    • What is the content of the autoresponder message? Any special character?

    Also, in your first message, there is an error about permissions on /var/log/imscp/imscp-arpl-msgr:imscp-arpl-msgr.log but you don't provide us the current permissions...


    To resume, if you want any help, provide us all information ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • I'm sorry :)


    Now i can reproduce the error. It really seems to be a special character.


    First of all the logfile. I'm a bit confused about the colon in path. But if i interpret that as slash:


    Code
    1. root@hosting5:/var/log/imscp/imscp-arpl-msgr# ls -altotal 40drwxr-x--- 2 vmail imscp 4096 Nov 29 09:17 .drwxr-x--- 3 root imscp 36864 Jan 23 09:03 ..-rw------- 1 vmail imscp 0 Jan 19 10:52 imscp-arpl-msgr.log

    To reproduce i created a new mail address with a autoresponder (nothing special - just the word "Antwort") and send an email via php script to that address. In the mail-body i used some wired special chars.




    PHP: test_mail.php
    1. <?php$message = "�";mail("[email protected]","Test",$message);?>

    (Ansi-coded file. Hex: FDFF)



    What it does:




    I'm quite sure that this first happened after the update from 1.3.8 to 1.3.16.

  • (Ansi-coded file. Hex: FDFF)

    You mean the ï character (239) from the Windows-1252?

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Originally it should be a ö (ö) after some (wrong) conversion... I just copied the character from a mail, that caused the error.


    I attached the php-file as zip. Hopefully that works.

    Files

    • test_mail.zip

      (245 Byte, downloaded 3 times, last: )
  • To clarify: I just used a php-script to reproduce the error. The original error occurred (multiple times now) with a normal email which a customer received.

    Edited once, last by comTim ().

  • @comTim


    Best would be to provide us the mail source. (privately if needed).

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206