Skip to main content

Turbo Email Sender File Edition

+ Write eMails & Schedules in Files, and Use Them to Get Automatic eMailing
+ Sending Schedule + Sending One by One with Interval (Seconds) Setting
+ Repeated Sending with Times and Interval (Minutes) Settings
+ Automatic Resending if Failed with Maximal Times and Interval Settings
+ Macros Manager & Built-in Macros
+ Folder Attachment Supportable
+ Supports Emptying Folder After Sent It Successfully
+ SMTP Accounts/Proxy Sservers (Automatic Selecting Available One) Read more

Sample Files

 

Interface Definitions and Sample Files


DownloadDownload Turbo Email Sender File Edition
Produced by SOFT-0.COM

Download Sample Files

Supported File Types

Text/Initialization/Configuration Files (*.txt;*.ini;*.cfg) and XML Files (*.xml).

Fields and Order

12 fields: To, CC, BCC, Subject, Attachments, Mail_Type, Content, Priority, One_By_One, Request_Read_Receipt, Schedule, Delete_File_After_Sent

Fields Explanation

FieldDescriptionSpecification & NoteExample
To/CC/BCCDesignates who receive this email and how.Required, must provide one of them at least.

Specification
xA@yA.zA,xB@yB.zB,... or Name A|xA@yA.zA,Name B|xB@yB.zB,...
That is, just write email addresses (or with contact name in Name|Address format) and separate them by comma (,).

File Supported
AMSFE Also supports reading email addresses from a plain text file (*.txt or any other extensions), ONE recipient per line (xA@yA.zA or Name|xA@yA.zA format).

Remarks
a few SMTP servers reject sending emails to self (the sender is the same as the receiver), if your message cannot be sent successfully, you may check this reason.		Direct Addresses
addA@AAA.com,addB@AAA.com,John|john@BBB.com,Jack|jack@BBB.com

Recipients File
E:\recips_for_amsfe\classmates.txt
SubjectThe subject of this email.Required. Must be written in ONE line.This is a test email.
AttachmentsThe attachments which will be sent with this email.Optional.

Specification
Supports file and folder attachments, just give full path of each file/folder and separate them by vertical (|). Also supports emptying corresponding folder after sent it successfully, just append *E string to folder path.

Remarks
a few SMTP servers reject sending the unsafe executable files (such as .exe/.bat/.com) directly, the servers will return the 552 error code (such as Gmail), you can compress these files as .zip/.rar or others for sending to solve this problem. Now, even the compressed file that include the unsafe executable files are not allowed to send also, such as Gmail, please click here to know more details. So, to ensure your message can be sent successfully, please rename the unsafe executable files and then compress them for sending (tell receivers the original file names in content).

*E is usually used to avoid sending duplicate files under a fixed folder. For instance: you plan to send latest machine running log to some colleagues every day, and a program logs them into E:\logtosend folder with different file names. So, you may need to use this folder attachment (E:\logtosend) in your email file. After it worked a few times, you will find that the received attachments include the previous logs every time, at this time, this option is very useful, it ensures that your colleagues will no longer receive duplicate and expired logs. But please note that you may need to choose a proper time for schedule (usually, after finished logging).		E:\atts\fileA.txt|E:\atts\folderA|E:\atts\folderB*E|E:\atts\fileB.png
Mail_TypeSpecifies the email content is 'Plain Text' or 'Rich Text' (HTML format).Optional. P or R. P = Plain Text, R = Rich Text (HTML), default: P.P
ContentThe email content.Optional.

Specification
For plain text, just write content directly, for rich text, please write HTML source code.

File Supported
AMSFE Also supports reading email content from a file (*.txt, *.html or any other extensions that contain text).

Remarks
To get the HTML source code, just open your .html file by Notepad and do a full text copy; to get a HTML file, just design email content in AMSFE's Rich Text (HTML) Email Content Editor and save it.

