PEAR Bug Search Results

Mail: Bug 16818 [Open] Validation Failed Error when entering a dot in FROM Header

yassinebelc at hotmail dot fr — 2009-11-21T22:55:46+00:00

Mail Bug
Reported by yassineb
2009-11-21T22:16:17+00:00
PHP: 5.2.8 OS: Linux CentOS 5.3 Package Version: 1.2.0b2

Description:
------------
Hello,
I get Validation Failed error when the From Header contains a "dot":
Validation failed for: FileHost Script V.1.7 


when i remove the "dot" the message get sent:
          $headers = array (
            'MIME-Version' => '1.0',
            'Content-type' => 'text/html; charset=iso-8859-1',
            'From' => str_replace(".", "", $settings['site_title'])." <".EMAIL_FROM_ADDR.">",
            'To' => $email,
            'Subject' => $subject);


Thanks.

Mail: Feature/Change Request 16432 [Open] Would you release 1.2.0b2 as a stable, please.

alan at ridersite dot org — 2009-07-16T00:09:57+00:00

Mail Feature/Change Request
Reported by ridera
2009-07-12T21:46:45+00:00
PHP: 5.2.5 OS:  Package Version: 1.2.0b2

Description:
------------
Would you release 1.2.0b2 as a stable, please.

Reason I'm asking is that I use mail() on shared hosts and the providers won't upgrade to betas. Thus, I'm stuck with using the old 1.1.14

Mail: Documentation Problem 15620 [Open] Please update package license

thijs at debian dot org — 2009-10-14T19:31:37+00:00

Mail Documentation Problem
Reported by thijs
2009-01-12T15:51:01+00:00
PHP: Irrelevant OS:  Package Version: 1.2.0b1

Description:
------------
Hi,

The package is now licensed under a combination of PHP 2.02 and BSD licenses.

There are some problems with the PHP 2.02 license; for example it states that "This software includes Zend" and "This software includes PHP", which is not the case for this module.

Would it be possible to update the license? My proposal would be to license all files under the BSD license, so the whole package gets one license, and the BSD license is a widely known liberal open source license. As (in my opinion less preferred) alternative would be to upgrade to version 3.01 of the PHP license.

thanks,
Thijs

Mail: Bug 13659 [Verified] Mail parse error in special condition

miklos at krivan dot hu — 2008-04-17T09:05:27+00:00

Mail Bug
Reported by mkrivan
2008-04-12T21:42:40+00:00
PHP: 5.2.5 OS: Windows XP Package Version: 1.1.14

Description:
------------
In special circumstances the parsing fail. If some partial text in string is the same, like mailbox name and comment, the parsing will be failed. I also have written a suggestion to solve the problem because I have found the suspicious place in the code.

Thanks for your help.

Test script:
---------------
$address = '"Test Student"  (test)';
$addresses = Mail_RFC822::parseAddressList( $address, 'anydomain.com', TRUE );



Expected result:
----------------
The result should give the parsed email into the following parts:

person: Test Student
mailbox: test
host: mydomain.com
comment: test


Actual result:
--------------
The suspicious code in RFC822.php

            // Catch any RFC822 comments and store them separately.
            $_mailbox = $mailbox;
            while (strlen(trim($_mailbox)) > 0) {
                $parts = explode('(', $_mailbox);
                $before_comment = $this->_splitCheck($parts, '(');
                if ($before_comment != $_mailbox) {
                    // First char should be a (.
                    $comment    = substr(str_replace($before_comment, '', $_mailbox), 1);
                    $parts      = explode(')', $comment);
                    $comment    = $this->_splitCheck($parts, ')');
                    $comments[] = $comment;

                    // +1 is for the trailing )
                    $_mailbox   = substr($_mailbox, strpos($_mailbox, $comment)+strlen($comment)+1);
                } else {
                    break;
                }
            }

            foreach ($comments as $comment) {
                $mailbox = str_replace("($comment)", '', $mailbox);
            }


I would suggest this:

        // Catch any RFC822 comments and store them separately.
        $p = $q = false;
        do {
          $p = strrpos( $mailbox, '(' ); // last occured
          $q = strpos( $mailbox, ')', $p === false ? 0 : $p );
          if( $p === false || $q === false ) break;
          $comments[] = substr( $mailbox, $p + 1, $q - $p -1 );
          $mailbox = substr( $mailbox, 0, $p ).substr( $mailbox, $q + 1 );
          // delete found comment from mailbox
        } while( true );

        if( $p !== false || $q !== false ) { // there is an error
            $this->error = 'Invalid address spec. Unmatched quote or bracket ()';
            return false;
        }

Mail: Feature/Change Request 13587 [Open] relay params like "NOTIFY=SUCCESS,FAILURE"

positron at gmx dot ch — 2008-04-06T02:19:21+00:00

Mail Feature/Change Request
Reported by alex2000
2008-04-04T06:31:35+00:00
PHP: 5.2.0 OS: SuSe 10.2 Package Version: 1.1.14

Description:
------------
Here:

http://pear.php.net/package/Mail/docs/1.1.14/__filesource/fsource_Mail__Mail-1.1.14Mailsmtp.php.html , line 204 anybody have to place 4th parameter like $params and at the line 282 instead $this->_smtp->rcptTo($recipient) have to write $this->_smtp->rcptTo($recipient, $params) or somethins like that.

