Gammadyne Mailer Support

Sending Mail

• The most common cause, by far, is a spam filter is blocking the email.  Try sending a very simple text email.  The content of the email may be causing the recipient's mail server to discard it.
• Try disabling all anti-virus and Internet security programs, like Norton Security Suite.  These often interfere with email delivery.
• If using Direct Delivery, use the "Direct Delivery Possible?" tool (on the Test menu) to determine if there is a PTR record for your computer's IP address.  This will also report if the IP address is on the Policy Blacklist (PBL).  These two issues prevent Direct Delivery from working.
• Look at the Send Log to see if any errors are mentioned.
• Use the "Check Blacklisting" tool to determine if your IP address, or the SMTP server's IP address, is blacklisted.
• Some SMTP servers are picky about the email address in the "From:" header.  If the "From" address is not a registered user, they will refuse to pass on your messages.  However, there is usually an error reported in this case.
• Some mail servers will discard messages if too many arrive from the same source too fast.  On the Send/Throttles branch, check the Universal Domain Throttle box.  Don't do more than 1 email every 4 seconds.
• Try disabling the "Recycle Connection" feature (on the Delivery branch).
• Make sure you are not using the "Expiration Date" setting on the Headers branch.  Even if the expiration date is correct, the recipient may not have the correct date/time on their computer's clock.
• Try sending the same message from another program, like an email client.  If it does not go through, then the problem is not specific to Gammadyne Mailer.  Either the SMTP server is not relaying the email, or it is being blocked somewhere.
• Try sending a test message using Direct Delivery.  If it arrives, then the problem is with the relaying email server.  It could be flooded with email, compromised by malware, or the victim of a Reverse-NDR attack.
• Microsoft 365 is infamous for just discarding outgoing emails without delivering them, and without notice.  It's the only mail server that we know of that performs junk mail filtering on outgoing email.  For this reason, you may find it unsuitable for email marketing.
• Wait a little while - not all email is instantaneous.  Some mail servers employ "greylisting", a technique where they will reject an email until it is retried after an hour.  Gammadyne Mailer's "Delayed Retry" feature (on the Delivery branch) is designed to get around this.

If no errors are reported in the log, that means Gammadyne Mailer is doing its job and delivering the email to your SMTP server.  What happens to it after that is outside Gammadyne Mailer's control.  We are only able to troubleshoot problems with delivery to the SMTP server.  We have no knowledge of what your mail server does with the email, and therefore we have no information with which to solve the problem.

If an error is reported in the log, please forward a copy of the log to support at gammadyne dot com for further review.




We have a complete article about this here.

• Look at the Send Log - it lists why each recipient is excluded.  If you are using the Database Clause Table, check the "Internally Process Clause Table" box so that Gammadyne Mailer can process and log the clauses (otherwise the database itself will silently apply the clauses).
• One of the database clauses excludes rows based on a string or date.  If the column contains a null value, the clause will fail for that row.  This even occurs when the clause uses the <> operator.  This is a limitation of the SQL standard and not Gammadyne Mailer.
• There is a clause in the Clause Table that is excluding the rows.  Try checking the "Ignore" column to see if a clause is the problem.  Make sure string values are not enclosed in quotes.
• An incorrect Recipient Column was chosen.  This column must contain an email address.  The address cannot be inside quotes.
• There are duplicate recipient email addresses and the "Eliminate duplicate recipients" box is checked.
• Check the recipient's email address carefully.  Some databases, like Access, will only show the first line of the cell.  If the cell contains more lines, they will not be visible.  Make sure the email address is only one line and has exactly one "@" character.
• Recipients are being excluded based on the contents of the Exclusions branch.
• If using a database (especially Excel), try setting the Cursor Type (on the Database/Setup branch) to "Static" or "Forward Only".

Error 4510 occurs when DNS fails to provide the mail server for the SMTP server.  Verify all settings on the Servers/DNS branch.  Use the "Test DNS Servers" tool to verify that DNS is working.  Verify that the name of the SMTP server is correct.  Try identifying the SMTP server by its IP address instead of its name.

Please note that the DNS branch is hidden unless you uncheck "Hide Advanced Settings" on the Options menu.




Possible causes:

• When using the Direct Delivery feature, use the "Direct Delivery Possible?" tool (on the Test menu) to make sure that Direct Delivery is allowed from your computer.  AOL blocks all email originating from a dynamic IP address/residential gateway.  Generally, email must be relayed through a web server with a static IP address.
• The "From:" header must contain a legal email address.
• The "To:" header must contain the same email address as the recipient.  On the Headers branch, leave the "To:" box unchecked.  Please note that the "To:" box is hidden if "Hide Advanced Settings" on the Options menu is checked.
• The HTML Body cannot contain "hex-encoded URL's".  In other words, any hyperlink in the HTML cannot contain a URL that has hex-encoded characters (such as "%20", which represents a space).
• It is very important to keep the mailing list clean of bad AOL addresses.  If the mailing contains more than 10% bad addresses, AOL will start to block all emails.  Hence, after each mailing, it is important to remove all bounced email addresses from the mailing list.  If the number of bad addresses is unknown, it would be prudent to throttle the delivery to AOL.  Also, if AOL cannot deliver bounce-backs, this too will incur their wrath.
• AOL has blacklisted the computer's IP address or the SMTP server's IP address.
• AOL has been known to discard messages if too many arrive from the same source too fast.  On the Send/Throttles branch, click the "Default" button.

We also recommend:

• Review AOL's official rules.
• Sign up for AOL's Feedback Loop.
• Follow our general guidelines.
• Call AOL or open tickets with the AOL Postmaster Group (the number is 703-265-4670) so that they can work with you.  They'll need to know what your sending IP address is, which is reported by Gammadyne Mailer's "Check PTR Record" tool.

• Double check the settings on the Throttling branch.
• Send an email with another program.  If it is slow, the problem is with the SMTP server or the Internet connection itself.  Your ISP may be limiting the bandwidth on port 25 to prevent users from sending large amounts of spam.
• Try disabling all anti-virus and Internet security programs, like Norton Security Suite.  These often interfere with email delivery.
• Some viruses infect the operating system's Internet DLL's.  It would be prudent to check the system for malware.
• Terminate other applications that use Internet bandwidth.
• Reduce the size of the message, its attachments, and embedded images.  Email sending time correlates directly with email size.
• The mail server could be suffering from a Reverse-NDR Attack.
• Look at the Send Log's performance statistics to see how much time was spent waiting on the database.  If the database takes a lot of time, the database file may be corrupt.  Many databases have a "Compact and repair database" tool that should be tried.  If the database is located on the network, try using a local copy to determine if the network is causing the slowdown.
• Disable the "Eliminate duplicate recipients" feature on the "Filtering" branch if there are no duplicates (for a small performance improvement).
• Uncheck the "Record send log" option on the "Logging" branch (for a small performance improvement).
• Get a faster Internet connection.

If using Direct Delivery:

• Use the "Test DNS Server" tool to check how fast the DNS server is responding.
• Disable the "Retry direct delivery failures" option on the "Delivery" branch.
• Increase the number of Threads on the "Send" branch.
• Please note that if using the "Delayed Retry" feature, this will often skew the performance statistics.  Throughput may be much better than is reported.

If not using Direct Delivery:

