Jump to content
horst

WireMailSmtp

Recommended Posts

Hi guys and girls! And thanks for Processwire!

Just to give some help with Google account settings for WireMailSMTP. They are pretty well known... but Google appears to reject SMTP authentication from "non-trusted apps". There's however a solution which doesn't make Processwire "more secure" (from Google point of view) but unlocks the possibility of sending mails by WireMailSMTP using a Google account.

  1.  You need to enable 2-factor authentication for Gmail account which You want to use with WireMailSMTP.
  2. You need to generate an "app password" different from Gmail account password.
  3. This "app password" should be used as SMTP password while setting WireMailSMTP up.
  4. Bingo! No more blocking.

P.S. In my case, that Google blocking was occuring even if i tried to send a single letter per day. I'm not sending spam, just notifications for website owner/manager.

  • Like 2

Share this post


Link to post
Share on other sites

Hi there!

Got a strange WireMailSMTP behaviour. I'm sending emails via Gmail which works fine except one problem. Gmail browser client shows that emails like this:

xxxxxxxxx@gmail.com
	
16:56 (23 минуты назад)
	
кому: я
X-Mailer: ProcessWire/WireMailSmtp
Date: Tue, 24 Sep 2019 13:56:49 GMT
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="99e7bb5336c619adedcc743d03b1ec46"
Message-ID: <20190924165649.0537.xxxxxxxxx@gmail.com>

--99e7bb5336c619adedcc743d03b1ec46
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=D0=9F=D0=BE=D1=81=D1=82=D1=83=D0=BF=D0=B8=D0=BB =D0=BD=D0=BE=D0=B2=D1=
=8B=D0=B9 =D0=B7=D0=B0=D0=BA=D0=B0=D0=B7 .
--99e7bb5336c619adedcc743d03b1ec46
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=D0=9F=D0=BE=D1=81=D1=82=D1=83=D0=BF=D0=B8=D0=BB =D0=BD=D0=BE=D0=B2=D1=
=8B=D0=B9 =D0=B7=D0=B0=D0=BA=D0=B0=D0=B7.

It's obviously the quoted-printable decoding problem. Google also allows to download any message as .eml file, and here's a sample of what is inside such a file:

X-Mailer: ProcessWire/WireMailSmtp
Date: Tue, 24 Sep 2019 13:56:49 GMT
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="99e7bb5336c619adedcc743d03b1ec46"
Message-ID: <20190924165649.0537.xxxxxxxx@gmail.com>

--99e7bb5336c619adedcc743d03b1ec46
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=D0=9F=D0=BE=D1=81=D1=82=D1=83=D0=BF=D0=B8=D0=BB =D0=BD=D0=BE=D0=B2=D1=
=8B=D0=B9 =D0=B7=D0=B0=D0=BA=D0=B0=D0=B7 .
--99e7bb5336c619adedcc743d03b1ec46
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=D0=9F=D0=BE=D1=81=D1=82=D1=83=D0=BF=D0=B8=D0=BB =D0=BD=D0=BE=D0=B2=D1=
=8B=D0=B9 =D0=B7=D0=B0=D0=BA=D0=B0=D0=B7.

Both samples are parts of the same letter with some editing applied (real address changed, some inline css skipped etc.).

Is there a way to make Gmail decode such letters in a correct way? Thanks in advance!

Share this post


Link to post
Share on other sites

I'm trying desperately to configure SendInBlue with this module, but I'm getting the same error: "SMTP settings did not work". Can I get more information on what does not work?

 

Xnip2019-10-27_14-43-24.jpg

Xnip2019-10-27_14-49-42.jpg

Share this post


Link to post
Share on other sites

@Chris B - I also wonder if you'd be better off creating a module that works with SendInBlue's API rather than using SMTP. I would use WireMailGun as a starting point.

  • Like 2

Share this post


Link to post
Share on other sites

@dragan Thank you for your answer ! I'm waiting the return of SendInBlue. I asked if on their side everything works with these parameters. I will keep you informed.

@Adrian I would like it a lot! For the moment I am not yet advanced enough in Processwire to make this. But I will come ... and so I could contribute to the modules too 🙂 

  • Like 1

Share this post


Link to post
Share on other sites
18 hours ago, Chris B said:

Can I get more information on what does not work?

You can add some debug code into a template file and call a page with it:

    $to = array('me@example.com');
    $subject = 'Wiremail-SMTP Test ' . date('H:i:s') . ' äöü ÄÖÜ ß';

    $mail = wireMail();
    if($mail->className != 'WireMailSmtp') {
        echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>";

    } else {

        $mail->from = '--INSERT YOUR SENDER ADDRESS HERE --'; // <--- !!!!

        $mail->to($to);
        $mail->subject($subject);
        $mail->sendSingle(true);

        $mail->body("Titel\n\ntext text TEXT text text\n");
        $mail->bodyHTML("<h1>Titel</h1><p>text text <strong>TEXT</strong> text text</p>");

        $dump = $mail->debugSend(1);
    }

