horst

WireMailSmtp

Recommended Posts

Oh, google only blocks Thunderbird, Outlook, 60% iOS apps and some more. Yes, of course, the only reason is security for users. ūüôĄ

@gebeer you may recherche on phpclasses.com, if the smtp class of Manuel Lemos has enhancement for this already. Im totaly behind my time schedules atm. Sorry. 

  • Like 1

Share this post


Link to post
Share on other sites
14 hours ago, gebeer said:

I am experiencing problems when sending through Gmail on a site that is sending out quite a lot of emails to different recipients.

For high mail volumes something like Mailgun is probably better. I've only used WireMail Mailgun in one project so far but it worked great.

  • Like 4

Share this post


Link to post
Share on other sites

I can also vouch for Mailgun. Its great, never had problem for the last 3 years I've been using it. Free tier is very generous too.

  • Like 1

Share this post


Link to post
Share on other sites

Thank you for your suggestions. It is not that many mails, maybe a total of 100 a day and max 10-30 per hour. So I will stay with Gmail for the time being.

Share this post


Link to post
Share on other sites
Just now, gebeer said:

Thank you for your suggestions. It is not that many mails, maybe a total of 100 a day and max 10-30 per hour. So I will stay with Gmail for the time being.

That's still a lot for Gmail.  Simply knowing about Gmail's Bulk Sending Guidelines should help you since you want to keep using them.

  • Like 3

Share this post


Link to post
Share on other sites

@horst Can you tell me how/where in the module this hijacks/extends wireMail()? I'm glad that it does, but I am desperate to understand how this works.

new WireMail();  // WireMail
new wireMail();  // WireMail
wireMail();      // WireMailSmtp
$mail->new();    // WireMailSmtp

This has highlighted one of the many parts of my PW knowledge that is majorly lacking.

 

 

Edit:
Ok. Finally get it. Here's how it works, for anybody else that wonders...

wire/core/boot.php loads JUST WireMailTools. WireMailTools::new() looks for any classes that overlay on WireMail. If WireMailSmtp is installed, it will be the class that is returned.

If none are found, it defaults to WireMail.

Shooooo-wee. Nice to know!

  • Like 2

Share this post


Link to post
Share on other sites

Is anyone using this module in combination with SendGrid? I had the module working til a few weeks ago and now I get a time out error that I can't connect to mail.sendgrid.net. Not sure what the exact settings need to be as Sendgrid isn't too clear on this as far as I can find.

Share this post


Link to post
Share on other sites

I've no experience with Sendgrid but just in case helpful, I used to use Mandril until they changed their pricing model from reasonable to insane (for small users), at that time I went with Postmark https://postmarkapp.com/ and have had a faultless experience with them for over year over multiple sites (I'm not on a commission ;))

  • Like 1

Share this post


Link to post
Share on other sites
12 minutes ago, alan said:

I've no experience with Sendgrid but just in case helpful, I used to use Mandril until they changed their pricing model from reasonable to insane (for small users), at that time I went with Postmark https://postmarkapp.com/ and have had a faultless experience with them for over year over multiple sites (I'm not on a commission ;))

Snap here on the PostMarkApp part. It may have been you who pointed me to them. :)

Do you verify all your individual domains via SPF and DKIM verified authentication?

P

Share this post


Link to post
Share on other sites

