Jump to content
Pierre-Luc

WireMail Mailgun

Recommended Posts

Hi Pierre-Luc

Does this Module with an unverified MailGun domain?

IE where a domain hasn't had any MailGun DNS changes and has simply been added to the MailGun Control panel as a domain?

I'm just testing it with PW 3 and am wondering why it's not working. I've identified and fixed a previous VPS issue.

Share this post


Link to post
Share on other sites

@Peter Knight are you seeing anything in the Mailgun logs in your PW admin panel?

Edit: If you can, could you post a pastebin of your /site/assets/logs/mailgun.txt. Either here or send me a PM.

Share this post


Link to post
Share on other sites

Hi Pierre-Luc,

First of all the module is working great for me at the moment. I haven't pushed it to hard yet but has done everything I've asked of it so far.

I have hit a small issue with mailgun and their complaint system and API. 

If people didn't know. If an email recipient accidentally(or on purpose) clicks the "junk" mail button it sends a complaint to Mailgun and they then block you from sending mail to that address, unless you clear/delete the complaint through the API.

As I'm somewhat new to web development, it's hard for me to understand how to even get started.

I was wondering if you or anyone had plans to add a way to administer the complaints from this module? or to check for complaints and delete any that are there before sending the email?

Cheers

  • Like 3

Share this post


Link to post
Share on other sites

@ Clarkey1891

Have you had any issues with MailGun's reports dashboard? I notice that although my mails are sending, the stats dashboard doesn't log this. Possibly it's because I'm using an unverified domain (no DNS records have been updated) but wondered if yours was working ?

Share this post


Link to post
Share on other sites

I was wondering if you or anyone had plans to add a way to administer the complaints from this module? or to check for complaints and delete any that are there before sending the email?

I'll have to look into Mailgun's webhooks API, and see if it's possible to get incoming notices from this.

Have you had any issues with MailGun's reports dashboard? I notice that although my mails are sending, the stats dashboard doesn't log this. Possibly it's because I'm using an unverified domain (no DNS records have been updated) but wondered if yours was working ?

The stats sometimes take some time to update, but never really long. If you really want to see what's going on, the Logs tab on Mailgun is much more efficient and is pretty much instant.

I would really recommend that you do set your SPF and DKIM, as there are a bunch of penalties on accounts who don't.. https://documentation.mailgun.com/quickstart-sending.html#verify-your-domain

  • Like 2

Share this post


Link to post
Share on other sites

@ Peter Knight

sorry Peter I'm not getting any issues with the reports but I've also completed the verification process on the domain.

@ Pierre-Luc

Thanks, anything would be a great help

Share this post


Link to post
Share on other sites

@Pierre-Luc

thanks for this module, everything seems to be working well and i greatly appreciate all the time you put into it; Mailgun is great, and i can see myself using it a lot in the future for transactional emails in processwire. :)

My only issues are probably more about adjusting from Mandrill to Mailgun, i do like the Mandrill interface in terms of seeing the outbound activity list, sender, status, subject, view content etc; it's a bit more user friendly; also, this may be how i have it configured but the from address on mailgun shows a "sent by " and then a long email address like person@mg.domain.com ; i know i'm going to get some complaints from clients if that is something that can't be changed, and they may just prefer paying the $10/month mailchimp minimum plan to carry on with Mandrill..

Share this post


Link to post
Share on other sites

@Pierre-Luc

thanks for this module, everything seems to be working well and i greatly appreciate all the time you put into it; Mailgun is great, and i can see myself using it a lot in the future for transactional emails in processwire. :)

My only issues are probably more about adjusting from Mandrill to Mailgun, i do like the Mandrill interface in terms of seeing the outbound activity list, sender, status, subject, view content etc; it's a bit more user friendly; also, this may be how i have it configured but the from address on mailgun shows a "sent by " and then a long email address like person@mg.domain.com ; i know i'm going to get some complaints from clients if that is something that can't be changed, and they may just prefer paying the $10/month mailchimp minimum plan to carry on with Mandrill..

My pleasure!

The sent by line usually shows when your DKIM / SPF isn't set, make sure you do.

Share this post


Link to post
Share on other sites

ok thanks - i followed their recommendation of the mg subdomain but i guess i need to now add all of the sending domains and dkim records for those domains, at least that's how it is with Mandrill...

Share this post


Link to post
Share on other sites

