Jump to content
Pierre-Luc

WireMail Mailgun

Recommended Posts

Started to use this module and works fine so far, thanks!

Is there a way to use the built-in WireMail in certain cases? Eg. I need to use MailGun only for newsletter emails.

Share this post


Link to post
Share on other sites

Just found that I have to comment out this line to make tags work:

$tag = transliterator_transliterate('Any-Latin; Latin-ASCII; [\u0080-\u7fff] remove', $tag);

Could it be the server environment or maybe something else?

Share this post


Link to post
Share on other sites

this may be a question i'd need to submit as a support ticket to mailgun, as their documentations is pretty sparse, but is it even possible to switch out the sending domain when you send a message, because my CRM app has a selectable "From" address when sending an email and that can be from one of 8 different domains. Since the mailgun api has you put in the api key for a particular domain, will it reject the email if it has a different from domain, or will it auto-detect the domain and switch to that; the difference here between this and Mandrill for example is that Mandrill doesn't require different smtp credentials for each domain...

EDIT: so i reviewed the Mailgun documentation and it does seem that you need to authenticate for the domain you are sending from; so now i wonder if i could just change my script to read the domain from the sender and then set the domain and api key for that message;

$WireMailMailgun->setApiKey( string $apiKey )

$WireMailMailgun->setDomainName( string $domainName ) :cool:

Share this post


Link to post
Share on other sites

Started to use this module and works fine so far, thanks!

Is there a way to use the built-in WireMail in certain cases? Eg. I need to use MailGun only for newsletter emails.

Hmm, I'm not sure to be honest! I think once you instantiate the WireMail class it will automatically call the installed module. Maybe Ryan has an idea on this.. 

Share this post


Link to post
Share on other sites

Just found that I have to comment out this line to make tags work:

$tag = transliterator_transliterate('Any-Latin; Latin-ASCII; [\u0080-\u7fff] remove', $tag);

Could it be the server environment or maybe something else?

If you run this :

echo transliterator_transliterate('Any-Latin; Latin-ASCII; [\u0080-\u7fff] remove', "YOUR TAG HERE");

in PHP in interactive mode on your host, (php -a .. then type in commands), what's the output, and what was the exact input for "your tag here".

Also do your setup satisfy both requirements >> PHP >= 5.4.0, PECL int >= 2.0.0? It's weird that it would give out an error since it succeeds checking the function exists. Also anything comes up in Logs > Mailgun ?

Share this post


Link to post
Share on other sites

EDIT: so i reviewed the Mailgun documentation and it does seem that you need to authenticate for the domain you are sending from; so now i wonder if i could just change my script to read the domain from the sender and then set the domain and api key for that message;

$WireMailMailgun->setApiKey( string $apiKey )

$WireMailMailgun->setDomainName( string $domainName ) :cool:

Bingo! :)

Share this post


Link to post
Share on other sites

These are my findings - seems that intl is the culprit:

php 7.05
intl 1.1.0

PHP Warning: transliterator_transliterate(): Could not create transliterator with ID "Any-Latin; Latin-ASCII; [\u0080-\u7fff] remove" (transliterator_create: unable to open ICU transliterator with id "Any-Latin; Latin-ASCII; [\u0080-\u7fff] remove": U_INVALID_ID)

There are no related lines in mailgun log txt file.

My tags were simple words like "newsletter" or "test".

Share this post


Link to post
Share on other sites

@tpr, what OS? I have the same intl version on my test box. It seems your build might be linking the wrong ICU (outdated) package.

I just added a check in the module to test if the transliterator ID was valid on a given system. https://github.com/plauclair/WireMailMailgun/releases/tag/0.4.2

Note that I am not able to replicate your environment or the issue, so please let if know if this release corrects the issue on your end.

  • Like 1

Share this post


Link to post
Share on other sites

it's CentOS 6.6 I don't have direct access to it, only through Plesk.

After the update the tags appear in the MailGun logs, thanks!

  • Like 1

