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

As long as you have space left in your records you should be able to have any number of SPF records on a domain.

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

The module will never use the MTA, it's pure cURL. Sounds like you have another email module enabled at the same time.

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

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 MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • 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-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 ----
       
×
×
  • Create New...