Well you don't really need to have specific email domains unless you expect to have incoming emails through Mailgun. If your main domain has MX records you can just have SPF and DKIM in your TXT entries.

You just need to make sure your outgoing email uses the same domain as the one which is set in your email's "from". When on gmail/gapps with a custom domain for example, it's good to test reception on another domain since Google doesn't like being sent email to an email address "owned" by its own servers but not originating from it and will usually display the originating server as a security measure. It won't generally show on addresses on other domains. The reason it is that way is to prevent address spoofing, since the way email is architected, you can send any email from any server using any email address and nobody would know. As you understand that could have pretty bad consequences in different scenarios, which is why Sender Policy Framework (SPF) and

DomainKeys Identified Mail (DKIM) exist. It might feel annoying and troublesome but in reality it's just good practice. Email is complicated. ;)

  • Like 2

Share this post


Link to post
Share on other sites

right i just checked and i do have all of the spf and dkim records correctly done but i think you are saying that i should not use the mg subdomain and change that to the normal domain so i don't get those sent by things..  i wonder if you can have both mailgun and mandrill txt records

Share this post


Link to post
Share on other sites

Yep, just change it to the normal domain and it'll show correctly as long as the From address is the same as the MG domain.

What I do worry about, and it is a lesser issue you only run into when switching between WireMail modules, is that they don't all have the same functions or parameters so it's just something to check when you switch. A simple bit of search and replace in your favourite editor and you're sorted though :)

Share this post


Link to post
Share on other sites

Yep, just change it to the normal domain and it'll show correctly as long as the From address is the same as the MG domain.

What I do worry about, and it is a lesser issue you only run into when switching between WireMail modules, is that they don't all have the same functions or parameters so it's just something to check when you switch. A simple bit of search and replace in your favourite editor and you're sorted though :)

sure enough, it works like you said! no more 'sent by'...!

good point though about wiremail - i currently use horst's wiremail module and am extensively using the functions for attachments and probably more;

i wonder if when i get to the stage of switching that site over to mailgun, if i'll need to use the SMTP connection option, instead of API..

Share this post


Link to post
Share on other sites

Hi Luc,

I am not sure if you can help me with this but I'll try anyway...I am using this module to send transaction email for my online store but I am not sure if I got this setup correctly. So my issue is: the email from mailgun is sent straight to spam and after looking into it, there is no mailed-by/sent-by (which I reckon is the issue it went to spam) in the email header. However when I tested it manually using the curl command (as per example here: https://documentation.mailgun.com/quickstart-sending.html#send-via-smtp) on the server (digital ocean) server, it went ok (not being sent to spam).

I also notice when using the curl command the IP address from which the email was sent is Mailgun's IP Address (refer to the details below) but when using this module the IP address is the IP address of the digital ocean ubuntu box. I am not sure which one it should be, but I reckon it should be the IP address of the box and not the mailgun API IP address?

I know this is probably not related to your module direcly but if you can help and potentially point me to the right direction, I really appreciate it. Thank you in advanced!

Mailgun Details

State: Active
IP Address: 209.61.151.224
SMTP Hostname: smtp.mailgun.org
API Base URL: https://api.mailgun.net/v3/v2.weareheim.co

Share this post


Link to post
Share on other sites

Hmm hard to say, but do you see any error message either on the module's log or on Mailgun itself?

What are your current options set to?

Also are your SPF and DKIM set?

Share this post


Link to post
Share on other sites

Hi Luc,

I know what the issue is but I dont know how to solve it and it probably has nothing to do with your module anyway. The issue is the module sends the email using the underlying MTA in my linux box in this case sendmail. Sendmail somehow use the box IP address instead of the IP address of the domain assigned in my mailgun account. I dont really understand how to force sendmail to use mailgun ip address and have been trying here and there but no luck whatsoever.

So, in the end I decided to install exim4 and use smtp settings which works ok. Maybe, I play around with it in the future to resolve this. If anyone here has unix experience with sendmail can point to the direction, really appreciate it. :D

Share this post


Link to post
Share on other sites

Hmmm....interesting,

So I don't need to install sendmail/exim/postfix etc? I tried that before but no luck....maybe I have a look again closely

Share this post


Link to post
Share on other sites

but I thought send() method of wireMail is looking for MTA? no?

are we using wireMail or WireMail? this is completely different question though

Share this post


Link to post
Share on other sites

Hi Luc,

