Jump to content
horst

WireMailSmtp

Recommended Posts

You are the man! ^-^

Tomaten auf den Augen! Is there an english expression for it?

 

Share this post


Link to post
Share on other sites

Is there a property to set a "Return-Path:" which differentiates from the "From:" setting? At a first glance, I have found a method call

$this->emailMessage->SetHeader('Return-Path', $address);

inside WireMailSmtpAdaptor.php - I guess this can't be overridden individually?

Share this post


Link to post
Share on other sites

You can set a reply-to emailaddress in the config screen. If this isn't what you are after, there is a possibility to add individual headers. 

I'm on mobile now, thus not able to do a search. Can have a closer look later. 

Share this post


Link to post
Share on other sites

I moved my site over to a new host and am starting to see errors on my contact form which uses FormBuilder and routes via WireMailSMTP

When I submit a form, I receieve the following

Quote

Unable to verify successful email delivery of this form submission.

I wondered if this were a WireMailSMTP issues and tried the Test Settings checkbox

Quote

535 Incorrect authentication data

The thing is, my PostMark App authentication credentials haven't changed in the move.

Just to be sure, I have pasted them in place again with the same result. 

I then tried to create new Server API tokens, hooked these up and had the same error.

I don't believe this is an issue with PostMarkApp (just a hunch) and wondering if anyone had any ideas?

Wondered if it might be an issue with the new host stopping somewhow outgoing connections to PostMarkApp etc?

 

Share this post


Link to post
Share on other sites
35 minutes ago, Peter Knight said:

I moved my site over to a new host and am starting to see errors on my contact form which uses FormBuilder and routes via WireMailSMTP

When I submit a form, I receieve the following

I wondered if this were a WireMailSMTP issues and tried the Test Settings checkbox

The thing is, my PostMark App authentication credentials haven't changed in the move.

Just to be sure, I have pasted them in place again with the same result. 

I then tried to create new Server API tokens, hooked these up and had the same error.

I don't believe this is an issue with PostMarkApp (just a hunch) and wondering if anyone had any ideas?

Wondered if it might be an issue with the new host stopping somewhow outgoing connections to PostMarkApp etc?

 

The key thing is that you changed hosts and now are having issues getting mail to work properly.  You need to read up and review how mail is processed at your new hosting company.  After finding out how mail works at the new host, you may have to make a few changes to your WireMailSMTP configuration screen to get things working.  

Additionally, your new hosting company should be able to verify that needed ports are opened (not blocked) for your account.  Good luck.

  • Like 3

Share this post


Link to post
Share on other sites
43 minutes ago, cstevensjr said:

The key thing is that you changed hosts and now are having issues getting mail to work properly. 

Solved it. I had just assumed that allowing SMTP processing by 3rd parties was a basic feature of mosts hosts.

Unfortunately my new host (A2 Hosting) actually don't allow this unless you're on a high level plan. :-/

Share this post


Link to post
Share on other sites

I am using WireMailSmtp for a project. Interestingly everything worked fine while I used it from localhost but as soon as I deployed to webspace and tried using it from the domain it threw me following error:  "Call to undefined function wire()"

As I was searching for a solution I came to this page :

Now I changed every wire() call to ProcessWire\wire() and it worked. Maybe that should be included in a following update?

If I am wrong please enlighten me. And if that is the case you might as well explain to me what the problem was ^-^

 

Share this post


Link to post
Share on other sites
On 1/31/2018 at 11:06 AM, flydev said:

I just tested with an Office365 account with these settings, it works well. WireMailSMTP 0.3.0 here.

Look like its your credentials that are incorrect ?  Double check ;)

 

smtp.thumb.png.19fcd8a84f8e76a1e96e78304f38dbf6.png

Thanks @flydev, credentials were alright, but turned out it was the host that was the problem, site is running on A2. So it's the same problem @Peter Knight ran into.

Share this post


Link to post
Share on other sites
1 hour ago, nikoka said:

Thanks @flydev, credentials were alright, but turned out it was the host that was the problem, site is running on A2. So it's the same problem @Peter Knight ran into.

Hi @nikoka

If you're running A2 Hosting on a Lite, Swift or Turbo plan OR Reseller plan then external SMTP servers won't work.

Here's the full support page

I had just started using A2 for my hosting and was about to migrate about 10 sites from a VPS. Really glad I discovered this early when I had just moved the first site.

FYI I moved to Hostinger. I've had a few setup issues but they do allow external SMTP processing. 

 

Share this post


Link to post
Share on other sites

Does anybody get it working with Gmail SMTP? 

I always get

could not connect to the host "smtp.gmail.com": Connection refused 

I have tried all possible combinations of settings and ports and double check my credentials. The same thing on localhost and remote hosts. 

Is it something with Gmail? 

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

Get it working on the remote host, ports were closed.

But what can be wrong with the local setup? 

Share this post


Link to post
Share on other sites

@Zeka you need to go to Gmail settings and allow access for less secure apps there. Then it should work. 

  • Like 2