:) I am sure I have 'bigged' them up before here yes (it was so lovely meeting them after the bottom fell out of Mandrill when then went for DaftPricing‚ĄĘÔłŹ.

I would like to have individual SPF and DKIM records for each client. A few have asked about why emails though apparently from "noreply at Example Inc." are clearly actually from me@mycorps domain if they reply to one. I've told them all that to save them money the emails come from my DKIM'd and SPF'd email address, but I can do the same for them if they pay for my time setting it up. So far all have said "Oh.., that's why eh? Never mind, leave it as is".

One day I will go tell each of them they must get their records setup, but it's just one of those things that's on the ToDo that's not shouting to be done 'today' ;)

Share this post


Link to post
Share on other sites
5 minutes ago, alan said:

:) I am sure I have 'bigged' them up before here yes (it was so lovely meeting them after the bottom fell out of Mandrill when then went for DaftPricing‚ĄĘÔłŹ.

I would like to have individual SPF and DKIM records for each client. A few have asked about why emails though apparently from "noreply at Example Inc." are clearly actually from me@mycorps domain if they reply to one. I've told them all that to save them money the emails come from my DKIM'd and SPF'd email address, but I can do the same for them if they pay for my time setting it up. So far all have said "Oh.., that's why eh? Never mind, leave it as is".

One day I will go tell each of them they must get their records setup, but it's just one of those things that's on the ToDo that's not shouting to be done 'today' ;)

Good approach. Same here on the authentication etc.

I just verified a single domain - one of my own and send in all responses to clients as "webforms@edenstudios.com". They're pretty ok with that as they recognise them immediately.

 

Share this post


Link to post
Share on other sites

@horst, I'm not sure how you'd feed about this but do you mind if I fix labels, icons a bit and send PR for it?

I mean turning this:

image.png.925884525248ef16fe42206d20d37454.png

Into something like this:

image.png.8482c1877b163607241ad8c51ef2dd99.png

  • Like 1

Share this post


Link to post
Share on other sites

That's made me think - I could¬†set up a generic domain, like¬†Campaign Monitor use¬†createsend.com, and send all emails from that. May do that if I need the emails to be more anonymous for any reason ūüĎć

  • Like 1

Share this post


Link to post
Share on other sites
16 hours ago, abdus said:

@horst, I'm not sure how you'd feed about this but do you mind if I fix labels, icons a bit and send PR for it?

I mean turning this:

image.png.925884525248ef16fe42206d20d37454.png

Into something like this:

image.png.8482c1877b163607241ad8c51ef2dd99.png

Apreciated! Send me the PR. ūüėÄ

Share this post


Link to post
Share on other sites

Just realized that I forgot to increment the version, I appreciate if you could sort that out

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

I'm having an issue with the 'Test Settings' feature.

Some background: I have a contact form which sends an email (triggered by ajax), which seems to work a couple of times, but then starts throwing 500 errors on send.

At the same time, once the contact forms starts throwing 500 errors, clicking 'Test settings' in the module settings panel throws the same error:

image.png.b7976c2b25a5628657f69c976aa6fd66.png 

I'm not sure where to start finding the source of this issue - it seems that sometimes clearing compiled files solves the issue temporarily, but beyond this I'm not sure what to do.

We're running the latest Dev branch, but swapping to Master didn't prevent the issue.

Any advice on how to resolve this would be much appreciated!

Thanks,

Tom

Share this post


Link to post
Share on other sites

It sounds like an issue with FileCompiler; it's adding/failing to add namespace prefixes to where it shouldn't.

But, I don't see anything on line #678 that could be prefixed. What do you have there in compiled (site/assets/cache/FileCompiler/site/modules/WireMailSmtp) and noncompiled (site/modules/WireMailSmtp) versions?

image.thumb.png.cc8692e1166b325634291cd07d46a372.png

Share this post


Link to post
Share on other sites

Thanks for the swift reply!

Prior to trying to send a form, I see:

Function SendMail($to, $subject, $body, $headers, $return_path)

Then once I have tried to send a form, I see this:

Function \ProcessWire\sendmail($to, $subject, $body, $headers, $return_path)

The partial which handles the ajax request is like this:

<?php
namespace ProcessWire;

use Valitron\Validator;

function getInput($modules, $sanitizer, $input, $user) {
...
$v = new Validator([ ... ])
...
$formFields = [...]
return $formFields; // This contains the sanitized form fields content and the validation results
}

function sendMail($formFields, $modules, $pages, $sanitizer) {
...
if ($v->validate()) {
...
$mail = wireMail()
	->to($contactFormRecipient)
	->header('Reply-To', $email)
	->subject(ucwords($mailer_subject))
	->bodyHTML($messageHTML);
...
}
}
}