I find out what the issue is, I installed your module alongside with WireMail for css inline etc. So, I uninstalled that module and this works like a charm! Thank you!

Cheers

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By nbcommunication
      I've spent the last while experimenting with srcset implementation - and PageimageSrcset is the result:
      PageimageSrcset
      Provides configurable srcset and sizes properties/methods for Pageimage.
      Overview
      The main purpose of this module is to make srcset implementation as simple as possible in your template code. It does not handle images rendered in CKEditor or similar fields.
      For an introduction to srcset and sizes, please read this Mozilla article about responsive images.
      Pageimage::srcset()
      // The property, which uses the set rules in the module configuration $srcset = $image->srcset; // A method call, using a set rules string // Delimiting with a newline (\n) would also work, but not as readable $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x"); // The same as above but using an indexed/sequential array $srcset = $image->srcset([ "320", "480", "640x480 768w", "1240", "2048 2x", ]); // The same as above but using an associative array // No rule checking is performed $srcset = $image->srcset([ "320w" => [320], "480w" => [480], "768w" => [640, 480], "1240w" => [1240], "2x" => [2048], ]); // Use the default set rules with portrait images generated for mobile/tablet devices $srcset = $image->srcset(true); // Return the srcset using all arguments $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x", [ "portrait" => "320, 640", ]); // The set rules above are a demonstration, not a recommendation! Image variations are only created for set rules which require a smaller image than the Pageimage itself. On large sites this may still result in a lot of images being generated. If you have limited storage, please use this module wisely.
      Portrait Mode
      In many situations, the ratio of the image does not need to change at different screen sizes. However, images that cover the entire viewport are an exception to this and are often the ones that benefit most from srcset implementation.
      The main problem with cover images is that they need to display landscape on desktop devices and portrait when this orientation is used on mobile and tablet devices.
      You can automatically generate portrait images by enabling portrait mode. It is recommended that you use this in combination with Pageimage::focus() so that the portrait variations retain the correct subject.
      The generated variations are HiDPI/Retina versions. Their height is determined by the portrait ratio (e.g. 9:16). Variations are always generated, regardless of whether the original image is smaller. Upscaling is disabled though, so you may find that some variations are actually smaller than they say they are in their filename.
      The sizes attribute should be used when portrait mode is enabled. Pageimage::sizes will return (orientation: portrait) and (max-width: {maxWidth}px) 50vw by default, which handles the use of these images for retina devices. The maximum width used in this rule is the largest set width.
      Pageimage::sizes()
      There is no option to configure default sizes because in most cases 100vw is all you need, and you do not need to output this anyway as it is inferred when using the srcset attribute. You can use the method for custom sizes though:
      // The property $sizes = $image->sizes; // Returns 100vw in most cases // Returns '(orientation: portrait) and (max-width: {maxWidth}px)50vw' if portrait mode enabled // A method call, using a mixture of integer widths and media query rules // Integer widths are treated as a min-width media query rule $sizes = $image->sizes([ 480 => 50, "(orientation: portrait) and (max-width: 640px)" => 100, 960 => 25, ]); // (min-width: 480px) 50vw, (orientation: portrait) and (max-width: 640px) 100vw, (min-width: 960px) 25vw // Determine widths by UIkit 'child-width' classes $sizes = $image->sizes([ "uk-child-width-1-2@s", "uk-child-width-1-3@l", ]); // (min-width: 640px) 50vw, (min-width: 1200px) 33.33vw // Determine widths by UIkit 'width' classes $sizes = $image->sizes([ "uk-width-1-2@m", "uk-width-1-3@xl", ]); // (min-width: 960px) 50vw, (min-width: 1600px) 33.33vw // Return the portrait size rule $sizes = $image->sizes(true); // (orientation: portrait) and (max-width: {maxWidth}px) 50vw // The arguments above are a demonstration, not a recommendation! Pageimage::render()
      This module extends the options available to this method with:
      srcset: When the module is installed, this will always be added, unless set to false. Any values in the formats described above can be passed. sizes: Only used if specified. Any values in the formats described above can be passed. uk-img: If passed, as either true or as a valid uk-img value, then this attribute will be added. The srcset attribute will also become data-srcset. Please refer to the API Reference for more information about this method.
      // Render an image using the default set rules echo $image->render(); // <img src='image.jpg' alt='' srcset='{default set rules}'> // Render an image using custom set rules echo $image->render(["srcset" => "480, 1240x640"]); // <img src='image.jpg' alt='' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w'> // Render an image using custom set rules and sizes // Also use the `markup` argument echo $image->render("<img class='image' src='{url}' alt='Image'>", [ "srcset" => "480, 1240", "sizes" => [1240 => 50], ]); // <img class='image' src='image.jpg' alt='Image' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 1240px) 50vw'> // Render an image using custom set rules and sizes // Enable uk-img echo $image->render([ "srcset" => "480, 1240", "sizes" => ["uk-child-width-1-2@m"], "uk-img" => true, ]); // <img src='image.jpg' alt='' data-uk-img data-srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 960px) 50vw'> // Render an image using portrait mode // Default rule sets used: 320, 640, 768, 1024, 1366, 1600 // Portrait widths used: 320, 640, 768 // Original image is 1000px wide // Not possible to use portrait mode and custom sets or portrait widths in render() // Sizes attribute automatically added echo $image->render(["srcset" => true]); // <img src='image.jpg' alt='' srcset='image.320x569-srcset-hidpi.jpg 320w, image.640x1138-srcset-hidpi.jpg 640w, image.768x1365-srcset-hidpi.jpg 768w, image.jpg 1024w' sizes='(orientation: portrait) and (max-width: 768px) 50vw'> Configuration
      To configure this module, go to Modules > Configure > PageimageSrcset.
      Set Rules
      These are the default set rules that will be used when none are specified, e.g. when calling the property: $image->srcset.
      Each set rule should be entered on a new line, in the format {width}x{height} {inherentwidth}w|{resolution}x.
      Not all arguments are required - you will probably find that specifying the width is sufficient for most cases. Here's a few examples of valid set rules and the sets they generate:
      Set Rule Set Generated Arguments Used 320 image.320x0-srcset.jpg 320w {width} 480x540 image.480x540-srcset.jpg 480w {width}x{height} 640x480 768w image.640x480-srcset.jpg 768w {width}x{height} {inherentwidth}w 2048 2x image.2048x0-srcset.jpg 2x {width} {resolution}x How you configure your rules is dependent on the needs of the site you are developing; there are no prescriptive rules that will meet the needs of most situations. This article gives a good overview of some of the things to consider.
      When you save your rules, a preview of the sets generated and an equivalent method call will be displayed to the right. Invalid rules will not be used, and you will be notified of this.
      Portrait Mode
      Set Widths
      A comma limited list of widths to create HiDPI/Retina portrait variations for.
      Crop Ratio
      The portrait ratio that should be used to crop the image. The default of 9:16 should be fine for most circumstances as this is the standard portrait ratio of most devices. However, you can specify something different if you want. If you add a landscape ratio, it will be switched to portrait when used.
      Any crops in the set rules ({width}x{height}) are ignored for portrait mode variations as this ratio is used instead.
      UIkit Widths
      If your website theme uses UIkit, you can pass an array of UIkit width classes to Pageimage::sizes to be converted to sizes. The values stored here are used to do this. If you have customised the breakpoints on your theme, you should also customise them here.
      Please note that only 1- widths are evaluated by Pageimage::sizes, e.g. uk-width-2-3 will not work.
      Remove Variations
      If checked, the image variations generated by this module are cleared on Submit. On large sites, this may take a while. It makes sense to run this after you have made changes to the set rules.
      Image Suffix
      You will see this field when Remove Variations is checked. The value is appended to the name of the images generated by this module and is used to identify variations. You should not encounter any issues with the default suffix, but if you find that it conflicts with any other functionality on your site, you can set a custom suffix instead.
      Debug Mode
      When this is enabled, a range of information is logged to pageimage-srcset.
      PageimageSrcsetDebug.js is also added to the <head> of your HTML pages. This will console.log a range of information about the images and nodes using srcset on your page after a window.onresize event is triggered. This can assist you in debugging your implementation.
      The browser will always use the highest resolution image it has loaded or has cached. You may need to disable browser caching to determine whether your set rules are working, and it makes sense to work from a small screen size and up. If you do it the other way, the browser is going to continue to use the higher resolution image it loaded first.
      UIkit Features
      This module implements some additional features that are tailored towards UIkit being used as the front-end theme framework, but this is not required to use the module.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. ProcessWire >= 3.0.123 is required to use this module.
×
×
  • Create New...