Share this post


Link to post
Share on other sites

I'm getting the following error when trying to add an attachment and not quite sure why:

Exception: Method WireMailSmtp::attachment  does not exist or is not callable in this context.

Is there any reason for this that anyone knows of?

Share this post


Link to post
Share on other sites

@ethanbeyer  here you go:

Should I be doing $mail = $modules->get('WireMailSmtp') or something?

$mail = wireMail();
$mail->to($name);
$mail->from = 'example@example.com';
$mail->subject("Subject Here");
$mail->body("Hello bla bla bla");
$mail->attachment($filepath);

$numSent = $mail->send();

 

Share this post


Link to post
Share on other sites

@ethanbeyer Got it sorted. Thank you for pointing that out. 

I got an instance of the module and then used $mail->attachments(array($filepath => $filename));

And that worked!

  • Like 1

Share this post


Link to post
Share on other sites

Hello, Ive but using the module for a few month now (its great thanks!)

Over the last couple of weeks I have been experiencing problems. Iam using a office 365 exchange account, which just randomly stops sending. If I run the test is setting it fails. After that if I deselect TLS save a then retick TLS save and test it works again. Any ideas what may be causing this?

Share this post


Link to post
Share on other sites

@Jon this sounds a little strange. Reading most of your comment, I would think that this might have something to do with your Office365 having sending limits that you're going over. The TLS issue is what makes it weird, though - because if it was a limits problem, that would not be happening.

Is there anything in the logs that gives what error is encountered, rather than saying it just stops sending?

  • Like 2

Share this post


Link to post
Share on other sites
On 5/29/2018 at 2:57 PM, ethanbeyer said:

@Jon this sounds a little strange. Reading most of your comment, I would think that this might have something to do with your Office365 having sending limits that you're going over. The TLS issue is what makes it weird, though - because if it was a limits problem, that would not be happening.

Is there anything in the logs that gives what error is encountered, rather than saying it just stops sending?

Hello Ethan,

Nothing in the logs I've now setup sendinblue and this has resolved the issues so I assumes its 365 like you suggested. The limit would be odd though as its not sending out that many emails

Cheers

Jon

Share this post


Link to post
Share on other sites

Solution to problem found on another forum post but cannot see how to delete this post.


 

Quote

 

 

Edited by MrKing
Problem solved

Share this post


Link to post
Share on other sites

We are getting the "WireMailSmtpConfig: ERROR: SMTP settings did not work" error with these settings (real address replaced with ***). 

Local hostname: www.***.com
SMTP Hostname: ***.mail.protection.outlook.com
SMTP Port: 25
SMTP User: (required to be left empty)
SMTP Password: (required to be left empty)
Use START-TLS: Yes

Authentication is made using something called O365 (assuming it means Office 365). Could this be the reason nothing works? Does WireMail: SMTP even work with user and password left empty?

What does the Authentication Mechanism stand for? An IP address?

In the front end when trying to submit from by Formbuilder I get "Notice: Undefined index: replyToName in ***.com/httpdocs/wire/core/WireMail.php on line 319

Share this post


Link to post
Share on other sites

For an outlook.com email address, I use this successfully. Do these work for you?

image.thumb.png.73792917c007265ce8e7615086f2bc77.png

Share this post


Link to post
Share on other sites

@adrian Unfortunately no. Tech support from the hosting company was also quite sure that the information we've entered is correct.

Share this post


Link to post
Share on other sites