• Look at the log's performance statistics to see if the data sending speed is much lower than the speed of the Internet connection.  If so, this indicates that the SMTP server is the bottleneck.
• Enable the "Recycle Connection" feature on the "Delivery" branch.
• If possible, specify more than one SMTP server on the "SMTP" branch.

Gammadyne Mailer can rotate through multiple SMTP servers while sending email.  Use the following procedure to configure a project for this:

1. Click on the "Servers/SMTP" branch.
2. Check the "Use Project SMTP Settings" box.
3. Click the "Add" button at the bottom of the table.
4. Enter the server name or IP address in the first column.
5. Set the Authentication column to "Login", then specify the user name and password.
6. If you need to limit the delivery rate to the mail server, fill in the Throttle Count and Throttle Period columns.  For example, to send only 100 emails to the server per hour, enter 100 for the Throttle Count and 3600 for the Throttle Period (or better yet 1 every 36).
7. Repeat steps 3 through 6 for each additional SMTP server.
8. On the Headers branch, it is recommended that you check the "Same as SMTP User" box.  This is required by some mail servers.

When a server becomes overloaded, sending mail to it will be slower.  The server may even begin to refuse connections (Winsock error 10061).

Solutions:

• Reduce the number of Threads on the "Send" branch.
• Use the Throttle feature in the SMTP Server Table.
• Enable the "Universal Domain Throttle" feature on the Throttles branch.
• Use the "Pulse" feature on the Throttles branch.

Gammadyne Mailer does not have an arbitrary limit on the number of recipients.  When using a database, only one record is in memory at a time.  For lists that are in a text file, Gammadyne Mailer will scan through the file one line at a time.  These techniques use very little memory and permit absolutely huge mailing lists.

Notes:

• If the list has more than 1000 recipients, uncheck "Preview Emails" on the Send branch.
• There is no limit to the message size, although many SMTP servers have trouble with messages over 35 MB.
• Gammadyne Mailer is not intended for spamming and contains no features for hiding your identity.  Please send email only to customers, acquaintances, and opt-ins.

At the time that Gammadyne Mailer delivers the email to the SMTP server, the server will happily accept it and try to deliver it to the final destination later.  From Gammadyne Mailer's point of view, there was no error.  When the SMTP server fails to deliver the email, it will return a bounce-back message.

Even when using Direct Delivery, the recipient's mail server may accept the email, producing no immediate errors, then later send a bounce-back.  No email program can prevent this.




Yes, use the "Direct Delivery" option on the "Send/Delivery" branch.  When checked, each message is delivered directly to its recipient's mail server.

For more information, please refer to this article.




Error 3007 occurs when a connection cannot be made with the SMTP server.  Check the following:

• Make sure the SMTP server name is correct.
• Make sure the SMTP server's port number is correct.  This is usually 25, but could also be 465 or 587.
• Make sure the user name and password are correct.  Sometimes these are identical to your POP3/IMAP4 account.  Sometimes the SMTP server has a separate user name and password.  It may be necessary to confirm the correct details with the mail server's administrator.
• To eliminate DNS as the culprit, specify the IP address of the SMTP server instead of its name.
• Try the following settings in the "SMTP Encryption" field: Disabled, Optional
• Make sure no firewall is blocking Gammadyne Mailer.
• Disable all anti-virus and Internet security software that are running in the background, especially those that scan outgoing email.
• Make sure that your ISP is not blocking port 25.  Many ISP's do this to prevent their users from sending bulk email.
• If the problem is intermittent, try reducing the number of Threads (on the Send branch).  On Windows XP, no more than 10 threads should be used because of a limit imposed by Microsoft.  Another possibility is that the SMTP server is simply too overwhelmed with connections to respond.
• Check to see if another program can send email using the same settings.
• For Gmail, try setting SMTP Authentication to "OAuth-Gmail" (on the SMTP branch).
• For Microsoft, try setting SMTP Authentication to "OAuth-Microsoft".

Cause:  An operation on a socket was not performed because the system lacked sufficient buffer space or because a queue was full.  This error indicates a shortage of resources on the system.  It can occur if too many applications are running.

Solution:  Reboot the machine.  Reduce the number of Threads on the "Send" branch.  Disable all anti-virus and Internet security software that is running.




The server is actively refusing the connection request from your computer.

Solutions:

• Make sure that the server's SMTP service is running.
• Make sure that port 25 is not blocked by a firewall.
• If the error is intermittent, reduce the number of Threads on the "Send" branch.  Consider using the Throttle feature in the SMTP Server Table on the "SMTP" branch.
• Disable all anti-virus and Internet security software that is running.
• Make sure that your ISP is not blocking port 25.  Many ISP's do this to prevent their users from sending bulk email.
• Configure the mail server to keep undeliverables in the mail queue for no more than an hour and a half.
• Delete all email in the mail server's mail queue.  Some email could be "stuck" there.
• Use the "Direct Delivery" feature (on the "Delivery" branch) to bypass the SMTP server altogether.
• It could be that the server is too overwhelmed to accept new connections.
• The mail server could be suffering from a Reverse-NDR Attack.
• Reboot the mail server.
• Wait a bit and try again.

Potential problems:

• Use the "Direct Delivery Possible?" tool (on the Test menu) to verify that Direct Delivery is allowed.
• Your ISP may be blocking port 25.  Ask them if this is the case.
• Make sure the DNS settings are correct.  Use the "Test DNS Servers" tool.
• The "SMTP Timeout" setting (on the "SMTP" branch) should be at least 600 seconds.
• The "DNS Timeout" setting (on the "DNS" branch) should be at least 30 seconds.
• Disable all anti-virus and Internet security software that is running.

If you see this error, chances are, the whole Internet connection is down.  Disconnect the power from the router and cable modem, wait 15 seconds, then power them back up.  It may also be necessary to reboot the computer.

Error 10051 is indicative of an improperly configured network.  The official explanation for this error code is as follows:

The local network system can generate this error if there is no default route configured.  Typically though, Winsock generates this error when it receives a "host unreachable" ICMP message from a router.  The ICMP message means that a router cannot forward the IP datagram, possibly because it did not get a response to an ARP request (which might mean the destination host is down).




Error 4570 occurs when a mail server rejects the Sender.  The Sender is configured on Gammadyne Mailer's Headers branch.

• Some mail servers will only transport mail that originates from or goes to one of its users.  Hence, if you are using the mail server mail.foo.com to relay email, then the Sender needs to be part of the foo.com domain, such as bar@foo.com.
• The SMTP server may require authentication.  On the Servers/SMTP branch, set SMTP Authentication to "Login".  Specify the user name and password.
• The SMTP server may limit the number of emails that can be relayed.  This is common when using a third-party's mail server.

In order for Gammadyne Mailer's activation status to be recognized properly, the user's security settings must permit access to the following two registry keys:

HKLM\Software\Microsoft\Current Version
HKLM\Software\Microsoft\Current Version\Uninstall\Gammadyne Mailer

Also, the user needs to have access rights to the folder where GM is installed, which is typically "c:\Program Files (x86)\Gammadyne Mailer".




Yes, please refer to this article.




Please read this article.




Yes, Amazon now supports SMTP email delivery just like a normal mail server.  Gammadyne Mailer can send through any SMTP server.  See here for details.

Try the following settings:

SMTP Server Name: email-smtp.us-east-1.amazonaws.com
Port: 465
SMTP Authentication: Login
SMTP Encryption: Required