Share this post


Link to post
Share on other sites

Post removed because I fixed it and wasn't a mailgun problem.

Share this post


Link to post
Share on other sites

This is the first time I've used WireMail and WireMail Mailgun and I'm having a problem where mail is showing as delivered in the Mailgun logs but nothing appears in my inbox, or in spam folder. Solved: see edit below

If someone can confirm I've followed the installation and setup correctly...

1. Open account at Mailgun, choosing domain mg.mydomain.com

2. Set up TXT, CNAME and MX records for mg.mydomain.com at domain registrar, according the values provided by Mailgun. Mailgun verifies these records are set correctly.

3. Installed WireMail Mailgun module

4. Configured WireMail Mailgun module, filling out all fields. Unchecked "Disable cURL SSL Check". Default Sender Email Address: no-reply@mg.mydomain.com (does this need to be an address where there is an actual mailbox to receive replies?)

5. Tried to send test message by putting the following in a template file and viewing from frontend:

$mail = wireMail();
$mail->to('myaddress@gmail.com')->from('no-reply@mg.mydomain.com');
$mail->subject('Testing Mailgun');
$mail->body( 'Just testing.' );
$mail->send();

In the Mailgun dashboard I can see entries in the log for mg.mydomain.com like

Test delivered: no-reply@mg.mydomain.com → myaddress@gmail.com 'Testing Mailgun'

But no mail arrives to me. Mailgun does not show any bounces or errors.

The label "Test delivered" makes me wonder - is Mailgun in some sort of test mode? I'm not using the sandbox feature.

Looked for entries in /site/assets/logs/mailgun.txt but no such log exists. Is that normal?

Any help much appreciated.

Edit: I obviously should have looked more closely at the module config. Maybe this should be unchecked by default? Yeah, excuses, excuses... :)

post-2897-0-47316100-1462498905_thumb.pn

Share this post


Link to post
Share on other sites

I am not certain, however I noticed that you are including Gmail in your test.  This is a note from the Mailgun User Manual that may apply to your situation.

 Why am I not receiving an email when sending via the route with the sending address as a destination?

You’re most likely using GMail for sending your message. From GMail’s documentation (https://support.google.com/mail/troubleshooter/2935079?rd=1):

Finally, if you’re sending mail to a mailing list that you subscribe to, those messages will only appear in ‘Sent Mail.’ This behavior also occurs when sending to an email address that automatically forwards mail back to your Gmail address. To test forwarding addresses or mailing lists, use a different email address to send your message.

When a message from, say, bob@gmail.com goes through a route:

test@mailgun-domain.com -> bob@gmail.com

When this message arrives to GMail, it will have bob@gmail.com as both sender and recipient, therefore GMail will not show it.

In other words GMail does not show you messages you sent to yourself.

The other possibility is that the address had previously experienced a Hard Bounce and is on the ‘do not send’ list. Check the Bounces tab for a list of these addresses and remove the address in question if it is there.

 

Source:  https://documentation.mailgun.com/faqs.html#why-am-i-not-receiving-an-email-when-sending-via-the-route-with-the-sending-address-as-a-destination

Gmail doesn't like sending anything to the same Gmail address.  You may want to try sending your test using another provider.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, all solved now as per the edit to my post. Just needed to uncheck "Enable Test Mode" in the module config.

  • Like 1

Share this post


Link to post
Share on other sites

I'm working on converting a site from WireMailSMTP + Mandrill to using Mailgun.
In case anyone else needs to do this i'm posting the steps and snafus here. So far in adapting the existing code, the differences i have logged so far are;

1.)

 

in WireMailSMTP you have to set sendSingle(true) if you want the messages to each be sent individually, but this is the default for WireMailMailgun, so that call gets removed.

2.)
the method for adding attachments differs:

this:
$mail->attachment(string $filepath);

becomes this:
$mail->addAttachment(string $filepath);