Does anyone know if using SMTP user without a password is a problem? Authentication is taken care of by something else in this case.

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 BitPoet
      Here's a little text formatter module that redirects all external links found in a textarea (e.g. for hit counting) to a given URL.
      TextformatterExternalRedirect
      GitHub repo
      As TextFormatters do, this module modifies the contents of the textarea (HTML) at rendering time. It prepends the given URL to the link address for external links (http and https), optionally makes sure that the link is opened in a new window and allows you to add css classes to such links.
      All options can be configured in the module's configuration settings.
      Usage:
      Download the zip archive and extract it to site/modules, the rename the top folder to TextformatterExternalRedirect Go to the backend and select "Modules" -> "Refresh", then click "Install" for "External Link Redirect" Click "Settings" and configure the module
      Go into the field configuration for the field(s) you want this formatter to apply to and add it from the dropdown
      Done, now any external links in the configured fields will have the configured settings applied Feel free to leave feedback and post and questions you have here.
       
    • By teppo
      Hey folks!
      Took a couple of late nights, but managed to turn this old gist of mine into a proper module. The name is SearchEngine, and currently it provides support for indexing page contents (into a hidden textarea field created automatically), and also includes a helper feature ("Finder") for querying said contents. No fancy features like stemming here yet, but something along those lines might be added later if it seems useful (and if I find a decent implementation to integrate).
      Though the API and selector engine make it really easy to create site search pages, I pretty much always end up duplicating the same features from site to site. Also – since it takes a bit of extra time – it's tempting to skip over some accessibility related things, and leave features like text highlighting out. Overall I think it makes sense to bundle all that into a module, which can then be reused over and over again 🙂
      Note: markup generation is not yet built into the module, which is why the examples below use PageArray::render() method to produce a simple list of results. This will be added later on, as a part of the same module or a separate Markup module. There's also no fancy JS API or anything like that (yet).
      This is an early release, so be kind – I got the find feature working last night (or perhaps this morning), and some final tweaks and updates were made just an hour ago 😅
      GitHub repository: https://github.com/teppokoivula/SearchEngine Modules directory: https://modules.processwire.com/modules/search-engine/ Demo: https://wireframe-framework.com/search/ Usage
      Install SearchEngine module. Note: the module will automatically create an index field install time, so be sure to define a custom field (via site config) before installation if you don't want it to be called "search_index". You can change the field name later as well, but you'll have to update the "index_field" option in site config or module settings (in Admin) after renaming it.
      Add the site search index field to templates you want to make searchable. Use selectors to query values in site search index. Note: you can use any operator for your selectors, you will likely find the '=' and '%=' operators most useful here. You can read more about selector operators from ProcessWire's documentation.
      Options
      By default the module will create a search index field called 'search_index' and store values from Page fields title, headline, summary, and body to said index field when a page is saved. You can modify this behaviour (field name and/or indexed page fields) either via the Module config screen in the PocessWire Admin, or by defining $config->SearchEngine array in your site config file or other applicable location:
      $config->SearchEngine = [ 'index_field' => 'search_index', 'indexed_fields' => [ 'title', 'headline', 'summary', 'body', ], 'prefixes' => [ 'link' => 'link:', ], 'find_args' => [ 'limit' => 25, 'sort' => 'sort', 'operator' => '%=', 'query_param' => null, 'selector_extra' => '', ], ]; You can access the search index field just like any other ProcessWire field with selectors:
      if ($q = $sanitizer->selectorValue($input->get->q)) { $results = $pages->find('search_index%=' . $query_string . ', limit=25'); echo $results->render(); echo $results->renderPager(); } Alternatively you can delegate the find operation to the SearchEngine module as well:
      $query = $modules->get('SearchEngine')->find($input->get->q); echo $query->resultsString; // alias for $query->results->render() echo $query->pager; // alias for $query->results->renderPager() Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 Note: later versions of the module may require Composer, or alternatively some additional features may require installing via Composer. This is still under consideration – so far there's nothing here that would really depend on it, but advanced features like stemming most likely would.
      Installing
      It's the usual thing: download or clone the SearchEngine directory into your /site/modules/ directory and install via Admin. Alternatively you can install SearchEngine with Composer by executing composer require teppokoivula/search-engine in your site directory.
    • By teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if someone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put I've been using MSN (...) for years, and it's been great – but there are some issues with it, particularly in the markup generation area, and it also does some things in a way that doesn't quite work for me – the xtemplates thing being one of these. In some ways less about features, and more about style, I guess 🙂
      Anyhow, in MarkupMenu I've tried to correct those little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and with PHP 7.1+ in mind, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) still on my todo list.
      One more small(ish) difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site had a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to leave that out 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM – one of those three or four letter abbreviations anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework" since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By Robin S
      After forgetting the class name of the wonderful AdminPageFieldEditLinks module for what feels like the 100th time I decided I needed to give my failing memory a helping hand...
      Autocomplete Module Class Name
      Provides class name autocomplete suggestions for the "Add Module From Directory" and "Add Module From URL" fields at Modules > New.
      Requires ProcessWire >= v3.0.16.
      Screencast

      Installation
      Install the Autocomplete Module Class Name module.
      Configuration
      Add Module From Directory
      Choose the type of autocomplete suggestions list: "Module class names from directory" or "Custom list of module class names". The latter could be useful if you regularly install some modules and would prefer a shorter list of autocomplete suggestions. The list of class names in the modules directory is generated when the Autocomplete Module Class Name module is installed. It doesn't update automatically (because the retrieval of the class names is quite slow), but you can use the button underneath when you want to retrieve an updated list of class names from the directory. Add Module From URL
      If you want to see autocomplete suggestions for the "Add Module From URL" field then enter them in the following format:
      [autocomplete suggestion] > [module ZIP url]
      Example: RepeaterImages > https://github.com/Toutouwai/RepeaterImages/archive/master.zip Awesomplete options
      The "fuzzy search" option uses custom filter and item functions for Awesomplete so that the characters you type just have to exist in the autocomplete suggestion item and occur after preceding matches but do not need to be contiguous. Uncheck this option if you prefer the standard Awesomplete matching. Custom settings for Awesomplete can be entered in the "Awesomplete options" field if needed. See the Awesomplete documentation for more information.  
      https://github.com/Toutouwai/AutocompleteModuleClassName
      https://modules.processwire.com/modules/autocomplete-module-class-name/
×
×
  • Create New...