So, in short, instead of using $mail->send(), use $mail->debugSend(1) to get output on a frontend testpage.

The output is PRE formatted and contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection, like this one:

Spoiler

Resolving SMTP server domain "XXXXXXXXXXXXXXXXXXXX"...

Connecting to SMTP server "XXXXXXXXXXXXXXXXXXXX" port 587...

Connected to SMTP server "XXXXXXXXXXXXXXXXXXXX".

S 220 XXXXXXXXXXXXXXXXXXXX ESMTP

C EHLO wiremailsmtp.kawobi.local

S 250-XXXXXXXXXXXXXXXXXXXX

S 250-PIPELINING

S 250-SIZE 102400000

S 250-VRFY

S 250-ETRN

S 250-STARTTLS

S 250-AUTH PLAIN LOGIN

S 250-AUTH=PLAIN LOGIN

S 250-ENHANCEDSTATUSCODES

S 250-8BITMIME

S 250 DSN

C STARTTLS

S 220 2.0.0 Ready to start TLS

Starting TLS cryptographic protocol

TLS started: STREAM_CRYPTO_METHOD_TLSv1_2_CLIENT

C EHLO wiremailsmtp.kawobi.local

S 250-XXXXXXXXXXXXXXXXXXXX

S 250-PIPELINING

S 250-SIZE 102400000

S 250-VRFY

S 250-ETRN

S 250-AUTH PLAIN LOGIN

S 250-AUTH=PLAIN LOGIN

S 250-ENHANCEDSTATUSCODES

S 250-8BITMIME

S 250 DSN

C AUTH PLAIN XXXXXXXXXXXXXXXXXXXX

S 235 2.7.0 Authentication successful

C MAIL FROM:<XXXXXXXXXXXXXXXXXXXX>

C RCPT TO:<XXXXXXXXXXXXXXXXXXXX>

C DATA

S 250 2.1.0 Ok

S 250 2.1.5 Ok

S 354 End data with <CR><LF>.<CR><LF>

C To:  <XXXXXXXXXXXXXXXXXXXX>


Subject: Wiremail-SMTP Test 08:41:31 =?UTF-8?q?=C3=A4=C3=B6=C3=BC_=C3=84=C3=96=C3=9C_=C3=9F?=


From: LocalTestmail <XXXXXXXXXXXXXXXXXXXX>


Return-Path: XXXXXXXXXXXXXXXXXXXX


Reply-To:  <XXXXXXXXXXXXXXXXXXXX>


X-Mailer: ProcessWire/WireMailSmtp


Date: Mon, 28 Oct 2019 07:41:32 GMT


MIME-Version: 1.0


Content-Type: multipart/alternative; boundary="dbbe5bbf21a410f0b110683a0afec17a"


Message-ID: <20191028084132.3800.XXXXXXXXXXXXXXXXXXXX>







C --dbbe5bbf21a410f0b110683a0afec17a


Content-Type: text/plain; charset=UTF-8


Content-Transfer-Encoding: quoted-printable





Titel=0A=0Atext text TEXT text text=0A


--dbbe5bbf21a410f0b110683a0afec17a


Content-Type: text/html; charset=UTF-8


Content-Transfer-Encoding: quoted-printable





<h1>Titel</h1><p>text text <strong>TEXT</strong> text text</p>


--dbbe5bbf21a410f0b110683a0afec17a--




C 


.

S 250 2.0.0 Ok: queued as XXXXXXXXXXXX

C QUIT

S 221 2.0.0 Bye

Disconnected.

 

 

  • Like 6

Share this post


Link to post
Share on other sites

Thank you @horst! I will test that. Why does not the module propose this directly in the "test" part?

  • Like 1

Share this post


Link to post
Share on other sites
2 minutes ago, Chris B said:

Why does not the module propose this directly in the "test" part?

Because the current test part only does the connection part, (ping the server and login), within the modules settings screen. It was written for PW 2.4 (and is backward compatible until now). I think this would be a good addition, maybe besides the current connection test.

  • Like 3

Share this post


Link to post
Share on other sites

Hello everybody,

I contacted the SendInblue technical department. Nobody can tell me why it does not work. So I chose to go through the API which makes it easier for me to send SMS and manage Hooks.

Thank you for your help 🙂

  • Like 1

Share this post


Link to post
Share on other sites
On 10/28/2019 at 8:49 AM, horst said:

You can add some debug code into a template file and call a page with it

This is GOLD!

Share this post


Link to post
Share on other sites
On 10/28/2019 at 12:49 AM, horst said:

You can add some debug code into a template file and call a page with it:

That debug code also works perfectly in the Tracy console 🙂

image.thumb.png.28d3fc9e8ce6365a28d36f9df5747d81.png

  • Like 1