For more information about obtaining the required user name and password, go here.





The following methods allow a Send Operation to be resumed from where it was interrupted:

Method #1:  Launch the "Resume Send" tool (on the Tools menu).
This is the simplest method, but it only works if the user aborted the Send Operation, and the project is still open or was saved.  The tool will tell you if it can automatically resume.  If not, you will need to resort to another method.


Method #2:  Storing the send date in a database column.
If using a database, use the "Store successful send date" feature to store the date and time of the last successfully sent email in a database column (create a new column for Gammadyne Mailer to use).  When an operation needs to be resumed, check the "Only send when before" box and enter the date and time when the original operation was started.  These settings are located on the Database/Setup branch.


Method #3:  Restarting the operation at a particular recipient.
If you can see from the Send Log approximately where in the mailing list the last recipient was, the "Begin with recipient" feature can be used.  Simply check this box (located on the Recipients/Filtering branch) and enter the email address of the last recipient.  The Send Operation will skip all recipients until the specified recipient is encountered.  Then the operation will proceed as normal.

Using this method, a small number of recipients may receive the email twice due to multi-threading.  Also, if you begin with a recipient whose email address appears in the mailing list more than once, then a large portion of the mailing list could receive the email twice.


Method #4:  Storing successes in a file.
Before starting a Send Operation, check the "Append successes to file" option on the Logging branch.  Enter the path and filename of a file, and make sure that the file is empty.  When an email is successfully sent, the recipient's email address will be appended to the file.

If the operation is interrupted, make a copy of the file and use the copy as an Exclusion File.  Then restart the Send Operation.  Any prior successes will be excluded by virtue of being located in the Exclusion File.  Be sure to delete the file and its copy when the operation is complete.


Method #5:  Storing successes into the Exclusion List.
Before starting a Send Operation, check the "Add successfully sent recipients to Exclusion List" option (on the Exclusions branch), and empty out the Exclusion List.  An interrupted Send Operation can simply be restarted, since any prior successes will be excluded by virtue of being located in the Exclusion List.

The weakness of this method is that it does not protect against power loss since the Exclusion List is only modified in-memory.  Only after the project is saved will the project file reflect the new Exclusion List.





This can happen when the server requires an SSL encrypted connection.  On the Servers/SMTP branch, change the "SMTP Encryption" setting to "Required".




Follow this procedure to disable scanning of outgoing email:

• Open Norton Internet Security.
• On the Options menu, click Norton AntiVirus.
• In the Norton AntiVirus Options window under Internet, click Email.
• Under What to scan, uncheck Scan outgoing email (Recommended).
• Click OK.
• On the Options menu click Norton Internet Security.
• On the Email tab, under Email scanning, uncheck Tray icon.
• Under Email scanning, uncheck Progress Indicator.
• Click ok.
• On the Options menu click Norton AntiSpam.
• On the left side of the window, under Email, click Filtering.
• Uncheck Use outgoing email to improve Norton AntiSpam filtering (recommended).
• Click OK.
• On the main Norton screen, disable Privacy Control.

Error 4640 indicates that the mail server did not respond properly after the message body was delivered.  The possible causes are:

• It is possible that the server has a restriction on the Sender or the From header (which are often, but not necessarily, the same).  The Sender and/or From header may need to be an email address that is local to the SMTP server.  Or sometimes, they may need to be identical to the SMTP user name.  The Sender is configured on the Headers branch.  The SMTP User Name is configured on the SMTP branch.
• The server may also disallow a Reply-To: header that differs from the SMTP user name.  We have seen Yahoo do this.
• The connection was broken.
• Too many emails have been sent in too short a time.  For example, Gmail has a limit of 100 emails per day.
• The email is too large.
• The server does not like the content of the email.
• Rarely: the recipient mailbox may be invalid.

Look in the Send Log.  Near the 4640 error, you may find a message that originates from the server.  This could explain exactly what it doesn't like.  Failing that, try using the "Simple Send" tool to send yourself a very simple email.  Experiment with the email content and the From: header.  If the relaying SMTP server does indeed have a restriction, only its administrator will be able to change the policy.



Winsock error 10053 usually indicates that a third party program is interfering with Gammadyne Mailer.  The program could be a firewall, anti-virus, or Internet security application.  It could also be a hardware device like a Dell SonicWALL.  Try disabling all such software, and try again.  It may also be possible to whitelist Gammadyne Mailer, or disable the software's email scanning feature.



When a connection is first made with a mail server, the mail server sends a one-line greeting message.  The first thing in the greeting is a status code.  If the status code is 400 or greater, then the server is indicating that it is not available to relay email.  Gammadyne Mailer reports this as error code 3009.

If you are using Direct Delivery, the most likely cause is that the computer's IP address is on the Spamhaus Policy Block List (PBL).  The PBL is a list of all IP addresses that are assigned a dynamic IP address, or are behind a residential gateway.  It may be possible to request removal from the PBL - ask your Internet Service Provider.  Use the "Direct Delivery Possible?" tool to determine if this is the problem.  The only other solution is to switch to Indirect Delivery (on the Delivery branch).

If you are using Indirect Delivery, you should verify that the SMTP server name and port number are correct.  Although unlikely, it is possible that the server is too busy to accept more email.  If the problem persists, it will be necessary to contact the mail server's administrator.

Database

Possible solutions:

• Make sure the Table Name is correct.
• Make sure all column names in the "Custom WHERE Clause" are correct.
• On the Database/Setup branch, try a different choice for the Cursor Type.
• Some databases permit invalid characters in a column name, even though such characters are illegal in SQL.  Column names should contain only letters, digits, and the underscore.
• Run the database's "Compact and repair database" tool (if present).
• In the ODBC Administrator, delete the system data source and recreate it.  Make sure the correct driver is chosen for the type of database being used.
• Make sure Primary Key has a unique value for each row of the table.

If no solution is forthcoming, you can send us a copy of the error message.




Gammadyne Mailer requires a result set that contains one recipient per row.  However, you can use the database to create a "View" (a.k.a. "Query") that joins the data into a single result set.  Then, specify the View's name for the Table Name.

If a View cannot be created, use the "Custom SELECT Statement" setting on the "Database" branch to create the database result set.

See also:
Help File > Table of Contents > Guides > Multiple Records Per Recipient
Help File > Table of Contents > G-Merge Functions > db_get()




Check the "Use Database" box.




Change the "SQL Date Format" setting on the Database/Setup branch and try it again.  There are only five possible choices; one of them should work.  Please note that you must uncheck "Hide Advanced Settings" on the Options menu for this setting to be visible.

If all types of database assignments fail, refer to the next FAQ.




If all database assignments fail to work right, check the following:

• Make sure that the Primary Key has a unique value for each row.
• Make sure that no script declares a G-Merge variable with the same name as the column.
• Make sure the Connection String does not contain "readonly=1".
• Make sure the database file does not have the "read only" file attribute set.
• Make sure the database file's security settings do not block any users from writing changes.

If only dates cannot be stored in the database, see the previous FAQ.

If no solution is forthcoming, please contact us.




Yes.  To use an Excel worksheet in Gammadyne Mailer, follow this procedure:

1. In Gammadyne Mailer, go to the Database branch.  Check "Use Database".
2. Check "Use Connection String".  Click the "Browse" button.
3. In the ODBC driver list, click on "Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)".  Click "OK".
4. The "ODBC Microsoft Excel Setup" window will appear.  Click on the "Select Workbook" button.
5. Select the Excel database file on your hard drive.  The file will have an ".xls" extension.  Click on the "OK" button.
6. Click on the "OK" button to exit the "ODBC Microsoft Excel Setup" window.

ODBC DRIVER
Because Gammadyne Mailer is a 32-bit application, it requires the 32-bit ODBC driver.  The 64-bit version of Office may not install the 32-bit driver, in which case you will not see the "Microsoft Excel Driver" mentioned in step 3.  You will have to download and install the 32-bit driver manually:

Office 2007:  https://download.cnet.com/2007-Office-System-Driver-Data-Connectivity-Components/3000-10254_4-75452798.html
Office 2010:  https://www.microsoft.com/en-us/download/details.aspx?id=13255
Office 2013:  https://www.microsoft.com/en-us/download/details.aspx?id=39358
Office 2016:  https://www.microsoft.com/en-us/download/details.aspx?id=54920

If you are using Office365, try the Office 2016 driver.  We have heard reports that the 2010 drivers do not work, but the 2007 drivers will work even for Office 2010.  If Office 2016 refuses to install without uninstalling the 64-bit driver, try installing the Office 2013 package instead.


EXCEL COLUMN NAMES
The first row of the worksheet should contain the column names.  These column names can be inserted into an email to personalize it, like this:

Dear [[customer_name]],


EXCEL TABLE NAME
The Table Name is typically "Sheet1$".  Enter this (without the quotes) in the Table Name field on the Database branch.


NOTES

• It is strongly recommended that the Cursor Type (on the Database/Setup branch) be set to "Static" or "Forward Only".
• Don't forget that any feature that makes changes to an Excel spreadsheet requires a proper Primary Key to work correctly.  This column must have a unique value in each row.
• Gammadyne Mailer may be unable to make changes to an Excel spreadsheet.  Changing a column can result in the "Operation must use an updatable query" error.  Deleting a row can result in the "Could not delete from specified tables" or "Deleting data in a linked table is not supported by this ISAM." error.  Trying adding ";READONLY=0" to the Connection String.  If that doesn't help, make sure there are no security restrictions on the Excel file or the folder it is located in.

Please see this article.




Gammadyne Mailer will work with any ODBC-compliant database that can be registered with the operating system (in Control Panel, ODBC Data Sources).  This includes all the major databases like Access, SQL Server, FoxPro, dBase, MySQL, Oracle, and SQLite.  Many CRM systems also support ODBC.

Because Gammadyne Mailer is a 32‑bit application, it requires the 32‑bit ODBC driver, even if your operating system is 64‑bit.  If you don't see your database type in the list of ODBC drivers, go to the database vendor's website and download and install their 32‑bit ODBC driver.

Gammadyne Mailer can also work with comma-separated text files, (.CSV files).  Please refer to the "Simple-Merge" feature at the bottom of the "Recipients" branch.




You must register the database under Control Panel, ODBC Data Sources and then point Gammadyne Mailer to the registered data source.  This will prevent the need to locate the database every time that Gammadyne Mailer needs to use it.

Look in the Help file for specific instructions on registering a database.  From the Table of Contents, choose "Database Menu", then "Register Database".

If you can't get it to work, the Database branch also offers a "Connection String" method.  Click the "Browse" button to create the Connection String.  If you don't see an ODBC driver for your database, you will have to obtain it from the database vendor.  Please note that you need the 32‑bit ODBC driver, because Gammadyne Mailer is a 32‑bit app.




We've noticed this error sometimes appears when a database column name is not recognized.

• Make sure that none of the column names contains a question mark.
• Verify the database columns in the Clause Table and Custom WHERE Clause.
• On the Database/Setup branch, try setting SQL Delimiter Mode to "Always".  Please note that this setting is hidden if "Hide Advanced Settings" on the Options menu is checked.

We have observed Access producing this error when a column name has a question mark.  Please rename the column.




Yes, on the Database branch, check the "Use Internal Database" box.  You will be prompted to supply a database name and table name.  To create columns, go to the View Result Set tool, then choose Create Column from the Column menu.  To import data, open the Database menu and choose "Import Addresses" or "Import CSV Data".

For a more robust solution, MySQL is free.




On the Database/Setup branch, change "Cursor Type" to "Static".




This typically occurs when trying to assign a new value to an Excel worksheet.  Possible solutions include:

• Add ";READONLY=0" to the Connection String.
• Make sure there are no security restrictions on the Excel file or the folder it is located in.
• Run Gammadyne Mailer with admin rights.
• Move the Excel data into a real database, like Access.

This typically occurs when trying to delete a record from an Excel worksheet.  Try the solutions in the previous FAQ.




This happens while Gammadyne Mailer is waiting for the database to satisfy the SELECT command that is used to fetch the mailing list.  Following are some changes that might help:

• Go to the Database/Setup branch and change Cursor Type to "Forward Only".
• Go to the Send/Logging branch and uncheck "Count Recipients".
• Go to the Database branch and clear out the "Order by column" field.
• Go to the Database branch and create a "Custom SELECT Statement" that only selects the columns that Gammadyne Mailer needs.
• If using a MySQL database, choose "Register Database" from the Database menu.  Select the data source and click "Configure".  The "MySQL Connector" window will appear.  Click Details, Flags 2.  Check "Don't cache results of forward-only cursors".
• Make sure that all columns that appear in the WHERE clause are indexed.

• It could be that a router/switch is being stressed.  Reboot all devices between you and your Internet connection.  Lower the number of Threads on the Send branch.  Employ throttling.
• Consider disabling TCP Chimney Offloading.

See also:  How to resume an interrupted Send Operation




Because Gammadyne Mailer is a 32‑bit application, it requires the 32‑bit ODBC driver, even if your operating system is 64‑bit.  Go to the database vendor's website and download and install their 32‑bit ODBC driver.

HTML Email

Before version 33.0, the <img> tags had to be properly specified.  This is no longer necessary.  On the HTML Body/Options branch, check the "Automatically Parse Images" box and set the "Image Locality" to the desired mode.  Gammadyne Mailer will automatically reformat the <img> tags and embed the images.

Gammadyne Mailer is extremely tolerant of how the file is specified.  All of these local filepaths are supported:
<img src="c:\images\example.png">
<img src="c:/images/example.png">
<img src="file:///c:/images/example.png">

Images that are in the Embedded Files Folder (on the "HTML Body/Embedded Files" branch) do not need a path:
<img src="example.png">
<img src="cid:example.png">

URL's to remote images are also allowed.  If "Image Locality" is set to "Internal", the image will be automatically downloaded and embedded in the email.
<img src="http://www.foo.com/example.png">

Notes:

• Unicode characters are supported.
• HTML encoded characters are supported.
• Images can also be relative to a <base> URL.
• Gammadyne Mailer may remove problematic characters from the filename to ensure that it appears properly in all email clients.
• We also recommend enabling "Auto Image Dimensions" and "Shrink Images" on the HTML Body/Options branch.

Please read this article.




Possible causes/solutions:

