Este plugin foi encerrado e não está mais disponível para download.

Postman SMTP Mailer e Log de Emails

Descrição

Postman is a next-generation SMTP Mailer, software that assists in the delivery of email generated by your WordPress site. Postman is the first and only plugin to support the latest security standards. With OAuth 2.0, there is no need to store your email passsword in the WordPress database where it might be found.

Postman is one year old! SparkPost API Integration is coming soon as Mandrill is no longer offering a free service.

O Teste de Conectividade e o Assitente de Configuração inteligente varrem o seu servidor de SMTP para detectar bloqueios de firewall e eliminar erros nas configurações. O Log de E-mails embutido é um recurso valoioso para diagnósticar problemas com e-mails. Mesmo em hosts que bloqueiam portas padrão de SMTP, como o GoDaddy ou o Bluehost, não conseguem parar seus e-mails pois o Postman pode entregar via HTTPS se não puder usar SMTP.

Postman is not another WP Mail SMTP clone like WP Bank or Easy SMTP. It replaces the default WordPress SMTP library, PHPMailer, with the heavy-duty Zend_Mail. Never lose an email to PHP mail() again.

Standard Features

  • Easy-to-use, powerful Setup Wizard for perfect configuration
  • Commercial-grade Connectivity Tester to diagnose server issues
  • Faz o log e reenvia todos -emails; veja a causa exata dos e-mails que falharam
  • Suporta Alfabetos Internacionais, E-mail HTML e MultiPart/Alternative
  • Supports forced recipients (cc, bcc, to) and custom email headers
  • SASL Suporta: Plain/Login/CRAM-MD5/XOAUTH2
  • Suporte de Segurançat: SMTPS e STARTTLS (SSL/TLS)
  • Copia configuração para outras instâncias do Postman

OAuth 2.0 Features

  • Supports the proprietary OAuth 2.0 implementations of Gmail, Hotmail and Yahoo
  • Fire-and-forget delivery continues even if your password changes
  • Gmail: By combining OAuth2 and the Gmail API, Postman can deliver where other plugins can not

WebService (HTTPS) Email Features

  • Gmail API for sending Gmail and Google Apps email (requires a Google account)
  • Mandrill API for sending any email (requires a Mandrill account)
  • COMING SOON: Sparkpost API for sending any email (requires a Sparkpost account)
  • SendGrid API for sending any email (requires a SendGrid account and PHP 5.3)

O Postman precisa de tradutores! Se você não é um nativo na língua inglesa, por favor envolva-se!

Compatível com…

Requirements

  • WordPress 3.9 and PHP 5.2 with SPL and iconv
  • Memory: 750KiB per process at idle
  • Entrega confiável de e-mail com domínios de e-mail personalizados requer um registro SPF
  • A entrega confiável por SMTP requer as credenciais com um provedor de serviços
  • O uso dos recursos de OAuth 2.0 requer as credenciais do Gmail, Hotmail ou Yahoo

Concede permissão a mensagens de erro OAuth

Por favor atente para que os campos Client ID e Client Secret NÃO são seu nome de usuário e senha. Eles são apenas para as credenciais OAuth.

Erro autenticando com este Client ID. [Erro ao executar wp_remote_post: O usuário bloqueou requisições via HTTP.]

Seu site WordPress está configurado com WP_HTTP_BLOCK_EXTERNAL para evitar conexões de saída. Adicione uma regra de lista segura ao wp-config.php

define(‘WP_ACCESSIBLE_HOSTS’, ‘www.googleapis.com, login.live.com, api.login.yahoo.com’);

Erro autenticando com este Client ID. [Erro ao executar wp_remote_post: Falha ao conectar-se a xxxx]

Há um firewall na porta 443 entre você e o servidor OAuth2. Abra a porta para conexões de saída.

Erro: redirect_uri_mismatch

  • Você não entrou com a URI de redirecionamento correta, assist ao vídeo de instrução
  • Você usou um endereço IP no lugar de nome de domínio (não é permitido)

Erro: invalid_client … sem e-mail de suporte

Você se esqueceu de escolher um endereço de e-mail na tela de consentimento.

Mensagens de erro SMTP

Erro de comunicação [334] – tenha certeza de que o ‘E-mail de’ seja a mesma conta usada para criar o Client ID.

  • Isto é causado quase sempre por estar logado no Google/Microsoft/Yahoo com um usuário diferente do que foi configurado no Postman para enviar email. Saia e tente novamente com o usuário correto
  • Faça login no Webmail e veja se há um aviso de “Atividade Suspeita” esperando pela sua atenção

Não foi possível abrir o socket

  • Seu provedor pode ter instalado um firewall entre você e o servidor. Peça a eles para abrirem as portas.
  • Você pode ter tentado usar (incorretamente) SSL pela porta 587. Verifique suas configurações de encriptação e porta.

Operação expirou

  • Seu provedor pode ter conectividade pobre com o servidor de e-mail. Tente dobrar o tempo esgotado de leitura.
  • Seu provedor pode ter instalado um firewall (DROP packets) entre você e o servidor. Peça a eles para abrirem as portas.
  • Você pode ter tentado usar (incorretamente) SSL pela porta 587. Verifique suas configurações de encriptação e porta.

Conexão negada

