|Field||Description||Specification & Note||Example|
|To/CC/BCC||Designates who receive this email and how.||
Required, must provide one of them at least.
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 (,).
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).
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.
|Subject||The subject of this email.||Required. Must be written in ONE line.||This is a test email.|
|Attachments||The attachments which will be sent with this email.||
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.
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).
|Mail_Type||Specifies 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|
|Content||The email content.||
For plain text, just write content directly, for rich text, please write HTML source code.
AMSFE Also supports reading email content from a file (*.txt, *.html or any other extensions that contain text).
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.
Dear John, I have got the greeting card, thank you!
|Priority||Set the priority of email.||Optional. H, N or L. H = High, N = Normal, L = Low, default: N.||H|
|One_By_One||Send email in one by one mode or not.||Optional. Y or N. Y = Yes, N = No, default: N.||Y|
|Request_Read_Receipt||Request read receipt for the receivers.||
Optional. Y or N. Y = Yes, N = No, default: N.
The read receipt receiver is specified in your SMTP account.
|Schedule||Set 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 (|).
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
Specific YYYY-MM-DD HH:MI
Repeat - *i t, to set repeated sending, just append it to above schedules.
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
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_Sent||Delete 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|