• Some email clients do not display images without the user's approval, especially if the sender is not trusted or the image is external (on a website, not inside the email).  Setting "Image Locality" (on the HTML Body/Options branch) to "Internal" may help.
• Some email clients, including Thunderbird, cannot handle spaces and certain symbols in the image filename.  For the best results, the filename should contain only letters and digits.
• Separate image files cannot share the same filename, even if they are located in different folders.
• It helps if the images are located in the Embedded Files Folder (located on the HTML Body/Embedded Files branch).
• Try using the "Troubleshoot HTML" tool (on the Test menu).
• Try using the "Validate HTML" tool (on the Test menu).
• Gammadyne Mailer does not support images specified by a style sheet.  The style sheet should only refer to external images with a complete URL.  The style sheet itself must not be located in an external file.  Some email clients do not support style sheets, even if they are in the HTML <head> section.
• Gammadyne Mailer does not support images specified by the "style" attribute of an HTML tag.  This technique will only work if the image's URL is absolute (not relative).
• Images may not appear correctly on the HTML editor's "Preview" tab, or in the Preview Window.  However, this does not mean that they will not appear correctly in the email client.  Send a test message to yourself to verify that the images work.
• Many email clients have a size limit for images.  Huge images may not display at all.  Try to keep them under 1 megapixel.

There are three methods for implementing an opt-out hyperlink in your emails.

METHOD #1: EMAIL

A recipient can be instructed to opt-out by sending an email to an email account that you have created that is dedicated to receiving opt-outs.  Gammadyne Mailer can then process these emails, and remove them from the mailing list.

An opt-out link typically looks something like this:

To unsubscribe from this mailing list, please send a blank email to remove@example.com

Where remove@example.com is replaced with an email account that you have created.  If you are using Gammadyne Mailer's internal HTML editor, it does have a tool to help create the opt-out link.  Go to the Edit tab, right click on the editor's background, and choose "Opt-Out Link" from the "Insert" submenu.

Each mailing list should have a separate opt-out account.  The next step is configuring a Gammadyne Mailer project to process the opt-outs in this email account and remove them from the mailing list.  This procedure is described here:  Help file > Table of Contents > Guides > Opt-Outs


METHOD #2: WEB FORM

If you want to have a web page that allows the user to submit their email address and have it removed from the mailing list, this involves website design which is outside the scope of the support we can offer you.  However, we have written an article on this here.


METHOD #3: ONE-CLICK UNSUBSCRIBE

Again, this involves website design.  You can write a PHP script that will do it, use the article mentioned in Method #2 for help.  The hyperlink will look something like this:

To unsubscribe from this mailing list, please go here:  http://example.com/optout.php?email=[[_email]]

We generally recommend against this.  It's better to use Method #2, otherwise any anti-virus software that tests all the URL's in the email will trigger the optout.


REMOVAL
Gammadyne Mailer does not necessarily have to delete a recipient from the mailing list.  When you are using a database, there are methods that don't involve destroying data.  On the Remove/Options branch, refer to the Removal Method setting.  You can insert an exclamation point at the beginning of the email address, which indicates they should not receive emails.  Or you can set a value in a different database column.  Whichever method you decide on, make sure you set this in both the opt-out project AND the mail sending project.  If you don't set it in the mail sending project, Gammadyne Mailer won't know which recipients to avoid.




To control the background color of the HTML body, the <body> tag should look something like this:

<body bgcolor="#FFFFFF">

The hexadecimal color code is reported by the System‑G color picker control.  Choose "Color picker" from the "Interface" menu.

Be aware that some email clients may ignore the <body> tag's style.




Sorry, but there is no way to prevent the recipient's email client from listing all embedded images along with the attachments.  Most email clients don't do it, but some do - there is nothing in the standard that prohibits it.

If you want the images to be external to the email (not embedded), then set Image Locality to "External" (on the HTML Body/Options branch), and specify a full URL to the image on your website, like this:

<img src="http://example.com/image.jpg">




An image that covers the entire background should not be specified in the <BODY> tag.  Instead, use a table, like this:

<body style="margin: 0">
<table style="background-image: url(http://foo.com/bar.gif)" width="100%">
<tr><td>...</td></tr>
</table></body>

For broadest support, do not attempt to embed the image - an external image should be used.




This usually won't affect the appearance of the email in the recipient's email client.  However, it is pretty easy to fix.

If the HTML refers to images located on a website, go to the HTML Body/Options branch and set the Image Locality to "External".

If the HTML refers to local images that will be embedded in the email, go to the HTML Body/Embedded Files branch and set the Embedded Files Folder to the location on the hard drive where the images are located.  Please note that for this to work, all of the embedded images must be located in this folder.

Note:  it was recently discovered that any <IMG> tag that follows an <OBJECT> tag will not preview correctly.  This is due to a flaw in Internet Explorer.  There is currently no known solution to this problem.




We have a whole article about this here.

Incoming Email Processing

Although it is not recommended, this is possible.  Please refer to Incoming Script Example #14 in the Help file.

To create a MS-DOS batch that will launch multiple incoming projects, please refer to the Help Guide entitled "Batch Operations".



Please refer to the help file (press F1), Table of Contents, Guides, Bounce-Backs.




If the opt-outs are coming in as emails, please refer to the help file (press F1), Table of Contents, Guides, Opt-Outs.

If you want an opt-out form on your website, please read this article.




If the sign-ups are coming in as emails, please refer to the help file (press F1), Table of Contents, Guides, Sign-Ups.

If you want a sign-up form on your website, please read this article.




The Incoming Log contains a detailed report of everything Gammadyne Mailer does during an incoming operation.  This reasons why messages were not processed can be found there.

On the "Incoming" branch, check the "Record incoming log" option.  To view the log, choose "View incoming log" from the Tools menu, or press F10.




The problem may be that the email addresses are occurring more than 2 lines away from the body keyword.  Change the "Addresses in body" setting (on the "Incoming/Processing" branch) to "Process all".

• Either "Process From:" or "Process Subject:" must be checked, or "Addresses in body" should be set to anything but "Ignore".  Otherwise, Gammadyne Mailer will not know where to look for the email address to be processed.
• The "Addresses in body" setting may need to be "Process all".  Keep in mind that if it is set to "Process if follows body keyword", then the email address must occur within two lines after the body keyword.

When the Processing Mode is "Add to database", the Incoming Script can use "let" statements to populate the newly created row:

[[let process_code = 6]]
[[let acct_rep = "John Public"]]
[[let sign_up_date = _now]]
[[let message = _mime]]

A more efficient alternative is to add and populate the row in one step with the db_add_row() G−Merge function, like this:

[[db_add_row("process_code", 6, "acct_rep", "John Public", "sign_up_date", _now, "message", _mime)]]

This function takes a variable number of parameters.  First there is a column name, inside quotes.  Next there is the value to store in the column.  See the help file for details.




The latch() G-Merge function can be used in the Incoming Script to extract data from the incoming message.  Consider the following message:

Name:John Public
Age: 36
Gender:M

The following Incoming Script could be used to extract this information and store it, first to a variable 's', and then to a file.

[[var s = latch(_body, "Name:") + CR]]
[[let s = s + latch(_body, "Age:") + CR]]
[[let s = s + latch(_body, "Gender:") + CR]]
[[file_save("c:\foo\bar.txt", s)]]

If the Processing Mode setting (on the Incoming/Processing branch) is "Add to database", the following script will extract this information and store it in the new row.  In this example, "name", "age", and "sex" are the names of database columns.

[[let name = latch(_body, "Name:")]]
[[let age = latch(_body, "Age:")]]
[[let sex = latch(_body, "Gender:")]]