Seu provedor provavelmente instalou um firewall (pacotes REJECT) entre você e o servidor. Peça para eles abrirem as portas.

503 má sequência de comandos

Você configurou a segurança TLS quando não deveria ter selecionado segurança.

Mecanismo de autenticação XOAUTH2 não suportado

Você pode estar em uma Rede Virtual Privada (VPN) que está devastando suas comunicações. Pule do navio.

E-mail foi parar na pasta de Spam

Para evitar ser marcado como spam, você deve provar que seu e-mail não é forjado. Em um domínio personalizado, é VOCÊ quem deve ajustar isso:

  • Certifique-se de estar usando o servidor SMTP correto com autenticação – o servidor SMTP correto é o que foi definido no seu registro SPF do serviço de email
  • Se você usa um nome de domínio personalizado, adicione um registro SPF ao seu arquivo de zona DNS. O SPF é específico para o seu provedor de e-mail, por exemplo Google
  • Se você usar um nome de domínio personalizado para e-mail, adicione um registro DKIM ao seu arquivo de zona DNS e envie sua Chave de Domínio (uma assinatura digital) para, por exemplo Google

Imagens de tela

  • WordPress Dashboard showing both the Postman widget and At a Glance widget
  • Main Settings screen - shows Main Menu and current status (new installation)
  • Setup Wizard (step 1) - Import data from other plugins
  • Setup Wizard (step 4) - Connectivity Test
  • Manual Configuration - Account Settings: Password Authentication
  • Manual Configuration - Account Settings: OAuth 2.0 Authentication
  • Manual Configuration - Message Settings
  • Manual Configuration - Advanced Settings
  • Test Email utility screen - Oops! Wrong password
  • Emai Log screen
  • Connectivity Test utility screen
  • Diagnostic Information screen

Instalação

To send email reliably, you must use the SMTP server assigned to that email. If Postman is unable to connect to the right SMTP server, you may have to ask your host to open the ports, or create a new email account managed by your host, or switch hosts!

The Connectivity Test utility will tell you which ports are open and the actions available to you.

Easy install and setup! (Recommended for all users)

  1. Install and activate the plugin through the ‘Plugins’ menu in WordPress.
  2. In the WordPress ‘Settings’ menu select ‘Postman SMTP’.
  3. Choose ‘Start the Wizard’ and follow the instructions.

To manually configure Password Authentication (Intermediate users only)

  1. Choose configure manually
  2. In ‘Transport’, choose ‘SMTP’
  3. In ‘Outgoing Mail Server Hostname’, enter the SMTP Server’s hostname
  4. In ‘Outgoing Mail Server Port’, enter the SMTP Server’s port
  5. In ‘Security’ choose the appropriate type (a good guess is SMTPS for port 465, STARTTLS otherwise)
  6. In ‘Authentication’, choose the authentication type (a good guess is ‘Plain’)
  7. If your Authentication method is not ‘None’, enter your username (probably your email address) and password.
  8. Choose the ‘Message’ tab.
  9. In ‘Envelope From Address’ enter your email address. This MUST be the same address you login to webmail with.
  10. In ‘Message From Address’ enter your email address. Or this can be an alias, mailing list, or group email if you wish.
  11. Choose the Save Changes button.
  12. Send yourself a test email.

To manually configure OAuth 2.0 Authentication (Advanced users only)

  1. Choose configure manually
  2. In ‘Transport’, choose ‘SMTP’
  3. In ‘Outgoing Mail Server Hostname’, enter the SMTP Server’s hostname
  4. In ‘Outgoing Mail Server Port’, enter the SMTP Server’s port
  5. In ‘Security’ choose the appropriate type (a good guess is SMTPS for port 465, StartTLS otherwise)
  6. In ‘Authentication’ choose ‘OAuth 2.0’
  7. Postman will give you a link to the Client ID maintenance page of your email service provider. Create a Client ID for your WordPress site.. instructions for this are detailed in the FAQ
  8. Copy your generated Client ID and Client secret into the plugin’s Settings page.
  9. Choose the ‘Message’ tab.
  10. In ‘Envelope From Address’ enter your email address. This MUST be the same address you login to webmail with.
  11. In ‘Message From Address’ enter your email address. Or this can be an alias, mailing list, or group email if you wish.
  12. Choose the Save Changes button.
  13. Choose the ‘Request OAuth2 Permission’ link and follow the instructions.
  14. Send yourself a test email.

Postman is developed on OS X with PHP 5.5.14 and Apache 2.4.9. Postman is tested in a Red Hat OpenShift environment with PHP 5.3.3 and Apache 2.2.15 with Gmail, Hotmail and Yahoo Mail (US). Postman is tested with mailtrap.io.

FAQ

O que é OAuth 2.0?

Um substituto moderno para a tradicional autenticação baseada em senha. O Postman suporta as implementação OAuth 2.0 dos três maiores provedores de e-mail: Gmail, Hotmail e Yahoo Mail.

Como o OAuth 2.0 funciona?

Postman requer um token de acesso limitado OAuth 2.0 (chave básica) para acessar as APIs (entrar em casa) e realizar um serviço específico (lida com Gmail, Google Docs ficam de fora) sem a necessidade de você entregar suas credenciais de nome e email (chave mestra da casa).