Share this post


Link to post
Share on other sites

Hey everyone.

I've build a site with a couple of form/email functions using WireMailSmtp.

Everything worked fine in my localhost server during dev, but now when the site is online no emails are being send, and i'm getting no errors (not with TraceyDebug or the debugsend(1) method, nor the connection test in the config module).. just no email are being send. 

only thing i can maybe suspect is the problem, is that the live site is secure using https and webserver refuses login with SSL (!?? i honestly don't know if that makes sense, i'm a bit of noob when it comes to SMTP ), but disabling https doesn't fix it. And then also, i don't get exactly what the "Local Hostname" in the configuration should be!?

If anyone has any idea of what might be the problem I would be super grateful. I've scoured this thread for any relevant solutions, but so far still no emails 😞

Share this post


Link to post
Share on other sites
55 minutes ago, Jonathan Sachse Mikkelsen said:

 

If anyone has any idea of what might be the problem I would be super grateful. I've scoured this thread for any relevant solutions, but so far still no emails 😞

Are you using an SMTP service to send emails through? IE PostmarkApp, MailGun, SendinGrid etc

Share this post


Link to post
Share on other sites
2 hours ago, Jonathan Sachse Mikkelsen said:

i'm getting no errors (not with TraceyDebug or the debugsend(1) method, nor the connection test in the config module).

What is the debuglog saying which server is connected, what is the servers response, what is the transfer protocol etc etc. 

the debug log from the debugsend() method should tell what happened. 

Share this post


Link to post
Share on other sites
On 11/11/2019 at 4:24 PM, horst said:

What is the debuglog saying which server is connected, what is the servers response, what is the transfer protocol etc etc. 

the debug log from the debugsend() method should tell what happened. 

Hi Horst i attached the debug log. to me it looks like it successfully connected to the smtp server drafted the email and send it... but i guess i'm missing something, so if you feel like having a look i would be very happy 🙂 

wiremailDebug.txt

Share this post


Link to post
Share on other sites
4 minutes ago, Jonathan Sachse Mikkelsen said:

I'm using the clients webmail server from their webhost service. 

Unfortunately this is probably a path to disaster these days - spam has made email painful and I think the only reliable option these days is to go with a transactional email service like MailGun, Postmark, SendInBlue etc. And be sure to spend the time to learn about and properly implement DKIM, SPF, and a DMARC policy.

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, adrian said:

Unfortunately this is probably a path to disaster these days - spam has made email painful and I think the only reliable option these days is to go with a transactional email service like MailGun, Postmark, SendInBlue etc. And be sure to spend the time to learn about and properly implement DKIM, SPF, and a DMARC policy.

ugh..ok.

but... it works fine from my localhost dev server though?!

Share this post


Link to post
Share on other sites
Just now, Jonathan Sachse Mikkelsen said:

ugh..ok.

but... it works fine from my localhost dev server though?!

I'll defer to horst on the troubleshooting of it actually sending. I am just talking about the deliverability issues you are likely to deal with. If the emails are only to site editors/staff you may be ok, but if they are being sent to site users then it's likely going to be an issue at least in my experience. Maybe others will disagree?

Share this post


Link to post
Share on other sites

pfffffff... ok everyone thanks for the replies!

but i think i just found the problem.

The client hadn't filled out the subject line field in the back-end, so i was trying to send emails with no subject lines.

so i guess all the send requests got filtered by a spam filter or something, or they were just invalid. But now they are being send.

Stupid mistake, which took way too many hours to correct! But that's web development for you i guess 😛 

  • Haha 1

Share this post


Link to post
Share on other sites

A great module that works absolutely fine out of the box but I am not happy having the SMTP password in plain text in the database. Is there maybe a reason I am just not getting why this is necessary?

  • Like 2

Share this post


Link to post
Share on other sites

Hi there,

I've been using Wire Mail for a while and now I would like to change its signature settings to send a signature along the email message "only when explicitly called via the API" (currently I have "automatically with every Message").

WireMail-signature-settings.png.a30ce971328a473dc13f39147919fcca.png

My questions are:

  1. How and where to call the signature API? That is, which code should I use and in which file should I add this code to have a "signature on demand"?
  2. I'm also using Form Builder and other PW modules that send emails with Wire Mail. How and where to set the signature via API for them, in particular for Form Builder?
  3. How to customise the signature if you don't want to use (and send) the Sender Signature set in Wire Mail module settings?

Share this post


Link to post
Share on other sites
On 3/3/2014 at 1:36 AM, horst said:

addSignature ( true | false ) - the default-behave is selectable in config screen, this can be overridden here
(only available if a signature is defined in the config screen)

Hi @LAPS,

current implementation only allows one signature, set in the config screen. The option only defines when it should be send: never everytime or defined via API.

Maybe it would be a nice addition to have a API method to pass in different signatures.

 

 

Edited by horst

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 bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...