PEAR Bug Search Results

Mail: Documentation Problem 29030 [Open] User note that is a documentation problem

aaron at wormus dot com — 2025-02-19T08:21:05+00:00

Mail Documentation Problem
Reported by wormus
2025-02-19T08:21:05+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 

Manual page: package.mail.mail.factory.php
Note submitter:
Sergio Basto 

The undocumented parameter: socket_options , let me authenticate when I got this error: \r\n authentication failure [SMTP: STARTTLS failed (code: 220, response: TLS go ahead)]\r\n\r\nI just need add : \r\n    \'auth\' => \"PLAIN\",\r\n   \'socket_options\' => array(\'ssl\' => array(\'verify_peer_name\' => false)),\r\n

Mail: Bug 21117 [Open] Mitigate STRIPTLS Attack Vector

JunkYardMail1 at Frontier dot com — 2017-05-09T18:59:42+00:00

Mail Bug
Reported by noyb
2016-09-15T00:42:41+00:00
PHP: 5.6.25 OS: FreeBSD 11.0-RC2 Package Version: 1.3.0

Description:
------------
 
Please add option to specify that TLS is required so that if the server does not support STARTTLS mail client will not continue with an unsecure connection.
 
Opportunistic TLS aka STARTTLS
Weaknesses and Mitigations
https://en.wikipedia.org/wiki/Opportunistic_TLS#Weaknesses_and_mitigations
 
"STRIPTLS attacks can be blocked by configuring SMTP clients to require TLS for outgoing connections (for example, the Exim Message transfer agent can require TLS via the directive "hosts_require_tls" [12])."
 
I've done this crudely with a few modifications to the Mail_smtp and Net_smtp classes.  But I'm sure someone who knows PEAR::Mail inside and out can do it much better.
 