The db_acquire_row() function can be used to lookup a recipient by their email address, and allow the columns of the recipient's database row to be modified.  The following example increments a column named "bounce_count".  If the resulting value is more than 4, the recipient is removed from the database.

[[if db_acquire_row(convert_lower_case(_email))]]
   [[let bounce_count += 1]]
   [[if bounce_count > 4]]
      [[db_delete_row()]]
   [[endif]]
[[endif]]

Please keep in mind that the Recipient Column must contain simple, lower case email addresses in order for the recipient to be found by db_acquire_row().




Here is an example that sets a column named "optout" to TRUE for all occurrences of the recipient.  This uses db_acquire_next_row() function to acquire subsequent rows after the first.

[[if db_acquire_row(convert_lower_case(_email))]]
   [[let optout = TRUE]]
   [[while db_acquire_next_row()]]
      [[let optout = TRUE]]
   [[endw]]
[[endif]]

To perform a removal, Gammadyne Mailer must check each record of the database.  This is necessary in order to implement all of the features on the "Remove/Options" branch.  However, there is an alternative method.  The db_acquire_row() G-Merge function will use a database query to find the email address.  Change the Processing Mode (on the Processing branch) from "Remove" to "No processing".  Then specify the following Incoming Script:

[[if db_acquire_row(convert_lower_case(_email))]]
    [[db_delete_row()]]
[[endif]]

This should be faster than performing a Remove operation.  However, it has the following disadvantages:

• The Recipient Column must contain simple, lower case email addresses in order for the recipient to be found by db_acquire_row().
• None of the features on the "Remove/Options" branch will be available.
• The workload will shift from Gammadyne Mailer to the database.

Either way, it helps if the Recipient Column's "indexed" property is enabled in the database.

Performance may also be improved by checking the "Fast Removal" box on the Remove/Options branch.  See the help file for more information about this feature.




The following example illustrates how the Incoming Script can take different actions based on a keyword in the subject.  The str_contains_i() function is used to search the subject for the keyword.

[[if str_contains_i(_subject, "SIGNUP")]]
   [[db_add_row()]]
   [[let email = convert_lower_case(_email)]]
   [[let status = "Active"]]
[[else]]
   [[if str_contains_i(_subject, "REMOVE")]]
      [[if db_acquire_row(convert_lower_case(_email))]]
         [[db_delete_row()]]
      [[endif]]
   [[endif]]
[[endif]]

This example adds the message's sender to the database if the subject contains "SIGNUP" and removes the sender if the subject contains "REMOVE".  For this to work, the "Process From:" box (on the Incoming/Processing branch) needs to be checked.




The auto-response can be redirected by assigning a new email address to the _recipient  predefined variable.  This is done in the Incoming Script.  Here is an example:

[[let _recipient = "jim@foo.com"]]

Please refer to the help file, Table of Contents, Guides, Bounce/Opt-Out Projects.





This error occurs when the POP3/IMAP4 server closes the connection abruptly.  Try the following:

• On the Incoming/Source branch, make sure Authentication is not "Secure Only".
• Try setting Incoming Encryption to "Disabled" (also on the Incoming/Source branch).
• Disable all anti-virus and Internet security software.

Tracking

Yes, please refer to the Gammadyne Email Tracking System.




Open the project that you use to send the mailing.  Click on the "Tracking" branch.  Check the "Tracking Enabled" box.  The settings for the tracking system are below this.  Enter the user name and password.




The user name is the email address that you specified when you purchased tracking credits.  The password is emailed to you once the payment is processed, usually within minutes.  Contact us if it does not arrive.




No, in the "Track Count" field you may enter a number that is smaller than the size of the mailing list.  It's okay if the number is larger, you will only be charged for the number of emails that are actually tracked.

Normally the beginning of the mailing list is tracked until Track Count is reached, however you may check the "Spread Tracking" box and enter a number.  For example, if Limit Number Tracked is 100, and Spread Tracking is 300, every third recipient of the first 300 is tracked.




Yes, choose "Manage Account" from the "Tracking" menu.




The tracking report is available for 30 days.  99% of email is received within 2 weeks.  After 30 days, the tracking data is deleted from the system.  Therefore you should download and save the report before that time.  You will receive an email warning 4 days in advance.

Also, read the next FAQ.




Yes, choose "Manage Account" from the Tracking menu.  Check the "FTP Upload Enabled" box.  Enter the domain name of the FTP server, the user name, and the password.  You must also specify the number of days after the mailing that the files should be uploaded (this must be less than 30).  Both the HTML report and the CSV data will be uploaded.




Yes.  First, generate a report.  Then choose "Export recipients to CSV" from the File menu.




The tracking system does not include bounces, because the only way to know there is a bounce is to process an email account and receive the bounce emails.  This process does not involve the tracking system because you are not paying Gammadyne for the expense of an email relay.

We recommend that you create and use a standard bounce project so that these emails can be removed from your mailing list.  Always run this project before starting a new campaign.  If you do so, your campaigns will have only a small number of bounces.  This is important because sending lots of undeliverable email can result in blacklisting.  For more information on creating a bounce project, please refer to the Help file > Table of Contents > Guides > Bounce-Backs.

It is possible to manually specify the number of bounces so that it appears on the report.  First, wait at least 24 hours for all the bounces to arrive.  Then run your bounce processing project.  Note the total number of bounces.  Generate the tracking report.  Choose "Specify Bounce Count" from the Tools menu.  Enter the total and click OK.

New in 58.0:  your bounce processing project can enable the "Track Bounces" option (on the Tracking branch).  After you run the Incoming Operation, it will prompt you to choose a Tracking Campaign, then the number of bounces will be transferred onto the report.




Some recipients do not download the tracking beacon, and so the email does not register as "opened", even though it was.  However, they may later click on a link, at which point the email does register as "opened".  Gammadyne Mailer is able to estimate how many recipients saw the email but went untracked by looking at link clicks.

For example, consider the following statistics:

Emails Tracked 100
Opens 30 (30%)
Links Clicked/Opened 6 (60%)
Links Clicked/Unopened 4 (40%)
Estimated Opens 58 (58%)

Because only 60% of the link clicks occurred on an email that downloaded the beacon, we can estimate that the number of opens is only 60% of the true number.  The number of emails that were detected from the beacon is 26 (30 - 4), and this is the number of emails that we want to calculate the estimate from.  We calculate "missed opens" as (26 / 60%) - 26.  This is 17.  Add this to the number of recognized opens, 30, for a total of 47 emails that are estimated to be opened.

The larger the mailing list and the more links clicked, the more accurate this estimate is.




After generating the tracking report, press the F1 key to open the help file where the statistics are explained in detail.




A low open rate could have the following causes:

• Many email clients do not download images automatically.  As a result, the tracking beacon never gets downloaded, and the email is not recognized by the tracking system as being opened.  A typical open rate is around 20%.  All email tracking services use the same technique, and therefore have this same weakness.  The cost of tracking credits is priced with this in mind.
• The mailing list could have a lot of undeliverable email.  Make sure that hard bounces are removed from the mailing list after every campaign.  This will reduce your consumption of tracking credits, and reduce your chance of being blacklisted.
• Your computer, or your mail server, may be blacklisted.  Use Gammadyne Mailer's "Check Blacklisting" tool to test for this.  If you are blacklisted, it is necessary to request removal from the organization that runs the blacklist.
• Your email may be treated as spam, so it is never reaching the recipient's inbox.  We have a detailed article on avoiding this here.