Assim que o acesso é concedido, o Postman comandará a função wp_mail() do WordPress para prover um subsistema de e-mail incrivelmente estável.

Eu não posso simplesmente dizer ao Google para permitir aplicativos menos seguros e usar minha senha antiga?

Google tem uma configuração em permitir aplicativos menos seguros mas esta opção não está disponível se você estiver usando Google Apps para administrar um domínio.

Existem muitas razões para o porquê de OAuth 2.0 ser melhor do que qualquer mecanismo baseado em senha:

  • Postman nunca irá pedir pela sua senha, então ela não será roubada
  • If you change your password regularly, you will never have to update Postman’s configuration
  • You have tighter control over the data Postman has access to. For Google users it can never access your Calendar or Docs or YouTube; for Yahoo users it can never access your Flickr
  • If your WordPress site gets hacked, you can revoke Postman’s email access without impacting any other application or website that has access to your account

NUNCa entregue sua senha do Gmail, Microsoft ou Yahoo a um terceiro ou a um programa terceiro que você não confie completamente.

O que é Client ID?

Para usar OAuth, seu site precisa de um Client ID próprio. o Client ID é usado para controlar a autenticação e a autorização e está ligado a URL específica do seu site. Se você administra muitos websites, você precisará de um Client ID diferente para cada um.

Como eu consigo uma Client ID do Google? (Apenas para usuários do Gmail!)

  1. Go to Google Developer’s Console and login with the same email address that you are configuring Postman with.
  2. Choose ‘Create a New Project’. This project will be for Postman SMTP only.
  3. Select ‘Consent Screen’ from under ‘APIs & auth’. Into ‘Email address’ choose the correct Gmail address and in ‘Product name’ put ‘Postman SMTP’. Choose ‘Save’.
  4. Select ‘Credentials’ from under ‘APIs & auth’. Choose ‘Create a new Client ID’.
  5. Para o ‘Tipo de Aplicação’ use ‘Aplicação web’.
  6. Em ‘Origens JavaScript autorizadas’ entre as ‘Origens Javascript’ dados pelo Postman (seja pelo assistente[screenshot], ou pela página do manual de configuração[screenshot]).
  7. In ‘Authorized Redirect URIs’ enter the ‘Redirect URI’ given by Postman (either from the wizard[screenshot], or from the manual configuration page[screenshot]).
  8. Escolha ‘Criar ID de Cliente’
  9. Digite o ID de Cliente e o Segredo de Cliente exibidos aqui na página de configurações do Postman captura de tela.
Como eu consigo uma Client ID da Microsoft? (Apenas para usuários do Hotmail/Live/Outlook.com!)
  1. Vá até Microsoft account Developer Center e selecione ‘Criar aplicação’.
  2. No campo ‘Nome da aplicação’ digite ‘Postman SMTP’. Selecione ‘Eu aceito.’
  3. Selecione ‘API Settings’ em ‘Configurações’.
  4. Em ‘Redireciona URL’, entre com a URL de redirecionamento dada pelo Postman (Através do assistente ou através da página de configuração). Selecione Salvar.
  5. Selecionar ‘Ajustes do Aplicativo’ em ‘Ajustes’.
  6. Entre com a Client ID e com o Client Secret mostrados aqui na página de ajustes do Postman.
Como eu consigo uma Client ID do Yahoo? (Apenas para usuários do Yahoo Mail!)
  1. Vá para Yahoo Developer Network e selecione ‘Create an App’. (Criar um Aplicativo)
  2. No campo ‘Application Name’ entre com ‘Postman SMTP’. Para ‘Application Type’ escolha ‘Web Application’.
  3. Em ‘Home Page URL’, entre com a ‘Home Page URL’ fornecida pelo Postman.
  4. Em ‘Domínio de Retorno’, entre com o ‘Domínio de Retorno’ fornecido pelo Postman.
  5. Em ‘Permissões da API’ escolha ‘Mail’. Em ‘Mail’ escolha ‘Read/Write’
  6. Clique em ‘Criar Aplicativo’
  7. Entre com a Client ID e com o Client Secret mostrados aqui na página de ajustes do Postman.
Como eu revogo o acesso do Postman ao OAuth 2.0?

Avaliações

Potsman is now >> POST SMTP <<

Like many others, I had to replace postman as it stopped working, just found out it has been updated under a new name:

Post SMTP Mailer/Email Log

(I followed the review request link in the new plugin and ended up here and thought I should share these pieces of information!)

XSS Vulnerability and not updated – WAS a great plugin

I had originally given this plugin a 5 star rating.

Then I saw this review:

Postman SMTP Mailer/Email Log is prone to a cross-site scripting vulnerability – https://wordpress.org/support/topic/postman-smtp-maileremail-log-is-prone-to-a-cross-site-scripting-vulnerability/

I confirmed that this is correct.

And then I also noticed that this plugin has not been updated in 2 years:
Last updated:
2 years ago

For the above reasons I am changing my review rating to 1 star.

Disappointed to see that such a great plugin was not coded securely and is not being updated. I wont use it for these reasons.

My old 5 star review:

First tried to write my own code to config wp mail function to use SMTP. The code is pretty easy, but hard to debug – I could not get it to work.
Then tried some other plugins – no success.
Then tried Postman plugin and I really like its setup process – provides helpful hints, tests connections to the server, has a very good log – with these I was able to get SMTP working in a few minutes.
Outstanding plugin!