Basically what I did was to add a 'require_tls' var to the Mail_smtp and Net_smtp classes.  And defaulted it to true.  Then added a test for 'require_tls' in the auth function.
 
        /* Or if TLS is required and aren't already connected over a secure
         * (SSL) socket connection. */
        if (($tls && version_compare(PHP_VERSION, '5.1.0', '>=')
            && extension_loaded('openssl') && isset($this->esmtp['STARTTLS'])
            && strncasecmp($this->host, 'ssl://', 6) !== 0
           ) || $this->require_tls && strncasecmp($this->host, 'ssl://', 6) !== 0
        ) {
            /* Start the TLS connection attempt. */
 
Thanks

Mail: Feature/Change Request 21043 [Open] empty queued_as by pipelining

degtyaryov at gmail dot com — 2016-03-22T11:12:46+00:00

Mail Feature/Change Request
Reported by degtyaryov
2016-03-22T11:12:46+00:00
PHP: Irrelevant OS: Fedora 23 Package Version: 1.3.0

Description:
------------
Hello.

I logged information sent emails including queued_as.

Using pipelining is not possible to get a list of queued_as for 
sended letters.

Mail/smtp.php:306
list(,$args) = $this->_smtp->getResponse();
if (preg_match("/Ok: queued as (.*)/", $args, $queued)) {
	$this->queued_as = $queued[1];
}

$this->queued_as already empty!

Need limit pipelining commands and parse all matches:
public function send($recipients, $headers, $body, Closure 
$callback)
{
............
if ($this->isPipelingLimit) {
  $this->_smtp->pipelining = false
}
$res = $this->_smtp->data($body, $textHeaders);
$this->_smtp->pipelining = true;
list(,$args) = $this->_smtp->getResponse();
if (preg_match_all("/Ok: queued as (.*)/", $args, $queued)) {
    foreach($queued[1] as $key => $q)
	$this->callbacks[$key]($q);
    }
}

Example using:
............
$mail_factory->send($email, $headers, $body, 
function($queued_as) use ($email) {
  syslog(LOG_INFO, "$email queued as $queued_as");
});

Mail: Feature/Change Request 19628 [Open] DKIM Signing No Work

scott at realorganized dot com — 2023-08-08T22:29:49+00:00

Mail Feature/Change Request
Reported by scottschmitz
2012-10-01T20:10:19+00:00
PHP: Irrelevant OS: Linux Package Version: 1.2.0

Description:
------------
I send a message using SMTP Pear Mail to my Gmail email 
address.  I have turned on the DKIM Signing option in my 
CPanel.

I get an error in the headers of my GMail message:



Delivered-To: sschmitz99@gmail.com
Received: by 10.220.48.85 with SMTP id q21csp52374vcf;
        Mon, 1 Oct 2012 07:50:06 -0700 (PDT)
Received: by 10.224.203.193 with SMTP id 
fj1mr37404599qab.13.1349103004503;
        Mon, 01 Oct 2012 07:50:04 -0700 (PDT)
Return-Path: 
Received: from server.realtyjuggler.com 
(server.realtyjuggler.com. [199.230.52.14])
        by mx.google.com with ESMTPS id 
hp7si2609423qab.116.2012.10.01.07.50.03
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 01 Oct 2012 07:50:04 -0700 (PDT)
Received-SPF: pass (google.com: domain of 
administrator@scottschmitz.com designates 199.230.52.14 as 
permitted sender) client-ip=199.230.52.14;
Authentication-Results: mx.google.com; spf=pass (google.com: 
domain of administrator@scottschmitz.com designates 
199.230.52.14 as permitted sender) 
smtp.mail=administrator@scottschmitz.com; dkim=hardfail 
header.i=@scottschmitz.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; 
c=relaxed/relaxed; d=scottschmitz.com; s=default;
	h=Content-Type:Message-Id:MIME-
Version:Date:Subject:To:From; 
bh=ir+2fndDBR2VGsqqwOL8N9Lry+da7RSB/GATx9/cV+U=;
	b=vl8DohJm7wVPKDzmbv+a4wr4+HA2IGbS4skiT7OKpvXS
Gqc8xQbgE1lqYi5mcQ52DJc5OBe3A667XB1DIxmpLCONpnusoZM
kEEQX4+CcJpptHv2keyfljIiBvRNrPOIM;
Received: from [199.230.52.15] (port=37657 helo=localhost)
	by server.realtyjuggler.com with esmtpsa (TLSv1:AES256-
SHA:256)
	(Exim 4.77)
	(envelope-from )
	id 1TIhJq-0002YJ-JU
	for sschmitz99@gmail.com; Mon, 01 Oct 2012 10:50:02 
-0400
From: "RealtyJuggler Administrator" 

To: "Scott Schmitz" 
Subject: Welcome to RealtyJuggler Desktop 90 day FREE Trial
Date: Mon, 01 Oct 2012 10:50:01 -0400
MIME-Version: 1.0
X-Sender: administrator@scottschmitz.com
Message-Id: 
<5069ad9c.47dae00a.2fd1.5ee7SMTPIN_ADDED@mx.google.co
m>
X-Mailer: RJ SMTP
Content-Type: multipart/alternative; 
boundary="RJ_40b6a5e411d432cbe3ad500484fa2f6a_alt"
X-AntiAbuse: This header was added to track abuse, please 
include it with any abuse report
X-AntiAbuse: Primary Hostname - server.realtyjuggler.com
X-AntiAbuse: Original Domain - gmail.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - scottschmitz.com


Expected result:
----------------
I would expect that GMail would say Pass when I send a DKIM 
signed email.

Mail: Feature/Change Request 18766 [Open] SMTP error code is not available to user of smtp

alan at akbkhome dot com — 2011-08-29T11:23:35+00:00

Mail Feature/Change Request
Reported by alan_k
2011-08-29T11:23:35+00:00
PHP: 5.3.8 OS: all Package Version: SVN

Description:
------------
need to get the real smtp error code back from mail. however currently it's only feasible 
by parsing the error text.

Mail: Feature/Change Request 18573 [Open] MAIL FROM and From: can't be different?

danielh at crosslink dot net — 2017-04-11T17:17:56+00:00

Mail Feature/Change Request
Reported by danielh
2011-05-31T06:29:20+00:00
PHP: 5.3.6 OS: windows 8 Package Version: 1.2.0

Description:
------------
I am using PEAR with PHP to send email. I send it through my ISP's SMTP gateway. My ISP's SMTP gateway will only process outgoing email when the MAIL FROM message lists my email address (on this ISP).

IOW: if I specify an address, in the From: header, other than the one supported by my ISP I get (using debug):

DEBUG: Send: MAIL FROM:

DEBUG: Recv: 250 2.1.0 Ok
DEBUG: Send: RCPT TO:

DEBUG: Recv: 554 5.7.1 : Sender address rejected: Access denied
DEBUG: Send: RSET

The issue is that I would like to list a From: header that is different from this email address (that is NOT the same as the email address supported by my ISP). Usin a script, I have successfully done this: by specifying a MAIL FROM message to the SMTP server, and then by specifying the alternative email address in the From: header: the MAIL FROM is used by my ISP to authenticate, while the From: header is displayed in the recipients "from" field.

Unfortunately, pear email doesn't seem to permit this -- it uses the From: header to specify the MAIL FROM message.
And there doesn't seem to be any way to override this default behavior. I tried Reply-To, but that yields the access denied message (that is, it changes both the From: header and the MAIL FROM message.

Is this a "feature" of PEAR email?

Thanks.

Test script:
---------------
I can gin something up if need be.

Mail: Bug 17758 [Open] smtpmx driver not work for windows.

n-ishii at chiether dot net — 2017-04-11T17:20:18+00:00

Mail Bug
Reported by chiether
2010-08-20T06:10:52+00:00
PHP: Irrelevant OS: Windows Package Version: 1.2.0

Description:
------------
smtpmx cannot nameservers overwrite.
smtpmx failed by Windows because no have "resolv.conf".

we can retry with overwrite when after failed(instanced $resolver). but I think need "nameservers" on mail_option.

# maybe Net_DNS resolver can overwrite nameservers. see Net_DNS example code.

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

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

Mail Feature/Change Request
Reported by alex2000
2008-04-04T11: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 — 2010-03-08T16:21:52+00:00

Mail Feature/Change Request
Reported by derernst
2007-11-30T11: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-19T00:48:42+00:00

Mail Feature/Change Request
Reported by cwiedmann
2007-11-19T00: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 — 2011-01-17T15:58:37+00:00

Mail Feature/Change Request
Reported by scottprive@...
2006-09-29T22: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] =>
                                        )

                                )
...