Because I need this optional notify - flags and have to change it each time manually :(

Can anybody do it for the next relase - or maybe another solution /way for the same problem.

Thanks.

Mail: Feature/Change Request 12557 [Open] Use mb_send_mail() if available

derernst at gmx dot ch — 2007-11-30T06:04:50+00:00

Mail Feature/Change Request
Reported by derernst
2007-11-30T06:04:50+00:00
PHP: 5.2.2 OS:  Package Version: 1.1.14

Description:
------------
In multilanguage environments working with the mbstring extension is very handy. Anyway, on shared hosting, function overloading is often not available, as mbstring.func_overload   cannot be set at runtime but only at system level. In these cases, the Mail classes use the mail() function, though mb_send_mail() would actually be available. 

I think it would be nice to introduce an option to use mb_send_mail() where it is available.

Mail: Feature/Change Request 12478 [Open] hide PHP warnings, raised from PHP functions used in the class

carsten_sttgt at gmx dot de — 2007-11-18T19:48:42+00:00

Mail Feature/Change Request
Reported by cwiedmann
2007-11-18T19:48:42+00:00
PHP: Irrelevant OS: Windows_NT Package Version: CVS

Description:
------------
Hello,

Mail_smtp:
For example, if you use mail() on Windows, and the mailserver is down, mail() returns false, and the class returns a PEAR::Error Object. But PHP also outputs a "Warning" with a failure description.

It would be nice, to not see this "Warning". Instead having the description in PEAR::Error->getUserInfo() / getDebugInfo().

That's my most important issue. For example in Mail_smtp you also hide the error in popen.

Mail_smtp:
It would be nice, if this class returns only a PEAR::Error and no PHP warning if Net/SMTP.php is not installed. Like it happend, if the Net_SMTP instance can not be created.

Mail_smtpmx:
It would be nice, if this class returns only a PEAR::Error and no PHP warning if Net/DNS is not installed.

Mail_sendmail:
IMHO the default args should be "-t -i". And not only "-i".

I have attached a patch, which fix this issues for me.

Regards,
Carsten

Mail: Feature/Change Request 8818 [Open] Request Option to suppress email address validation (allow RFC OK fringe cases)

scottprive at gmail dot com — 2006-10-24T16:01:40+00:00

Mail Feature/Change Request
Reported by scottprive@...
2006-09-29T17:00:19+00:00
PHP: 5.1.4 OS: Linux Fedora Package Version: 1.1.13

Description:
------------
Requestion an option to completely suppress email address validation. The validation has its uses, but gets in the way of server testing. Two use cases:

1) Server testing (spam relay tests, destructive string tests, etc)

2) Current validation is simple and restrictive, blocking special characters even if they are used in a RFC 3696 valid context:
`domain literals'
"someone@example.com"
possibly others.

I have attempted to disable the raising of RFC822.php errors in Mail.php but have failed (I have begun studying the OO code, but my background is 'function-based' PHP).
 

Test script:
---------------
 'mail.example.com',
        'port'      => 25,
        'localhost' => 'test.example.com',
        'timeout'   => 240,
        'debug'     => TRUE,
        'persist'   => FALSE,
    );


    $body = "
This is a test, which fails on Mail address validtion. ";

    $message =& Mail::factory('smtp',$params);
    $emailresult = $message->send($to, $headers, $body);
    print "\n RESULT CODE looks like: $emailresult\n";
    print "\n RESULT OBJECT looks like:";
    print_r($emailresult);
?>


Expected result:
----------------
The contents of $to become (IN-cluding quotes):
"user name@example.com"

Personally I don't advise or support users with such gray area usernames. The purpose in feeding the RCPT TO with unusual data is to test the target mailserver to see if it is an "open relay". While the simplest test is to use mailbox@not-your-domain.com, there are another 15-20 testcases using quotes and escaping in an attempt to trick the SMTP server in accepting the email.

Mail.php seems very suited (and more) for such an exercise.



Actual result:
--------------
 RESULT OBJECT looks like:PEAR_Error Object
(
    [error_message_prefix] =>
    [mode] => 1
    [level] => 1024
    [code] =>
    [message] => Validation failed for: "user name@example.com"
    [userinfo] =>
    [backtrace] => Array
        (
            [0] => Array
                (
                    [file] => /usr/share/pear/PEAR.php
                    [line] => 566
                    [function] => PEAR_Error
                    [class] => PEAR_Error
                    [object] => PEAR_Error Object
 *RECURSION*
                    [type] => ->
                    [args] => Array
                        (
                            [0] => Validation failed for: "user name@example.com"
                            [1] =>
                            [2] => 1
                            [3] => 1024
                            [4] =>
                        )

                )

            [1] => Array
                (
                    [file] => /usr/share/pear/Mail/RFC822.php
                    [line] => 198
                    [function] => raiseError
                    [class] => PEAR
                    [object] => Mail_RFC822 Object
                        (
                            [address] =>
                            [default_domain] => localhost
                            [nestGroups] =>
                            [validate] => 1
                            [addresses] => Array
                                (
                                    [0] => Array
                                        (
                                            [address] => "user name@example.com"
                                            [group] =>
                                        )

                                )
...