O Melhor!

O único que resolveu o meu problema em relação aos e-mails do Woocommerce estarem indo para o Spam dos meus clientes. Após instalar e configurar o plugin, os e-mails imediatamente começaram a ir para a caixa de entrada do cliente! Simples, fácil e muito funcional! PERFEITO!!

Best by far

After years of using several different SMTP plugins, we settled on this one for all the sites we work with. There are three reasons.

1. It supports more services than anything from SMTP, to SendGrid API to AWS SES.
2. It includes outgoing email logging which is _priceless_ in debugging issues
3. It is rock solid

Leia todas as 458 avaliações

Contribuidores e desenvolvedores

“Postman SMTP Mailer e Log de Emails” é um software com código aberto. As seguintes pessoas contribuíram para este plugin.

Contribuidores

“Postman SMTP Mailer e Log de Emails” foi traduzido para 16 localidades. Obrigado aos tradutores por suas contribuições.

Traduzir “Postman SMTP Mailer e Log de Emails” para o seu idioma.

Interessado no desenvolvimento?

Navegue pelo código, dê uma olhada no repositório SVN ou assine o registro de desenvolvimento via RSS.

Registro de alterações

1.7.2 – 2015-11-08

  • [Ticket] – v1.7 ignores the content-type header set in the Additional Headers. Fixed.
  • [Ticket] – Fixed an issue where v1.7 admin screens crash for non-admin users when Postman is not configured. Fixed a multiste issue where v1.7 site admins lose access to their Postman settings screen. Special thank-you to Domi2015 for giving me access for testing! 🙂
  • Localized jQuery Validation messages
  • Localized MyMail messages
  • Put the local translation files back, as WordPress on-line translations do not work as advertised

1.7.1 – 2015-11-05

  • [Ticket] – the Optimizepress plugin calls wp_mail before the WordPress init hook, before Postman is fully initialized, so I made a change to accomodate this behavior
  • [Ticket] – v1.7 admin screen may become inaccessible after upgrading. Fixed.
  • [Ticket] – v1.7 breaks compatibility with WordPress Leads. Fixed.

1.7.0 “Iliana” – 2015-11-03

  • Happy Halowe’en! 30,000 installations! – 2015-10-31
  • Integrated Mandrill API
  • Integrated SendGrid API
  • Language files have been removed from the plugin as translations are now performed on-line. If you are a non-English speaker please constribute!
  • Postman commandeers email when activated and sends using the WordPress default of localhost:25 – this is for people who want to use it to diagnose email problems without configuring SMTP
  • Re-send failed e-mails from the Email Log screen
  • Added an internal ‘manage_postman_smtp’ capability for advanced management with, for example, User Role Editor
  • [Ticket][Ticket] Added an import/export tab to the Advanced Configuration screen for those who want to duplicate settings between sites.
  • [Ticket] Added option to disable e-mail address validation
  • [Ticket] Fix for fatal error when using a non-administrator in the admin menu.

1.6.24 – 2015-09-10

  • 20,000 installations! – 2015-09-09
  • Translated into Greek, thank-you Michael Kotsarinis!
  • Diagnostic Test displays all the wp_mail-related hooks of active plugins and themes
  • When validating e-mail addresses, Postman will disclose which field has a validation issue in the error message
  • Default log entries bumped from 10 to 250
  • [Ticket] Added nasty fake input field hack to prevent browsers from autofilling username/password fields.
  • [Ticket] Added a warning to the Email Log for emails that have an empty subject line
  • [Ticket] Test Email detects Ajax errors and displays them in the Status window
  • [Ticket] Removed the references to images in Postman’s copy of jquery-ui.css causing HTTP 404
  • [Ticket] Fixed an Ajax name collision with the plugin MemberPress
  • [Ticket] Some sites can not handle International (UTF-8) characters in the Test Email. Fixed.
  • [Ticket] Fix for PHP Notice: Undefined offset: 1 in postman-smtp/Postman/Postman-Mail/google-api-php-client-1.1.2/autoload.php on line 22
  • [Ticket] Silenced PHP warnings in Zend_Mail from ini_set

1.6.23 – 2015-06-27

  • 10,000 installations! – 2015-06-27
  • 9,000 installations! – 2015-06-20
  • [Ticket] Causes bbPress or Buddy Press to generate warning messages. Fixed.
  • [Ticket] User reported error “Fatal error: Internal Zend error – Missing class information” – Whoops, used ‘require’ PostmanState.php instead of ‘require_once’ PostmanState.php which was causing errors. Fixed.
  • [Ticket] [Ticket] MyMail Newsletter Plugin for WordPress refuses to use wp_mail. I don’t want to make this a habit, but I’ve integrated Postman with MyMail’s proprietary delivery mechanism.
  • [Ticket] Found an environment where the plugin’s call to new Exception was creating PHP Fatal errors. Fixed.
  • [Ticket] Perform validation on all email headers before sending message
  • The Gmail API transport displays a copy of the payload during the Send Email Test and saves this payload to the Email Log
  • No longer shows the Javascript pop-up if the error is caused by the user cancelling everything (by checking JSON response.responseText for null)

1.6.22 – 2015-06-14

  • Finally realized that for the last five months I’ve been relying on register_activation_hook to fire during plugin updates – and it doesn’t. Lovely. Well this change should eliminate all the “update doesn’t work!” bugs for good.
  • [Ticket] I enable Strict mode when I code Postman to ensure it’s error free and I forgot to turn it off. This was causing all plugins and themes to show their warnings. Fixed.
  • [Ticket] I didn’t thoroughly test the Gmail API, causing “Catchable fatal error: Argument 1 passed to PostmanGmailApiModuleTransport::getAuthenticationType() must be an instance of PostmanOptions, none given.” Fixed.
  • [Ticket] I didn’t thoroughly test the Gmail API, it wasn’t warning the user if the Envelope Sender Address is missing. Fixed.
  • [Ticket][Ticket] Found a problem in the Activation Handler. It was re-encoding passwords when it shouldn’t have been. Fixed.

1.6.18 – 2015-06-13

  • 8,000 installations! Big milestone! The author of Contact Form 7 has officially endorsed Postman SMTP as the SMTP plugin of choice! You can’t wipe the smile from my face 😀
  • [Ticket] Postman is determining the current user’s admin capability incorrectly. Fixed.
  • [Ticket] Added an additional From field, the Envelope From Address, so users can use a different From address than the Account address (for example, to use a Google Apps’ Group email address)
  • Added a uniqueness (based on site URL) to the lock filename in case this is shared hosting
  • Persistence-level updates now run across all subsites on a multisite installation

1.6.17 – 2015-06-08

  • You know you’re having a really bad day when you have to have do three releases. Fix for “Fatal error: Call to a member function addError() on a non-object”. This happens when wp_mail is blocked by another plugin and a non-admin user accesses the site.
  • [Ticket] Fixed a bug “Fatal error: Cannot redeclare IsNullOrEmptyString()” I introduced in v1.6.15
  • Added Cc and Bcc addresses to Email Log
  • [Ticket][Ticket] Force a Logout of Google before launching the Developers Console so it’s obvious to the user which account is being used
  • Now using Google Developers Console Gmail Wizard URL in place of Google Developers Console URL to simplify Client ID creation
  • [Ticket] Removing the BCC header in the case of the Gmail API was incorrect and causing lost recipients. Fixed.
  • Fixed a compatibility issue (PHP Fatal Error) with the Postman Gmail API Extension

1.6.14 – 2015-06-05

  • [Ticket] Fixed a bug (PHP Warning) I introduced in v1.6.13
  • 7,000 installations!
  • Translated into Dutch, thank-you Louise
  • [Ticket] Add process-locking to make sure the OAuth2 token is refreshed synchronously
  • Use the Zend_Mail setReturnPath option to communicate the Mail-From and Sender as the SMTP account, allowing arbitrary addresses in the From header
  • [Ticket] Added Emoji lock icons to Dashboard and Main Setting screens to indicate security
  • [Ticket] Emails from the Email Users plugin were causing undeliverable errors – fixed by removing the SMTP Return-Path header that Email Users injects

1.6.12 – 2015-05-30

  • 6,000 installations! – 2015-05-26
  • Postman now calls wp_mail when sending a test email. This marks the beginning of the “Postman API”
  • Shaved admin memory use from ~6MB to ~4MB; Non-admin memory use holds at ~2MB
  • Now loading the Sent Email post type for all admin screens, in case other custom post type-related plugins (e.g. WordPress Importer) need it
  • Wasn’t comfortable how plugin_data was being retrieved, so reverted back to hard-coded plugin name and version
  • Save original wp_mail parameters to Email Log so that a Resend action can be implemented
  • [Ticket] Removed sanitize_text_field from the PostmanSanitizer to prevent corruption of some passwords
  • [Ticket] Removed the WordPress function call wp_slash – systems that don’t support it can now use logging
  • A lot of general code clean-up and memory optimizations

1.6.11 – 2015-05-22

  • [Ticket] Fix for “Fatal error: Call to undefined function spritnf() in PostmanEmailLogController.php on line 284” – sometimes PHP really sucks compared to Java
  • Added a link to a HowTo Video for configuring Google OAuth 2.0 in the OAuth2 authentication section

1.6.10 – 2015-05-18

  • 5,000 installations!
  • Looks for php_openssl and php_socket in the Pre-Requisites check
  • [Ticket] I hate when you have to have a fix for a fix. It means you need to hire more testers.
  • [Ticket] Changed the way Postman performs the API Connectivity Test to more resemble how Google does it
  • [Ticket] Found a host that the Connectivity Test gets confused on : send.one.com. STARTTLS detection was failing. Fixed.
  • [Ticket] Some users insist on running Postman in WordPress < 3.6 which has no wp_slash function. Logging is disabled in this case.

1.6.8 – 2015-05-14

  • [Ticket] Found a PHP envrionment that choked in the catch block trying to call a function (get transcript) on an object instantiated in the try (mail engine). Fixed.
  • [Ticket] If wp_mail is called with a recipient list that ends in a comma, Postman tries to add an empty address to the message. Fixed.
  • The SMTP Session Transcript was not being saved for errors! Fixed.

1.6.6 – 2015-05-12

  • [Ticket][Ticket][Ticket][Ticket][Ticket] Fixed a long-standing bug where Postman would ignore the Grant Code from an OAuth provider if it wasn’t in the very next HttpRequest that the site received. Changed this to use a three-minute window.

1.6.5 – 2015-05-10

  • [Ticket] Fixed a Javascript bug
  • Added an Ajax failure handler to every Ajax post

1.6.4 – 2015-05-08

  • SMTP transport requires a Sender Email Address be set
  • Wizard will not clear the hostname if it comes back null
  • If the host does not support “humanTime”, the Email Log will fall back to an ISO date
  • Added a new advanced option: Transcript size to adjust how much of the transcript is saved in the log
  • The wizard gets confused if the user specified auth type is undefined for the newly chosen socket. for example, a gmail address, with a mailtrap.io server, toggling between the gmailapi socket and the mailtrap socket. Fixed.
  • Show a warning on the main setting screen if the Delivery mode is not set to Production

1.6.2 – 2015-05-06

  • 4,000 installations!
  • [Ticket] Some of the changes released in v1.6 broke the Gmail Extension. Fixed.
  • [Ticket] Added a new advanced option: Stealth Mode to hide the Postman X-Mailer signature
  • Added a Transcript option in the Email Log
  • Fixed how the Wizard handles new GoDaddy Office-365 supported email

1.6.1 – 2015-05-04

  • You test and test and test, and there’s always a bug. Fixed a problem in the Port Recommender where it thought STARTTLS was offered when it isn’t (test case: test@aol.com)

1.6 – 2015-05-03

  • Fold all code from the Postman Gmail Extension back into Postman
  • Remove warning from main screen for sender override if it’s already on
  • Delivery mode – production, logging, test
  • Help screens
  • Log all email attempts with error messages (if any)
  • Truncate logs to max amount
  • View all the email attempts, and view a single entry
  • Delete single, delete batch, and delete the entire log on pugin data purge
  • Highlight Logging option to users
  • Obscure password from front-end
  • Ask to see password when typing
  • When the wizard is looking up details on the email address, disable the smtp hostname field
  • Wizard check server ID and warn for MITM ‘attack’
  • Check for GoDaddy SMTP server during Wizard and use that SMTP server
  • Check for Gmail during wizard and remember for gmail api option.
  • Present choices to user when select the auth type and socket in wizard more elegantly (radio buttons?)
  • Warn when using AUTH with NO encryption – done with padlock emoji
  • Add hostname to connectivity test table.
  • Remove hard-coded plugin version number

1.5.13 – 2015-04-22

  • 3,000 installations!

1.5.13 – 2015-04-18

  • Minor fix in Wizard: OAuth labels weren’t updating dynamically (since v1.5.11)
  • Lots of changes at Yahoo’s Developer Network required changes here: updated format of Callback Domain; updated Yahoo Developer Network portal launch link; renamed Consumer Key/Secret to Client ID/Client Secret; updated FAQ for Yahoo Client ID instructions
  • [Ticket] Updated stylesheet to avoid interference from Dating Solutions Plugin (DSP)

1.5.12 – 2015-04-14 – The Jamaican release!

  • [Ticket] PHP 5.2 users: fix test messages that show failures but still get delivered; fix Contact Form 7 submission freezes
  • Translated into Turkish, thank-you ercan yaris

1.5.11 – 2015-04-05

  • 2,000 installations! 😀
  • Commercial-grade improvements to Connectivity Test and Setup Wizard. The new wizard prevents misconfiguration by interrogating the MTA for capabilities and intelligently suggests the best settings for the user. Steve Jobs would be proud.
  • Fixed Wizard’s MSA hostname guess for GoDaddy addresses (smtp.secureserver.net is the MTA not the MSA)
  • Fixed Wizard’s MSA hostname guess for Outlook 365 addresses (smtp.live.com is for their free Hotmail service)
  • Added French/Italian translation for JQuery Validation

1.5.10 – 2015-03-29

  • Fix for Fatal error: Cannot redeclare class PEAR_Common in C:\PHP5\PEAR\PEAR\Common.php – similar to this error in WP Minify

1.5.9 – 2015-03-26

  • Added JQuery tabbed UI for manual configuration screen
  • Added functionality to add to, cc, and bcc recipients to every message
  • Added functionality to add custom headers to every message – useful for Mandrill “SMTP” headers
  • [Ticket] The Setup Wizard will check for IP addresses in the site URL and warn the user when they are about to configure OAuth 2.0 that this will fail.
  • [Ticket] Added functionality to prevent plugins and themes from overriding both the sender name and sender email address
  • [Ticket] Hide PHP warnings from stream_set_timeout() in case the host has disabled this function.

1.5.8 – 2015-03-16

  • 1,000 installations! 😀
  • [Ticket] Postman will not shut down if it can’t find OpenSSL. It will just display a warning to the user.

1.5.7 – 2015-03-14

  • [Ticket] renamed Zend framework classes to prevent errors with other plugins using the Zend framework
  • [Ticket] Added ajax error checks, especially for Error 502 : Bad Gateway (from WPEngine.com) when sending test e-mail
  • Multipart/Alternative was horribly broken, clearly no-one was using it. It’s working now, and Postman’s new Test Message is Multipart/Alternative. Thanks to Victor Hung of poofytoo for the use of his cartoon.
  • Add PHP library pre-requisite checks to Binder, Dashboard widget, Admin screen and Admin screen error messages.
  • Translated into Italian, thank-you Andrea Greco
  • Obfuscated e-mail address in Diagnostic Info
  • Fixed Wizard’s SMTP hostname guess for Apple addresses (icloud.com, me.com, mac.com)

1.5.5 – 2015-03-11

  • Added a Dashboard Widget to display Postman status
  • [Ticket] Added diagnostics check for iconv library
  • Moved the SMTP transcript to it’s own step in the Send Email Test
  • Moved 3rd-party plugin import to the Setup Wizard
  • [Ticket|Ticket] Stopped writing to error log if a language file can’t be found
  • Added the Http User Agent string to the diagnostics

1.5.4 – 2015-03-04 – the Birthday Release

  • [Ticket] Added support for the wp_mail filter – this adds compatibility with plugins like email-log
  • Better diagnostics – includes a port check on the currently configured host:port
  • Fixed a bug where multiple error messages at once overwrite each other
  • [Ticket] Fixed a bug in Sanitizer for cases where WordPress calls sanitize twice in a row – known WP bug

1.5.3 – 2015-02-28

  • Added a dedicated screen for Diagnostics (so that I can add more intensive, slower-running checks like DNS)
  • Fixed port-testing race condition bug in Postman Setup Wizard when using Gmail API Extension
  • Fix for error “Fatal error: Cannot redeclare class PostmanOAuthTokenInterface” when using Gmail API Extension
  • Checks to make sure that the hostname used for SMTP/OAuth 2.0 is one that is supported
  • Removed display_errors=On, Mr. Space Cadet here left it in the previous release by accident

1.5.1 – 2015-02-23

  • Bugs slipped through. In the Wizard, choosing port 465 was not hiding the authentication label. Worse, choosing port 587 was not showing the authentication buttons.
  • In the wizard, if no ports are available for use, the error message was not being displayed.

1.5 – 2015-02-22

  • [Ticket|Ticket] Added support for modular transports. The first external transport is the Postman Gmail Extension, which uses the Gmail API to send mail out on the HTTPS port, a convenient way around traditional TCP port blocks for Gmail users
  • [Ticket] Made my debug logging “less agressive” so that broken systems (those that pipe warning messages to STDOUT regardless of the WordPress WP_DEBUG_DISPLAY setting or PHP’s display_errors settings) will no longer experience the Port Test hanging during a check
  • Fixed a bug in the Setup Wizard where it would not use OAuth 2.0 on port 587
  • Fixed a bug where Postman refused to send mail with Password authentication and no encryption (who does that??)

1.4.1 – 2015-02-17

  • All text has been externalized in prep for I18N Internationalization and localization
  • Fixed a bug where the Setup Wizard would force OAuth 2.0 configuration, instead of falling back to Password, even if the required port was closed
  • Added more error checking, and more warning messages.
  • Translated into French, thank-you Etienne Provost

1.4 – 2015-02-15

  • Happy Valentine’s Day! Sending Yahoo email now supported with OAuth 2.0 authentication! If the Wizard detects that a Yahoo server has been entered, it automatically configures OAuth 2.0
  • First time users may choose to import settings from any of the Big Four WordPress SMTP plugins (five if you count Easy SMTP Mail, a clone of WP Mail SMTP): Easy WP SMTP, WP Mail Bank, WP Mail SMTP and WP SMTP
  • [Ticket] Suppressed warning messages generated by calls to fsockopen – they were causing the remote Ajax queries to hang
  • The wizard was resetting some settings by accident, namely Connection Timeout, Read Timeout and Reply-To
  • [Ticket] Found an environment where calls to error_log were being displayed in the HTML even after display_errors was disabled. Therefore, disabled error_log calls by default. The log may be re-enabled in Advanced Settings
  • The Bad, Postman! screen was messing with the Port Test Ajax call when fsockopen generated an error and debug level is set to E_ALL in php.ini. Therefore added a switch in the configuration “Show Error Screen” that is off by default. When it is off, Port Test works perfect but errors generate a WSOD. When it is on, errors are displayed in the “Bad, Postman!” screen but Port Test fails.
  • I heard that some hosts, like WPEngine, do not allow writing to the Http Session. Well that’s balls. I’ve modified the code to write to the database instead.

1.3.4 – 2015-02-11

  • 500 downloads and six 5-star ratings in only three weeks! Cool! 😎
  • Replaced the Google OAuth API with pure PHP code. No more unexpected Google API errors.
  • [Ticket] Enabled overriding of the timeouts in the configuration screen. If Postman is intermittently sending mail, doubling the TCP Read Timeout may help
  • Added the SMTP session transcript output when a test message fails to send.
  • Fixed the error: Class ‘Zend_Mail_Protocol_Smtp_Auth_Plain’ not found in /Postman/Postman-Mail/Zend-1.12.10/Mail/Transport/Smtp.php on line 198
  • Passwords in the database are now Base64-encoded so casual viewing of the database won’t reveal them
  • Fixed a couple minor database upgrade bugs: for new users who use Password Authentication, and for old users that don’t have an expiry token stored
  • Added a version shortcode, mostly for promotion of Postman on my own websites
  • Serveal minor tweaks to the user interface, including focus, style, validation, and enabling/disabling inputs where applicable

1.3.2 – 2015-02-10

  • [Ticket] Fixed the error: PHP Fatal error: Call to private PostmanAuthorizationToken::__construct() This occurs when upgrading from a pre-v1.0 version of Postman (when PostmanAuthorizationToken had a public constructor) to v1.0 or higher
  • [Ticket] Fixed the error PHP Fatal error: Class ‘Google_IO_Stream’ not found in /Postman/Postman-Auth/google-api-php-client-1.1.2/src/Google/Client.php on line 600 by including Google/IO/Stream.php
  • Postman now has a modest fatal error screen, rather than a dreaded white screen of death

1.3 – 2015-02-09

  • Sending Hotmail/Windows Live/Outlook.com email now supported with OAuth 2.0 authentication! If Wizard detects that a Hotmail server has been entered, it automatically configures OAuth 2.0.
  • Separated Authentication input from Encryption input for finer configuration control
  • Added additional authentication types: plain and CRAM-MD5. ‘basic’ became ‘login’
  • Added Ajax to manual config and wizard screens to allow dynamic OAuth2 redirect url + help text changes in response to hostname changes
  • Removed ‘Allow Plugin to Override Sender’ user input
  • Added Online Support link in menu
  • Clarified text in ‘Run a Port Test’ so people won’t continue to ask me about connection problems (hopefully)

1.2 – 2015-02-04

  • Support for Sender Name and Reply-To. Turns out Google no longer honours the MUA Return-Path header due to Spam. Makes sense, so I’ve decided not to add a Return-Path field to Postman’s configuration.
  • Support for WordPress filters wp_mail_from and wp_mail_from_name
  • Disable stats-keeping for email sent by the test function
  • Minor tweaks to the Wizard to support WordPress v3.9

1.1.1 – 2015-02-03

  • [Ticket] Fixed a bug I introduced in 1.1. Thanks to user derrey for catching this one. Zend_Mail crashes when attempting to throw an exception when the ‘from’ standard header was added as a header : “Zend_Mail_Exception code=0 message=Cannot set standard header from addHeader()”

1.1 – 2015-02-03

  • [Ticket] Added support for international characters (the WordPress default is UTF-8) which can be specified with headers or the wp_mail_charset filter
  • Added support for multi-part content type which can be specified with headers or the wp_mail_content_type filter

1.0 – 2015-02-02

  • Overhaul of the UI – A navigation pane is shown at the top of each page and each major function has been separated into its own screen
  • Postman now supports sending with basic auth and no auth just like the other SMTP plugins
  • Added a Port Test function so users can have peace of mind whether the plugin is failing (never!) or whether the host has firewalled them
  • [Ticket] Now supports email headers, such as a text/html content-type
  • Now supports email attachments
  • Added a warning if the user has configured OAuth but not requested permission from Google
  • Added a warning if the user is using Google with Basic auth (or worse) and a suggestion to enable OAuth 2.0
  • Recording of successful/failure tally

0.2.7 – 2015-01-29

  • Fixed error: “Undefined variable: authorizationToken” was preventing mail delivery outside of the admin screen.
  • Fixed warning message that Postman couldn’t bind to wp_mail immediately after Activation
  • Added prerequisite checks to make sure the PHP environment can handle Postman
  • Moved the screenshots and icons out of /trunk and into /assets

0.2.6 – 2015-01-28

  • [Ticket] Fixed “Configure and Authorize the plugin” missing the link address. Thanks to user kaorw for catching ths one.
  • [Ticket] Fixed “Warning: Missing argument 2 for update_option()”. Thanks to user kaorw for catching ths one. Fixed by calling delete_option instead of update_option().
  • [Ticket] Fixed “Fatal error: Call to undefined function str_getcsv()”. Thanks to user micb for catching ths one. This function is not available before PHP 5.3. Fixed by replacing str_getdsv() with custom implementation.

0.2.5 – 2015-01-27

  • [Ticket] Removed the namespace for users with older version of PHP
  • Changed the Postman Redirect URI (now includes a trailing ?page=postman) – this means Client ID’s from 0.2.4 or earlier MUST be updated with the new Redirect URI or re-created from scratch.

0.2.4 – 2015-01-25

  • Fixed issues on servers where the plugin is installed as a symbolic link.
  • Better error handling/debugging with php logging and assertions.

0.2.1 – 2015-01-23

  • Fixed an environment-specific error that prevented Postman reloading the setting screen after sending a test email

0.2 – 2015-01-20

  • wp_mail() accepts multiple recipients (array and string)
  • display a warning to the user if another plugin is preventing Postman from overriding wp_mail
  • paired down the external libraries to only what was required – from 3,700 files to just 75
  • default Gmail port corrected to 465 – previously 465 was hardcoded but 587 was saved to the database
  • Added ‘Delete All Data’ button to erase the stored tokens
  • OpenShift production problem: This environment didn’t like the callback and there were possibly invalid characters in the source script

0.1 – 2015-01-19

  • First release. Happy Fig Newton Day! It was a grueling week-end, studying PHP and OAuth and Googling like a Boss, but it’s done and it works!