Miscellaneous

• Lower the number of Threads (on the Send branch).
• Consider changing Image Locality to "External" (located on the HTML Body/Options branch).  This will prevent images with an Internet URL from being downloaded and embedded in the outgoing emails.  The emails will be smaller, will deliver faster, and much less memory will be used.  If you must use embedded images, make sure they are no larger than necessary.
• Make sure that the hard drive has plenty of free space - at least 1 GB.
• When the "Preview Emails" option on the Send branch is checked, emails are stored in memory all at once, and this can use a lot of memory.  Disable this option.
• Using the "Eliminate Duplicate Recipients" option can use a lot of memory for large lists.  Remove the duplicates by checking "Remove Duplicates" on the Remove/Options branch, then choose "Remove Recipients" from the Tools menu.  Then uncheck "Eliminate Duplicate Recipients".  Once this is done, you can resume the Send Operation.
• Disable all third-party programs that run in the background, especially networking security/anti-virus products.
• Upgrade to the latest version of Gammadyne Mailer.

Multiple threads allow Gammadyne Mailer to send email as fast as the Internet connection allows.  Following is a list of the number of 4 KB messages that can be sent in one hour.  These figures are approximate, and can depend greatly on the message size, the speed of the Internet connection, the speed of the SMTP server, etc.

Connection Speed	Messages Per Hour
56K	2500
ISDN 64K	3500
ISDN 128K	7000
Cable 128K up	7000
DSL 384K	21,000
T1 1.5M	105,000

Not all SMTP servers support mailbox verification because this is commonly used by spammers.  It is better to send a slow, throttled campaign and remove the bounce-backs.




No.  AOL blocks port 25 except to its own mail servers.  However, its own mail servers have very restrictive policies, and there is no real chance that you can relay a significant quantity of mail through them.  We recommend getting a real ISP.




No.




Uncheck the Expiration Date setting on the Headers branch.




An SMTP server may automatically append an @ sign and its domain name to the "From:" or "To:" headers if they do not contain an email address.  This is a "feature" of some SMTP servers, and unfortunately Gammadyne Mailer has no control over it.  The only solution is to specify an email address in those fields.




No.  The only possible use for a list of random email addresses is spamming.  Please do not send spam with our software.




No.  The only possible use for a list of random email addresses is spamming.  Please do not send spam with our software.




Yes.  Relaying email through Gmail requires the following settings:

Server name: smtp.gmail.com
Port: 465
SMTP Authentication: OAuth-Gmail
User: your email address at gmail
Password: not needed for OAuth
SMTP Encryption: Required


Receiving email from Gmail requires the following settings:

Server name: pop.gmail.com
Port: 995
Authentication: OAuth-Gmail
User: your email address at gmail
Password: not needed for OAuth
Incoming Encryption: Required

Or if you prefer IMAP to POP3:

Server name: imap.gmail.com
Port: 993


Notes:

• A free Gmail account will only relay 100 emails per day.
• POP3/IMAP4 access must be enabled in the Gmail settings.  More on this here.
• When using POP3, you may need to add the "recent:" prefix to the user name.  This is described at the bottom of this page.

Your ISP is responsible for providing this information.  Usually, they post this information on their website.

Following are several methods for finding out which DNS server your computer is using:

Method #1 (LAN, shared, or proxy connections)
1.  Open File Explorer (the hotkey is Win+E).
2.  Right click on "Network Neighborhood" and choose "Properties".
3.  Double click on the "TCP/IP" protocol that is bound to the network adapter.  The "TCP/IP Properties" window should appear.
4.  Select the "DNS Configuration" folder.
5.  The DNS server address is listed under "DNS Server Search Order".  If it is not listed here, ask your system administrator.

Method #2 (dial-up connections)
1.  Open File Explorer (the hotkey is Win+E).
2.  Navigate to "Dial-up Networking".
3.  Right click on the connection and select "Properties".
4.  Select the "Server Types" folder.
5.  Click on the "TCP/IP Settings" button.
6.  The DNS server address is listed next to "Primary DNS".

Method #3 (Windows XP)
1.  Open File Explorer (the hotkey is Win+E).
2.  Right click on "My Network Places" and choose "Properties".
3.  A list of Internet connections will appear.  Right click on the appropriate one and choose "Status".  Usually there is only one Internet connection labeled "Local Area Connection".
4.  Click on the "Support" tab.
5.  Click on the "Details" button.  A window will appear listing the DNS Servers.

Method #4 (10/8/2012/7/2008/Vista)
1.  Open the Run dialog (the hotkey is Win+R).
2.  Type "cmd" and press Enter.  An MSDOS console window will appear.
3.  Type "ipconfig /all" and press Enter.
4.  The output will contain a listing of the DNS servers.




Most email clients will automatically detect hyperlinks in the text body.  Since the message body can contain only text, there is nothing you can do to ensure that all email clients will handle hyperlinks properly.  Just make sure the URL has the "http://" prefix for web hyperlinks and the "mailto:" prefix for email hyperlinks.

Following is an example of a page hyperlink and an email hyperlink:

For more information, visit http://www.foo.com

For more information, contact mailto:foo@bar.com

It is possible to integrate Office 365 with Gammadyne Mailer.  Use these SMTP settings:

Server name: smtp.office365.com
Port: 587
SMTP Authentication: Login or OAuth-Microsoft
SMTP Encryption: Required

Use these POP3 settings:

Server name: outlook.office365.com
Port: 995
Authentication: Normal or OAuth-Microsoft
Incoming Encryption: Required

Or this for IMAP4:

Server name: outlook.office365.com
Port: 993
Authentication: Normal or OAuth-Microsoft
Incoming Encryption: Required


Office 365 may have certain restrictions that can be problematic.  We recommend the following:

• Use the Universal Domain Throttle with a very restrictive rate of 1 email every 5 seconds.
• Set "Threads" (on the Send branch) to 3 or less.  Otherwise you may see this error:    432 4.3.2 STOREDRV.ClientSubmit; sender thread limit exceeded
• If you receive SMTP error 4640, then Office 365 is probably objecting to the From: header.  You may need to change the From: header to the same email address used in the SMTP User Name, or vice versa.
• Office 365 has a relay limit of 30 emails per minute (1 every 2 seconds), and 10,000 per day.  On the Servers/SMTP branch, check the "Use Project SMTP Settings" box.  Fill out the server information.  Specify the message limit (1) in the "Throttle Count" column.  Specify the number of seconds (2) in the "Throttle Period" column.  No more than Throttle Count messages will be sent to the SMTP server during each Throttle Period.  Or, if your mailing list is greater than 10,000, the Throttle Count should be 1 and the Throttle Period should be 9 (which is 9600 per day).
• Consider Option #3 as described in this article.  However, this should be unnecessary when using OAuth authentication (see above).

Office 365 is not terribly friendly to bulk email sending.  It would be wise to use the Single Send tool to send a test email to a Gmail address.





Check the "Preview Emails" box on the Send branch.  In the Preview Window, click on the "MIME" tab.

Also, the Success Script and Failure Script have a predefined variable, _mime, that contains the MIME body.  Here is an example that saves it to a file:

[[file_save("c:\work\mime.txt", _mime)]]

