Send vs wL

Did you find this plugin helpful? Please consider leaving a 5-star review. Note: This is a forked version of the now unsupported wpMandrill plugin. The notes below are copied over from the original plugin and will be updated as relevant updates become available. Please help by contributing to the GitHub repository Send Emails With Mandrill on GitHub This plugin uses Mandrill API to send outgoing emails, with or without attachments, from your WordPress installation. It replaces the wp_mail function included with WordPress. Emails are tracked and automatically tagged for statistics within the Mandrill Dashboard. You can also add general tags to every email sent, as well as particular tags based on selected emails defined by your requirements. You can also use your own templates that have been added to your MailChimp account and shared with your Mandrill account. There are a few levels of integrations between your WordPress installation and this plugin: The simplest option: Install it, configure it, and Send Emails with Mandrill will start sending your emails through Mandrill. If you need to fine tune certain emails, you can change any email by creating a filter for the mandrill_payload hook. For further customization, we’ve exposed a function that allows you to send emails from within your plugins, instead of the regular wp_mail function: wpMandrill::mail Enable the connection by entering a valid API key in the settings page or adding the line define('SEWM_API_KEY', '{YOUR_API_KEY}') your site’s wp-config.php file. Spanish translation available. Request If you find that a part of this plugin isn’t working, please don’t simply click the WordPress “It’s broken” button. Let us know what’s broken in its support forum so we can make it better. Our mind-reading device still needs some tweaking. Localizations Send Emails with Mandrill is currently available in the following languages: Albanian (Shqip) Arabic (العربية) Armenian (Հայերեն) Basque (Euskara) Bengali (বাংলা) Bulgarian (Български) Catalan (Català) Chinese Simplified (简体中文) Croatian (Hrvatski) Czech (Čeština) Danish (Dansk) Dutch (Nederlands) Estonian (Eesti) Finnish (Suomi) French (Français) Galician (Galego) Georgian (ქართული) German (Deutsch) Greek (Ελληνικά) Hebrew (עברית) Hindi (हिन्दी) Hungarian (Magyar) Indonesian (Bahasa Indonesia) Irish (Gaeilge) Italian (Italiano) Japanese (日本語) Korean (한국어) Latvian (Latviešu) Lithuanian (Lietuvių) Macedonian (Македонски) Norwegian (Norsk) Persian (فارسی) Persian – Afghanistan (دری) Polish (Polski) Portuguese – Brazil (Português do Brasil) Portuguese – Portugal (Português) Romanian (Română) Russian (Русский) Serbian (Српски) Slovak (Slovenčina) Slovenian (Slovenščina) Spanish (Español) Swedish (Svenska) Tamil (தமிழ்) Thai (ไทย) Turkish (Türkçe) Ukrainian (Українська) Urdu (اردو) Vietnamese (Tiếng Việt) Welsh (Cymraeg) Known Issues Daily statistics will show data for the first 20 senders (emails) registered. Daily statistics will show data for the first 40 tags registered. If your account has more than 20 senders registered or more than 40 tags used, the detailed daily statisticas might show incompleted data.

wL Email Encrypter scans pages, articles, comments or RSS feeds for email addresses and encrypts them using JavaScript or replacing the @ signs with your own text like [at]. This allows bots and other email-collectors do not recognize and save the emails. A visitor who has not activated JavaScript, gets displayed a userdefined message about it. If an user is logged in, the emails won’t be encrypted. The protect method can be set separately for posts, comments and rss feeds. For example, RSS Feeds should not include JavaScript, so there should prefer the @ sign to be replaced. wL Email Encrypter also recognizes with mailto: email addresses linked with subject information and others, and protect this information also. There is a meta box for page-specific settings in the administration, in which a specific protection can be selected or disabled. Take a look at the screenshots to find out more.