alberto

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • in reply to: Email Piping #4241
    alberto
    Participant

    Hello,

    No, I dont have any custom plugin.

    It creates a message after the user send the first message.

    Thanks

    in reply to: Email Piping #4204
    alberto
    Participant

    Hi,

    Yeah. Now I see it works. I didnt work though with email aliases, as in my prior case.

    But right now, everytime I register a new user, an automatic message is sent saying: “body was binary”. I really dont know what it is all about.

    in reply to: Email Piping #4197
    alberto
    Participant

    Hi Shamim,

    I think you replied to another request. Could you find out about my problem? I see you placed a “body is a binary” but I dont know what you mean.

    Thank you

    in reply to: Email Piping #4185
    alberto
    Participant
    This reply has been marked as private.
    in reply to: Email Piping #4073
    alberto
    Participant

    Ok, I figured out the path thanks to the link below:

    Now I dont get a mailer daemon email with an error (not in the recipient inbox nor in the sender inbox – I really got the two cases) and when writting from the FEP, there is no problem. The recipient gets the message and the email… BUT, if the recipient replies the email (yes, with a key in the subject line), there is not a registration in the FEP. I thought that was the whole point of email piping.

    Am I getting it wrong?

    in reply to: Translation issue #4070
    alberto
    Participant

    I just edited the plugin and got (temporarely) out of the problem.

    in reply to: Email Piping #4049
    alberto
    Participant

    Hi, so…how do we get the piping path set up correctly?
    I followed all the instructions but Im getting a “delivery failure” message. Yes, message has a [KEY…] into the subject line.

    this is what I get:
    This message was created automatically by mail delivery software.

    A message that you sent could not be delivered to one or more of its
    recipients. This is a permanent error. The following address(es) failed:

    pipe to |/home/jyrriwdv/public_html/wp-content/plugins/front-end-pm-pro/pro/fep-email-parser/email-piping.php
    generated by clientes@legalprojectsonline.com

    The following text was generated during the delivery attempt:

    —— pipe to |/home/jyrriwdv/public_html/wp-content/plugins/front-end-pm-pro/pro/fep-email-parser/email-piping.php
    generated by clientes@legalprojectsonline.com ——

    Error in argument 1, char 3: option not found
    Usage: php-cgi [-q] [-h] [-s] [-v] [-i] [-f <file>]
    php-cgi <file> [args…]
    -a Run interactively
    -b <address:port>|<port> Bind Path for external FASTCGI Server mode
    -C Do not chdir to the script’s directory
    -c <path>|<file> Look for php.ini file in this directory
    -n No php.ini file will be used
    -d foo[=bar] Define INI entry foo with value ‘bar’
    -e Generate extended information for debugger/profiler
    -f <file> Parse <file>. Implies `-q’
    -h This help
    -i PHP information
    -l Syntax check only (lint)
    -m Show compiled in modules
    -q Quiet-mode. Suppress HTTP Header output.
    -s Display colour syntax highlighted source.
    -v Version number
    -w Display source with stripped comments and whitespace.
    -z <file> Load Zend extension <file>.
    -T <count> Measure execution time of script repeated <count> times.
    Reporting-MTA: dns; lake15.banahosting.com

    Action: failed
    Final-Recipient: rfc822;|/home/jyrriwdv/public_html/wp-content/plugins/front-end-pm-pro/pro/fep-email-parser/email-piping.php
    Status: 5.0.0

Viewing 7 posts - 1 through 7 (of 7 total)