If you use rich text (HTML) as email content, you must specify Mail_Type field as R, else the recipients will receive the HTML source code, no one knows what you meaning.		Direct Text
Dear John, I have got the greeting card, thank you!

Content File
E:\content_for_amsfe\for_classmates.html
PrioritySet the priority of email.Optional. H, N or L. H = High, N = Normal, L = Low, default: N.H
One_By_OneSend email in one by one mode or not.Optional. Y or N. Y = Yes, N = No, default: N.Y
Request_Read_ReceiptRequest read receipt for the receivers.Optional. Y or N. Y = Yes, N = No, default: N.

Remarks
The read receipt receiver is specified in your SMTP account.		Y
ScheduleSet the automatic emailing schedule here.Required. AMSFE supports yearly, monthly (day and weekday), weekly, daily, specific date schedules and repeated sending.
You can set many schedules here, and must separate them by vertical (|).

Specification
Yearly MM-DD HH:MI
Monthly DD HH:MI or Monthly LastDay HH:MI or Monthly First/Second/Third/Fourth/Fifth/Last d HH:MI
Weekly d HH:MI
Daily HH:MI
Specific YYYY-MM-DD HH:MI
Repeat - *i t, to set repeated sending, just append it to above schedules.

Remarks
YYYY - years as 1900-9999.
MM - months as 01-12.
DD - days as 01-31.
HH - hours as 00-23.
MI - minutes as 00-59.
d - days of week as 0-6 (0 = Sunday, 1 = Monday, ...).
i - interval minutes as 10-120.
t - repeated times as 1-3.
'LastDay' may be 31 (for Jan, Mar, May, Jul, Aug, Oct, Dec), 30 (for Apr, Jun, Sep, Nov), 28 or 29 (for Feb), so, it is a very flexible option.
All the blanks between blue texts are ONE space character.		For Each Schedule
Yearly 02-27 15:35
Monthly 23 09:08
Monthly LastDay 15:00
Monthly Fourth 0 09:09
Weekly 5 16:30
Daily 08:29
Specific 2012-06-28 12:00

A Complete Schedules Setting with Repeated Sendings
Monthly 23 09:08|Monthly LastDay 15:00|Weekly 5 16:30*30 2|Monthly Fourth 0 09:09*60 1|Specific 2012-06-28 12:00
Delete_File_After_SentDelete this email file after sent it successfully, commonly used for the one-off files that produced by other programs/devices.Optional. Y or N. Y = Yes, N = No, default: N.N


Text/Initialization/Configuration Files (*.txt;*.ini;*.cfg) Explanation

  • These 3 file types have the same format, please choose the appropriate extension according to your preference.
  • The first line must be [AMSFE_Email_File].
  • Please use equal sign (=) to separate name and data for each field, e.g. Subject=This is a test email.
  • Name and data of each field must be written in one line except 'Content' field.
  • For 'Content' field, if uses a content file, just write it in one line as above; if uses direct text, please place all data between <BEGIN> and <END>.
    E.g. Content=<BEGIN>Hello Michael,
    Thanks for your help, now I know about how to make it, thank you again.
    Best regards!
    Yours: Jack<END>

XML Files (*.xml) Explanation

  • Just write data in the corresponding element/field by referring to the XML sample files.
  • Data must be written in one line except 'Content' element/field.
  • Please replace & symbol with &amp;, < symbol with &lt;, > symbol with &gt; (do NOT replace & in &amp;, &lt; and &gt; again) for Attachments, Subject and Content elements/fields. This is XML/HTML specification, else the XML file can not be parsed by AMSFE or any other XML reader.
    These symbols usually appear HTML source code in Content field, so we recommend you use file content to replace direct HTML source code for Content field in XML file.
  • All element/field names are case sensitive.
Download Sample Files

DownloadDownload Turbo Email Sender File Edition for Windows 11. 10. 8.1. 8. 7