Gammadyne Mailer runs on the Windows platform (XP or later).  Any computer made since 2001 should run it fine.

For machines that cannot send via direct delivery, a relaying SMTP server is required.




A Word document cannot be used for the body of an email.  HTML is the only solution.

To convert a Word document to text, first select all text by pressing Ctrl+A, press Ctrl+C to copy it to the clipboard, then go to Gammadyne Mailer and paste the clipboard into the Text or HTML Body by pressing Ctrl+V.  However, this is a bad idea for HTML.  This will put a bunch of proprietary Microsoft tags in the HTML code, and it won't look right in some email clients.  HTML should be designed from the ground up to work right for email.  Use Gammadyne Mailer's Template Designer or a third party email template.




It has been observed that Hotmail will treat messages as spam if:

1. The email does not have a valid email address in the "From:" header.
2. The email's "To:" header does not match the recipient's email address.

These limitations are "features" of Hotmail and Gammadyne Mailer has no control over them.  There are no workarounds for this problem.  These rules must be obeyed in order to send to Hotmail successfully.

In general, you should also follow these guidelines.




Educational institutions can receive a 20% discount by going here.

You won't be alone!  Gammadyne Mailer is used by the following educational institutions:

American College of Cardiology
American College of Orgonomy
Arcadia University
Arkansas State University
Auburn University
Avon College
Baylor University
Beaver College
Brown University
Carnegie Mellon University
Columbia University
Concordia University
Conestoga College
Cornell University
Crichton College
Culver-Stockton College
Dallas Independent School District
Eastern Michigan University
Elmira College
Florida A&M University
Florida International University
Fordham University
Georgia Southern University
Georgia Tech
Harvard
Hawaii Pacific University
Hondros College
Indiana State University
Kansas State University
Kenyon College
King's College London
Knox College
Kwantlen University College
Lehigh University
Live University
Mars Hill College
Maryville College
McGill University
McMaster University
MIT
Mt. San Antonio College
Murray State University
Newcastle College
North Iowa Area Community College
Norwich University
Ohio University
Oklahoma State University
Open Universiteit Nederland
Pace University
Penn State University
Pensacola Christian College
Pfeiffer University
Presbyterian College
Purdue University
Queens College
Quesnel School District
Ross University
Royal NZ College of GPs
San Francisco State University
Seoul Digital University
Sheffield University
Skidmore College
Sonoma State University
South Cheshire College
Spring Hill College
St. Francis College
St. Jean Vianney Catholic School
St. John's School
St. Mary's Dominican High School
Stanford University
Stellenbosch University
Stony Brook University
Strongsville City Schools
Swarthmore College
Temple University
The American College of Greece
The City University of New York
The Dallas School of Music
Tufts University
Tulane University
United Nations International School
United States Sports Academy
Universitat Autonoma De Barcelona
University of Alabama at Birmingham
University of Alaska
University of California
University of Colorado at Colorado Springs
University of Dallas
University of Edinburgh
University of Fribourg
University of Iowa
University of Maryland
University of Michigan
University of Montreal
University of New Orleans
University of North Dakota
University of North Texas
University of Queensland
University of South Florida
University of Texas at San Antonio
University of Virginia
University of Wisconsin-Milwaukee
University of Zurich
Utah State University
West Valley College





Non-profit institutions can receive a 20% discount by going here.

You won't be alone!  Gammadyne Mailer is used by the following non-profit institutions:

A.J. Fletcher Foundation
American Missionary Fellowship
Archdiocese of Chicago
Archdiocese of Milwaukee
Arthritis-Research.org
Atlanta Contemporary Art Center
C. S. Mott Foundation
Canadian Landmine Foundation
Chofetz Chaim Heritage Foundation
Christian Leadership Ministries
Colonial Williamsburg Foundation
Congregation Beth Adam
Council of Better Business Bureaus
Doctors For Global Health
Earth Pledge Foundation
Faith Life Church
Far Hills Baptist Church
Feminist Majority Foundation
Ferguson Library
Fishers of Men Lutheran Church
Florida Dept. of Education
Florida Holocaust Museum
Foundation for Advancements in Science and Education
Foundation for Early Learning
Foundation for Indigenous Languages
Fremont Presbyterian Church
Greater Philadelphia Cultural Alliance
Hartford Foundation
Harvest International Ministries
Henry Jackson Foundation
Hewlett Foundation
Immanuel Presbyterian Church
Iowa Association of School Boards
Iowa Rural Water Association
Jewish Community Alliance
Kenneth Copeland Ministries
Lawyers' Committee on Nuclear Policy
Maine Association of Nonprofits
Mercy Ships
Mid Atlantic Arts Foundation
Minnesota Historical Society
Minnesota Public Radio
Multiple Sclerosis Association
Muscular Dystrophy Association
National Center for Farmworker Health
National Energy Action
National Jewish Democratic Council
National Middle School Association
National Writers Union
New Hope International
New Life Church
North Point Community Church
PEACEchurch
Pinellas Community Church
Plain Truth Ministries
Presidential Trust Foundation
Rainbow Ministries
Religious Freedom Coalition
RHEMA Bible Church
Science Museum of Minnesota
The Alannah & Madeline Foundation
The BlackUSA Foundation
The Jewish Destiny Foundation
The Nature Conservancy
The New York Public Library
The People's Church
The Pettit Foundation
The Stanley Foundation
Twin Cities Public Television
UN-HABITAT
United Way
Westport Historical Society
Willow Creek Association
Wisconsin Dept. of Health & Family Services
Zion's Hope





Gammadyne Mailer is trusted by thousands of companies all over the world, including:

Agilent Technologies
Airbus
Asus
AT&T
Avis
Bayer
Beretta
Boeing
Canadian Worldwide Express
CBS
Chicago Cubs
Cisco Systems
Council of Better Business Bureaus
Cottman Transmission
Crabtree & Evelyn
DHL
Dice.com
Discount Home Shopping Club
Dollywood
Ford Motor Co.
France Telecom
Go Daddy
Guess? Inc
Home Shopping Network
IBM
Intel
Kodak
Lucent Technologies
Lycos
Merrill Lynch
Microsoft
MIT
Mobil 1
Motorola
Multiple Sclerosis Association
Muscular Dystrophy Association
Nintendo
Nokia
Nortel Networks
Novell
RE/MAX
Segway
Siemens
Smith & Wesson
Sony
St. Marys Hospital For Children
Texas Department of Health
The Golf Channel
The Futures Channel
The Nielsen Company
Thomson Reuters
Time Warner
Toshiba
UAW
United Way
UPS
U.S. Steel
WebMD
Xerox




No email program has the ability to hide the sender's IP address.  The only use for such a feature would be sending spam.  Please do not send spam with our software.




Gammadyne Mailer is not vulnerable to viruses.  The only conceivable way that it would be is if you intentionally wrote an Incoming Script that saves attachments to the hard drive and then opens them.




Sorry, but Gammadyne Mailer cannot run as a service.  A service is not allowed to have a user interface, and this requirement is incompatible with Gammadyne Mailer's design.

If Gammadyne Mailer is taking up too much space on the taskbar, go to the Window menu and check "Minimize to Tray".

You may find the "Scheduler" tool to be useful.  This is located on the Tools menu.




Although this does not involve Gammadyne Mailer directly, we have written two articles on this subject:
Signup Forms
Optout Forms