horst

WireMailSmtp

Recommended Posts

@horst, @LostKobraki - thanks! Excellent module - tested/works perfectly.

Share this post


Link to post
Share on other sites

Hi.

I have moved my site to another VPS and now I get "Error in hnsmtp::send : cannot connect to smtp-server!".

Differences in VPS: php 5.4 -> 5.6 and http->https. Can it be the issue in my case or I must dig in other place?

p.s. I can connect to smtp server in console with

#openssl s_client -crlf -connect smtp.yandex.ru:465

so it is not a firewall I guess.

Share this post


Link to post
Share on other sites

I had a similar situation a couple of months ago when I tried to upgrade my domains to PHP 5.6.x on my web host.  I never resolved this issue and ended up reverting to PHP 5.5.x

Note:  The following is what I found out by using Goggle search.  It may apply or not apply to your situation, however I hope that maybe it will cause others to chime in on possible solutions

All encrypted client streams now enable peer verification by default. By default, this will use OpenSSL's default CA bundle to verify the peer certificate. In most cases, no changes will need to be made to communicate with servers with valid SSL certificates, as distributors generally configure OpenSSL to use known good CA bundles. - OpenSSL changes in PHP 5.6.x (PHP Manual)

It appears that in PHP 5.6.0 (at least the version in Debian jessie, with openssl 1.0.1h-3), this function is now validating SSL certificates (in a variety of ways). First, it appears to fail for untrusted certificates (i.e. no matching CA trusted locally), and secondly, it appears to fail for mismatched hostnames in the request and certificate.

"PHP 5.6 now verifies SSL certificates, the "fsockopen" function fails in the "ConnectToHost" method due to mismatched certificate CN (expects host name, but IP is given instead)." -Klemen (PHP 5.6 compatibility)

The problem is that this change is resulting in an error on Email Class SMTP protocol:

fsockopen(): SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

When you update to PHP 5.6+ the "CA Root" have to be set, or OpenSSL certificate verify don't work correctly.

Step One: Install CA_Root (In my case, on FreeBSD 10, via Ports)
/usr/ports/security/ca_root_nss

After install, the Pem Cert will be located at:
/usr/local/etc/ssl/cert.pem

Step Two: Add to php.ini the openssl.cafile

openssl.cafile = /usr/local/etc/ssl/cert.pem

Restart your HTTP Server, and verify with phpinfo()

References:     http://stackoverflow.com/questions/27622427/codeigniter-2x-email-class-smtp-ssl-verification-bug-on-php-5-6
                    http://www.phpclasses.org/discuss/package/14/thread/78/
                    http://php.net/manual/en/migration56.openssl.php
  • Like 1

Share this post


Link to post
Share on other sites

@cstevensjr thanks for your answer, it point me to the right direction.

The problem is in old version of smtp class: Certificate is issued to hostname, but smtp class sends IP. In the last version it was fixed and works fine for me now on php5.6.

@horst, update smtp class, please.

http://www.phpclasses.org/package/14-PHP-Sends-e-mail-messages-via-SMTP-protocol.html

  • Like 2

Share this post


Link to post
Share on other sites

Many thanks! I have updated the repo!

  • Like 2

Share this post


Link to post
Share on other sites

@horst - just in case you missed it: https://github.com/horst-n/WireMailSmtp/issues/3

I believe I have setup my Github the wrong way, I get notify messages for allmost everything, but not for issues of my own repos. I haven't seen it, but will look into it now.

Edited by horst
  • Like 1

Share this post


Link to post
Share on other sites

There seems to be something was changed with the newer smtp class that we have changed 2 weeks ago. But anyways, it seems to be fixed now.

@Pete, please can you have a look to it? I haven't changed anything on the behave of To-Recipients, only CC and BCC.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks horst - saw your updates on Github so will have a look tonight :)

Share this post


Link to post
Share on other sites

Just tested and with the latest change you made it works perfectly - thanks!

  • Like 1

Share this post


Link to post
Share on other sites

How can I get the sender Emailaddress set in the config of the module, from a template or module?

Thank you?

Share this post


Link to post
Share on other sites

That's it.

$data = wire('modules')->getModuleConfigData('WireMailSmtp');
echo $data['sender_email'];
echo $data['sender_name'];

Thank you

Share this post


Link to post
Share on other sites

I can't believe I've not thanked you Horst for this module. I've been using it for about a year, linked to Mandrill, a match made in heaven ^_^ and no false-positive spam rejected emails.

Thank you again, cheers, -Alan.

  • Like 1

Share this post


Link to post
Share on other sites

having some trouble with CC, i'm supplying an array, like this:

$mail->cc($array);

and i know my array is good, and CC works for 1 CC (I have $mail->sendSingle(true); )

but it will only CC the last member of the array, no matter which array type i input.

......

OK - forget this, i just updated to the latest version and this was fixed...

Share this post


Link to post
Share on other sites

First time using this module and I get this error:

"it is not supported any of the authentication mechanisms required by the server"

The SMTP server is an open relay restricted by sender IP, no authentication required.

I have tested using PHPMailer succesfully.

Any ideas?

Share this post


Link to post
Share on other sites

First time using this module and I get this error:

"it is not supported any of the authentication mechanisms required by the server"

The SMTP server is an open relay restricted by sender IP, no authentication required.

I have tested using PHPMailer succesfully.

Any ideas?

Can you please provide some information regarding your setup for this website (versions of PHP/ProcessWire, type of hosting used, the hosting provider/or whether local hosted)?  Have you followed the instructions from your hosting provider regarding SMTP setup details, if not locally hosted?

Share this post


Link to post
Share on other sites

Can you please provide some information regarding your setup for this website (versions of PHP/ProcessWire, type of hosting used, the hosting provider/or whether local hosted)?  Have you followed the instructions from your hosting provider regarding SMTP setup details, if not locally hosted?

It appears this code as part of smtp.php, generates a false positive in my case (no authentication required)

While the test fails, the module still sends mail correctly.

if($success
&& strlen($mechanism)==0)
{
   $this->error="it is not supported any of the authentication mechanisms required by the server";
   $success=0;
}

Commenting out $success will make the test pass, but probably not a good idea.

Nothing special about the hosting enviroment, as I said all email scripts, the normal wireMail() works, along with PHPMailer.

The issue is the SMTP server does not require authentication, which seems to be a requirement of the smtp.php as above, which in turn causes the test of the module to fail.

Share this post


Link to post
Share on other sites

The important thing is that the emails are processed and work.  I believe if wireMail() is working then this module is working (as it uses wireMail()). 

If you could open an issue on Github, the module creator/maintainer can have a look at the issue you are reporting.

  • Like 2

Share this post


Link to post
Share on other sites

+1 what cstevensjr said re Github.

Re the problem, it sounds like the module assumes some authentication will be required (not surprised that it assumes this, surprised there's SMTP services which don't require auth).

On a general note, this module providing as it does a way to send mail via Mandrill.com, has been a life saver for me. No more lost emails due to recipients email systems assuming an email from a tiny unknown host is spam (as Mandrill delivers millions of emails their reputation is superb and so emails invariably get to their destination w/o getting rejected).

  • Like 2

Share this post


Link to post
Share on other sites

Hey, you are all right. We have had another issue with authentication and the test, where the original SMTP-class also allowed the missing of authentication. In this regard, the user could successfully pass the test (connecting to the server, IP + Port) without providing authentication credentials.

Therefore I have hacked the original class with this code you have posted above. (assuming there will be no open relay servers out there in 2015) But yep, now you comes along here. :lol:

I will have a closer look to it and provide a better fix. (apropriate for both situations). In the meantime you can A) comment the part in the code, or B) don't use the test anymore on tis server.

Thanks for your help.

  • Like 1

Share this post


Link to post
Share on other sites

This has nothing to do with WireMailSmtp but I have a question:

Can't wrap my head around this... The module is not autoloading, only extending WireMail, but it loads on demand... I'm lost :-)

Share this post


Link to post
Share on other sites

Have a look into Functions.php line 805, function wireMail():

	$mail = null; 
	$modules = wire('modules'); 

	// attempt to locate an installed module that overrides WireMail
	foreach($modules as $module) {
		$parents = class_parents("$module"); 
		if(in_array('WireMail', $parents) && $modules->isInstalled("$module")) { 
			$mail = wire('modules')->get("$module"); 
			break;
		}
	}
	// if no module found, default to WireMail
	if(is_null($mail)) $mail = new WireMail(); 

:lol:

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported, and page values can't be directly accessed configuration settings are limited to the bare essentials (selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently) supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine for me in one particular project, but hasn't been tested that much, so please tread carefully – and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.4. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180528, v1.0.4 add custom select statement option 180516 change sql query method, bump version to 1.0.0 180515 multilang bugfix 180513 beta release <180513 preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By blynx
      Hej,
      A module which helps including Photoswipe and brings some modules for rendering gallery markup. Feedback highly appreciated
      (Also pull requests are appreciated 😉 - have a new Job now and don't work a lot with ProcessWire anymore, yet, feel free to contact me here or on GitHub, Im'm still "online"!)

      Modules directory: http://modules.processwire.com/modules/markup-processwire-photoswipe
      .zip download: https://github.com/blynx/MarkupProcesswirePhotoswipe/archive/master.zip
      You can add a photoswipe enabled thumbnail gallery / lightbox to your site like this. Just pass an image field to the renderGallery method:
      <?php $pwpswp = $modules->get('Pwpswp'); echo $pwpswp->renderGallery($page->nicePictures); Options are provided like so:
      <?php $galleryOptions = [ 'imageResizerOptions' => [ 'size' => '500x500' 'quality' => 70, 'upscaling' => false, 'cropping' => false ], 'loresResizerOptions' => [ 'size' => '500x500' 'quality' => 20, 'upscaling' => false, 'cropping' => false ], 'pswpOptions' => (object) [ 'shareEl' => false, 'indexIndicatorSep' => ' von ', 'closeOnScroll' => false ] ]; echo $pswp->renderGallery($page->images, $galleryOptions); More info about all that is in the readme: https://github.com/blynx/MarkupProcesswirePhotoswipe
      What do you think? Any ideas, bugs, critique, requests?
      cheers
      Steffen