$formFields = getInput($modules, $sanitizer, $input, $user);
$output = sendMail($formFields, $modules, $pages, $sanitizer);
if ($output['sent']) {
	echo json_encode(array(...));
} else {
	echo json_encode(array(...));
}

Does the namespaced compiled function look right to you?

Share this post


Link to post
Share on other sites

Great, thank you for confirming.

Is there anything I can do in the meantime to get around this? 

 

I'm on the 3.0.79 dev branch

Share this post


Link to post
Share on other sites

Hmm, on second look, I don't have your issue, it works fine in my setup. Compiled file doesn't have the namespace prefix.

image.thumb.png.60b9a0a45c76415e9a3e3cd00173a8f8.png

You problem might be caused by something else.

Share this post


Link to post
Share on other sites

Could it be to do with the fact I've named the function in my template sendMail? It only just occurred to me that it's the same as the function used by wireMail.

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 dreerr
      TemplateEnginePug (formally TemplateEngineJade)
       
      This module adds Pug templates to the TemplateEngineFactory. It uses https://github.com/pug-php/pug to render templates.
      doctype html html(lang='en') head meta(http-equiv='content-type', content='text/html; charset=utf-8') title= $page->title link(rel='stylesheet', type='text/css', href=$config->urls->templates . 'styles/main.css') body include header.pug h1= $page->title if $page->editable() p: a(href=$page->editURL) Edit Project on GitHub: github.com/dreerr/TemplateEnginePug
      Project in modules directory: modules.processwire.com/modules/template-engine-pug/
       
      For common problems/features/questions about the Factory, use the TemplateEngineFactory thread.
       
    • By tpr
      ProcessNetteTester
      Run Nette Tester tests within ProcessWire admin.
      (continued from here)

      Features
      AJAX interface for running Nette Tester tests, in bulk or manually display counter, error message and execution time in a table run all tests at once or launch single tests show formatted test error messages and report PHP syntax errors stop on first failed test (optional) hide passed tests (optional) display failed/total instead passed/total (optional) re-run failed tests only (optional) auto scroll (optional) include or exclude tests based on query parameters start/stop all tests with the spacebar reset one test or all tests (ctrl+click) https://modules.processwire.com/modules/process-nette-tester/
      https://github.com/rolandtoth/ProcessNetteTester
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue ūüėȬ†
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I¬†offer paid support for 60‚ā¨ per hour.
       
      Changelog
      180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By tpr
      Update 2018-07-09: ProcessNetteTester module is available in the Modules Directory and on GitHub.

      This is a short tutorial on how to use Nette Tester with ProcessWire.
      As you will see it's very easy to setup and use and it's perfect for testing your code's functionality. With bootstrapping ProcessWire it's also possible to check the rendered markup of pages using the API, checking page properties, etc. It's also a great tool for module developers for writing better code. 
      While there will be nothing extraordinary here that you couldn't find in Tester's docs this can serve as a good starting point.
      Prerequisites: PHP 5.6+
      01 Download Tester
      Go to https://github.com/nette/tester/releases and download the latest release (currently 2.0.2). Download from the link reading "Source code (zip)". You can use composer also if you wish.
      02 Extract Tester files
      Create a new directory in your site root called "tester". Extract the zip downloaded here, so it should look like this:
      /site /tester/src /tester/tools /tester/appveyor.yml /tester/composer.json /tester/contributing.md /tester/license.md /tester/readme.md /wire ... 03 Create directory for test files
      Add a new directory in "/tester" called "tests". Tester recognizes "*.Test.php" and "*.phpt" files in the tests directory, recursively. 
      04 Create your first test
      In the "tests" directory create a new "MyTest.php" file.
      The first test is a very simple one that bootstraps ProcessWire and checks if the Home page name is "Home". This is not the smartest test but will show you the basics.
      Add this to "/tester/tests/MyTest.php":
      <?php namespace ProcessWire; use \Tester\Assert; use \Tester\DomQuery; use \Tester\TestCase; use \Tester\Environment; require __DIR__ . '/../src/bootstrap.php'; // load Tester require __DIR__ . '/../../index.php'; // bootstrap ProcessWire Environment::setup(); class MyTest extends TestCase {     // first test (step 04)     public function testHomeTitle()     {         $expected = 'Home'; // we expect the page title to be "Home"         $actual = wire('pages')->get(1)->title; // check what's the actual title Assert::equal($expected, $actual); // check whether they are equal     }     // second test will go here (step 06)     // third test will go here (step 07) } // run testing methods (new MyTest())->run(); I've added comment placeholders for the second and third tests that we will insert later.
      05 Run Tester
      Tester can be run either from the command line or from the browser. The command line output is more verbose and colored while in the browser it's plain text only (see later).
      Running from the command line
      Navigate to the "/tester" directory in your console and execute this:
      php src/tester.php -C tests This will start "/tester/src/tester.php" and runs test files from the "/tester/tests" directory. The "-C" switch tells Tester to use the system-wide php ini file, that is required here because when bootstrapping ProcessWire you may run into errors (no php.ini file is used by default). You may load another ini file with the "-c <path>" (check the docs).
      If the title of your Home page is "Home" you should see this:

      If it's for example "Cats and Dogs", you should see this:

      Running from the browser
      First we need to create a new PHP file in ProcessWire's root, let's call it "testrunner.php". This is because ProcessWire doesn't allow to run PHP files from its "site" directory.
      The following code runs two test classes and produces a legible output. IRL you should probably iterate through directories to get test files (eg. with glob()), and of course it's better not allow tests go out to production.
      <?php ini_set('html_errors', false); header('Content-type: text/plain'); echo 'Starting tests.' . PHP_EOL; echo '--------------------------' . PHP_EOL; $file = __DIR__ . '/PATH_TO/FirstTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; $file = __DIR__ . '/PATH_TO/SecondTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; echo '--------------------------' . PHP_EOL; echo 'Tests finished.'; exit; Navigate to "DOMAIN/testrunner.php" in your browser to execute the file. If every test succeeds you should get this:

      If there are failed tests the execution stops and you can read the error message. If there were more tests (eg. ThirdTest), those won't be displayed under the failed test.

      06 DOM test
      This test will check if a page with "basic-page" template has a "h1" element. We will create the page on the fly with ProcessWire's API. To keep things simple we will add the new test as a new method to our MyTest class.
      Add this block to the MyTest class:
      public function testBasicPageHeadline() {     $p = new Page();     $p->template = 'basic-page';     $html = $p->render();     $dom = DomQuery::fromHtml($html);     Assert::true($dom->has('h1')); } This will most likely be true but of course you can check for something more specific, for example "div#main". Note that we have used the DomQuery helper here (check the "use" statement on the top of the file).
      07 Custom function test
      You will probably want to make sure your custom functions/methods will work as they should so let's write a test that demonstrates this.
      I don't want to complicate things so I'll check if the built-in "pageName" sanitizer works as expected. Add this to the myTest class:
      public function testPageNameSanitizer() {     $expected = 'hello-world';     $actual = wire('sanitizer')->pageName('Hello world!', true);     Assert::equal($expected, $actual); } This should also be true. Try to change the expected value if you are eager to see a failure message.
       
      08 Next steps
      You can add more methods to the MyTest class or create new files in the "tests" directory. Check out the range of available Assertions and other features in the docs and see how they could help you writing more fail-safe code.
      Once you make a habit of writing tests you'll see how it can assist making your code more bulletproof and stable. Remember: test early, test often ūüôā
      If you find out something useful or cool with Tester make sure to share.
    • By bernhard
      @Sergio¬†asked about the pdf creation process in the showcase thread about my 360¬į feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread: