Nick’s Review of Mysmtp Vs Greenarrow

Speed Considerations

Email delivery speed is an important factor to consider when choosing an email software solution. In order to determine the speed of GreenArrow, a benchmarking test can be conducted. The test involves delivering messages to a dummy SMTP service using a default GreenArrow configuration.

A pre-defined list of 10,000 email addresses can be used for the test. Alternatively, users can generate their own test list using addresses at subdomains of discardallmail.drh.net. The test list should be formatted using “\n” for line breaks.

To conduct the test, GreenArrow includes an SMTP sink service that allows for speed testing. The sink service accepts and discards all messages delivered to 127.0.0.1 on port 226. It also has the capability to simulate network latency, deferrals, and bounces for the SMTP, QMQP, and HTTP injection methods.

To install and configure GreenArrow Sink on a server that is not running GreenArrow, the executable file greenarrow-go should be copied from an up-to-date copy of GreenArrow to the desired server. The executable file can be placed in /usr/local/bin/greenarrow-sink. A launcher script can then be created with the necessary parameters for the test. The script should specify the IP addresses and port number on which the sink will listen, the maximum pause duration, and the server name, among other parameters. The script should be saved as greenarrow-sink-wrapper.

A systemd service entry should also be created for the sink service. The service entry should specify the description, user, executable path, and restart behavior. The service can then be enabled and started using systemctl commands.

Once GreenArrow Sink is installed and configured, the speed test can be conducted using the hvmail_speed_test command. This command allows users to specify various parameters such as the host, port, speed, sender, recipient, mail class, message file, and injection protocol. The command can be used to inject messages as fast as possible or at a specified speed. The current statistics on injection speed will be printed during the test.

Some of the parameters that can be specified include the host address, port number, speed of messages injected per second or per hour, envelope sender address, envelope recipient, mail class, message file, injection protocol (SMTP, QMQP, HTTP, or direct), number of messages to send or time to send, and additional parameters for HTTP injection.

The hvmail_speed_test command also supports realistic subdomain sinks, which allow for the delivery of messages to generated domains using a realistic distribution. This can be useful for testing email delivery patterns.

It is recommended to install GreenArrow Sink and conduct benchmarking tests to determine the speed and performance of GreenArrow. This will help users make an informed decision when choosing an email software solution.

In conclusion, speed is an important factor to consider when evaluating email software solutions. GreenArrow offers features such as benchmarking tests, SMTP sink services, and the hvmail_speed_test command to help users assess the speed and performance of their email delivery. Conducting speed tests using GreenArrow Sink can provide valuable insights into the capabilities of the software and assist in making an informed decision.

Tina’s Review of Mysmtp Vs Greenarrow

Domain Policies Deny/Allow newbie confusion

There seems to be some confusion regarding the Domain Policies feature in the MailWizz self-hosted email marketing software. A user named avidns posted a question on the MailWizz forum asking about the purpose of both the allow and deny options in the Domain Policies for a delivery server. They wondered why they would need both options and if they could simply delete a denied domain if they eventually wanted to allow it. Another user named ghimes responded, mentioning that there are some use cases for both allow and deny options and shared a screenshot explaining them.

In response to the thread, avidns later realized that they may want to allow a domain temporarily and then deny it again if there are any issues, instead of having to recreate the whole domain policy.

After some time, another user named ridgerunner777 joined the discussion and shared their own question and situation. They mentioned that they have multiple installations and domain brands, with around 200,000 active lists on each. They explained that they want to send different emails to different email service providers (ESPs) based on their performance. They mentioned using Mandrill for Gmail, smtp.com for Yahoo, Green Arrow for Microsoft domains, and Spark Post with specific criteria for other domains. They asked if this setup would work effectively and in real-time, ensuring that subscribers receive their emails without delay.

They further clarified their question by discussing the use of multiple sending servers, domain policies, probabilities, and rate/quota limits. They wanted to know if MailWizz could handle this setup and if it would switch to the next sending server if the previous one couldn’t send for any reason. They also questioned if this processing would happen ahead of time or on-the-fly, depending on the email type.

There were no direct responses to ridgerunner777’s question, so they bumped the thread in the hopes of getting an answer from other users. Unfortunately, the summary does not provide any further information or resolution to the question.

In conclusion, the forum thread revolves around the confusion and queries regarding the Domain Policies feature in the MailWizz software. Users are seeking clarity on why both allow and deny options are necessary, how to effectively use multiple sending servers with domain policies, and if MailWizz can handle these setups in real-time. Unfortunately, the thread does not provide complete answers to these questions.

Steve’s Review of Mysmtp Vs Greenarrow

In a recent forum post, a user named ridgerunner777 asked for advice on how to maintain consistent delivery when using multiple email servers. The user explained that their company has multiple ESP (email service provider) accounts but none of them have all the features they need. They have four delivery servers – Green Arrow, my.smtp.com, SendGrid, and Spark Post – and they want to split their email sending evenly across these servers. They have a total list size of 100,000 subscribers and want to send 25% of their emails through each server.

The user emphasized the importance of maintaining consistent delivery for each set of domains they mail to. They have a list of the top 10 TLDs (top-level domains) they mail to, with Gmail and Yahoo/Ymail making up the majority of their list. They want to determine which delivery server performs best with each domain group and route emails accordingly.

The user also asked how to ensure that each individual contact is consistently sent from the same server they were initially sent from. They don’t want contacts to be randomly assigned to different servers. For example, if Jack was initially sent from Green Arrow, they want all future emails to Jack to be sent from Green Arrow as well. The user expressed a desire to add a custom tag to each contact to track which server they were associated with, but they couldn’t find a way to do that.

In addition, the user mentioned that they wanted to track engagement metrics, such as opens and clicks, and tie them to the specific delivery server. They wanted to be able to update or modify tags based on engagement behavior. For example, if a contact wasn’t opening emails from one server, they wanted to change the tag to try sending emails from a different server to increase engagement.

In response to the user’s question, another forum member named twisted1919 explained that the only way to achieve this level of control is to allow delivery server selection in the campaign setup step. The user would need to segment their list properly and consistently send to the same segments with the same servers. This way, each contact remains associated with the server they were initially assigned to.

The user thanked twisted1919 for the response and mentioned that they would try implementing this solution and report back on their success.

In summary, the user was seeking advice on maintaining consistent delivery when using multiple email servers. They wanted to evenly split their email sending across four delivery servers and ensure that each contact remained associated with the server they were initially sent from. They also wanted to track engagement behavior and modify tags based on that behavior. The solution provided was to allow delivery server selection in the campaign setup and use proper list segmentation to send to the same segments with the same servers.

Rick’s Review of Mysmtp Vs Greenarrow

In this blog post, we will be discussing the comparison between mySMTP and GreenArrow, two popular private SMTP connectors offered by Ongage.

Before diving into the details, let’s understand what a private SMTP connector is. A private SMTP connector allows you to connect to your own on-premise or cloud SMTP server and use it to send emails through the Ongage platform. This gives you more control over your email delivery and allows you to leverage the power and flexibility of your own SMTP server.

Let’s start by looking at the compatibility of the two connectors. mySMTP, offered by Ongage, is compatible with several on-premise MTAs (Mail Transfer Agents) including PowerMTA, GreenArrow, MailerQ, and MDaemon. On the other hand, GreenArrow is a standalone on-premise MTA developed by DRH Internet. Both connectors offer robust features and are widely used by email marketers.

For those considering mySMTP, it is important to note that it supports connecting to various cloud SMTPs as well. This means that you can use popular cloud SMTP relays such as SMTPeter, which is made and maintained by Copernica, along with MailerQ, or other generic cloud SMTP servers.

Now, let’s discuss the setup process for each connector. To connect to your own on-premise MTA using mySMTP, you need to contact your account manager to open a private SMTP connection. Ongage support will then provide you with the necessary documentation to set up the connection. You will need credentials such as the SMTP host, port, username, password, authentication type, and TLS settings.

GreenArrow, being an on-premise MTA, requires you to install and configure the software on your own server. This may require technical expertise and resources to set up and maintain the server. However, once properly configured, GreenArrow offers complete control over your email delivery process.

Now, let’s explore the bounce handling options for these connectors. Ongage provides two options for setting up bounce handling with a private SMTP connection. The first option is to set up a bounce domain as described in the ESP setup page of the private SMTP. Ongage will handle the bounce processing for you in this case. The second option is to update bounces and complaints via API calls from your private SMTP back to Ongage. This option requires some development effort but allows you to have more control over how bounces and complaints are handled.

If you choose to use the second option, you will need to use the Ongage X-JOB header in your API calls. This header contains the child campaign ID, which is necessary to associate the status changes with the campaign it happened in.

Additionally, the default number of parallel connections used by Ongage to communicate with your SMTP server is 30. This number can be adjusted based on the capacity of your server. You can work with Ongage support to determine the optimal number of parallel connections for your setup.

PowerMTA, one of the supported on-premise MTAs, offers a configuration parameter called “log-connection” that can be used to enable or disable logging of connection data. This can be useful for tracking the number of messages sent on each connection.

For those who want more control over bounce handling and want to set their own Return-Path email and domain, Ongage offers an option to set a custom Return-Path header in the Private SMTP connection settings. This allows you to manage bounce handling on your end and override the default Return-Path set by Ongage.

In conclusion, both mySMTP and GreenArrow are powerful private SMTP connectors offered by Ongage. The choice between the two depends on your specific requirements and preferences. If you are looking for a cloud-based solution that supports various MTAs, mySMTP is a great choice. On the other hand, if you prefer an on-premise solution with complete control over your email delivery, GreenArrow is worth considering.

Beth’s Review of Mysmtp Vs Greenarrow

Today, I want to talk about two email marketing software options: mySMTP and GreenArrow. Both of these options offer in-house bulk email systems that can help you improve your email marketing campaigns. Let’s dive into the details.

mySMTP is an email service provider that allows you to send emails via your own in-house mail server or through Amazon SES. One of the main benefits of using mySMTP is that it eliminates the need to pay a per-email fee, which can save you money in the long run. Additionally, mySMTP allows you to keep your member data in-house, meaning you can connect to a variety of CRM databases without sharing your data. This level of data security is crucial for many businesses. With a customer base of over 7,500 businesses, mySMTP has proven to be a reliable option for email marketers.

On the other hand, GreenArrow also offers an in-house bulk email sender that promises better delivery rates, lower costs, and no locking. With many email service providers, you are not in control of your business. If your account is suspended or terminated, you can lose your entire list of subscribers overnight. This can be devastating for businesses that rely on their email lists for income. GreenArrow solves this problem by providing you with full control over your email marketing. Your account will never be deleted without notice, giving you peace of mind and the ability to maintain a clean reputation with blacklists.

GreenArrow also offers features such as full control over your data, AES encryption for secure data storage, and automatic data backup. With GreenArrow, you can access your data from anywhere, making it convenient for businesses with multiple locations or remote teams. If you’re an agency managing multiple clients, GreenArrow allows you to create multiple users and workplaces, ensuring that each user has their own unique data. Additionally, GreenArrow integrates with email analytics platforms such as G-Lock Email Analytics, Google Analytics, and Piwik Analytics, providing you with valuable insights into your email campaigns.

When it comes to contact management, both mySMTP and GreenArrow offer flexible options. With mySMTP, you can create unlimited contact groups and links to CRM databases. The software allows for super fast import of contacts from CSV files or databases, making it easy to manage and customize your contact records. Similarly, GreenArrow offers unlimited contact groups and the ability to import contacts from various sources such as CSV files, MS Access, and MySQL databases. Integration with CRM databases is also possible with GreenArrow, allowing you to connect to any ODBC compatible database on your network.

In terms of email sending capabilities, both mySMTP and GreenArrow offer fast and secure sending options. mySMTP supports numerous SMTP connections, allowing you to send 1 million emails in just 1 hour. It also integrates with Amazon SES API, which can be useful if you have restrictions with your ISP SMTP server. GreenArrow, on the other hand, offers smart email throttling and a campaign scheduler that allows you to schedule your email campaigns for any date or time. Both options provide features for automated emails, list segmentation, and inbox placement testing.

When it comes to message design, mySMTP and GreenArrow both offer customizable options. mySMTP includes a fully-featured message editor that allows you to create HTML emails directly in the program. You can also create your own layout using standalone HTML editors or download beautiful HTML email templates from their store. GreenArrow offers a drag-and-drop message editor that makes designing responsive emails quick and easy. They also provide a store of responsive HTML email templates to help you create professional email marketing messages.

In conclusion, both mySMTP and GreenArrow offer strong in-house bulk email systems that can benefit your email marketing campaigns. While mySMTP focuses on reducing costs and keeping your member data in-house, GreenArrow prioritizes full control over your email marketing and data security. Both options provide flexible contact management, fast and secure sending capabilities, and customizable message design features. Ultimately, the choice between mySMTP and GreenArrow depends on your specific needs and preferences.