3.)
If your site sends from different domains, then you need to switch that setting before send.
It appears to me that the API key is the same for all my domains, so I should only need to change the one setting when i send the email assuming i have already entered the API key in the WireMailMailgun module settings, then i can extract the domain of sending email address and set the domain to that (and also assuming I have all of those domains configured in Mailgun).

$domain = substr(strrchr($identity->email, "@"), 1);
$mail->setDomainName($domain);

*** This doesn't actually work because the runtime setting is not overriding the domain that is set in the ___send() options. ***

I made modifications to the module and now i have this working with my system; would probably need another setting like "match "sending domain" to "from email" domain" or something and also make the domain field optional in the module settings..

https://github.com/plauclair/WireMailMailgun/issues/7

------------------------------------------------------------------------------------------------------------

Additional comments and observations:

- would also be nice if an attachment() method could simply be added which aliases the other method (would save some code checks)

 

  • Like 1

Share this post


Link to post
Share on other sites

No. 1 is a violation of the WireMail interface, which says send() should return an integer and not a boolean. This should rather be changed in the module than in user-code. 

  • Like 1

Share this post


Link to post
Share on other sites

you mean so around line 132 changing like this:

switch ($info['http_code']) {
	case 200:
	//return true; // Can't set int for number sent, since Mailgun doesn't return that data
	return 1; // this instead ?
	break;
...

 

Share this post


Link to post
Share on other sites

At least. Better would still be to possibly return the actual number of sent emails. 

Share this post


Link to post
Share on other sites
4 minutes ago, LostKobrakai said:

At least. Better would still be to possibly return the actual number of sent emails. 

I agree but Mailgun doesn't return that info. I felt like returning true might be better since at least it's not giving you fake info. Further faking it might include counting the number of addresses in the emails array, but that feels even worse to me. 

For the other methods, I'd be more than happy if the interface was updated so we could standardize on things like attachments.

Share this post


Link to post
Share on other sites

I'd like to see that, too, especially as it's probably only left out because it wasn't part of the pw native implementation. Maybe we could just have a WireMailAttachments interface for that?!

  • Like 1

Share this post


Link to post
Share on other sites

You could do

```

return count($this->getToRecipients()) + count($this->getCCRecipients()) + count($this->getBCCRecipients());

```

Share this post


Link to post
Share on other sites

Well there's quite a few things lacking if you ask me, CC, BCC, attachments, batch mode on/off. I don't know if these are mail() constraints, I never use that thing. Basic things in email protocols are left out I believe because you could hack things up with the headers method, but that's far from an obvious thing especially for beginners. I don't have much preference on adding to the WireMail class, or having a supplemental interface to implement, or else. 

Personally I believe the interface specification for send should not be an int, but a true-ish or a false-ish value. Many ways of sending mail don't return numbers sent, but will tell you if it went ok or not. By the very nature of email, it could take hours/days until an email is certified as being accepted by the receiving servers, and some email servers don't even return accept/decline messages.

true/1…n should be correct return values for success, false/0 should also be correct for failure. It's just a matter of documenting it and using == instead of ===.  It's all fun insisting on integers but if we can't realistically meet those requirements it's just for show..

  • Like 2

Share this post


Link to post
Share on other sites

So after some hours of testing/research/code experiments, that yielded the modifications I made to the module as noted on GitHub, i can now send messages with the ability to switch between the sending domain and it all works. (also see edited post above).

Goodbye Mandrill! :P

  • Like 2

Share this post


Link to post
Share on other sites
On 6/25/2016 at 8:13 AM, Pierre-Luc said:

I agree but Mailgun doesn't return that info.

@Pierre-Luc is there still no way to get feedback on success/errors when sending through the Mailgun API?

I would like to build a Lister(Pro) Action around your module and for that I would like to show results after sending. Something like $mail->getResult(); in WireMailSMTP.

EDIT: Guess I would need to use Mailgun Events for tracking emails. Right?

  • 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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...