opflags specifies various operation flags, using the sum of one or more of the following (from EMAILX.MAP):
|
Symbol |
Value |
Type |
Description |
|
EMF'NORMAL |
0 |
B,2 |
normal operation |
|
EMF'LEAVEOPEN |
1 |
B,2 |
don't close session |
|
EMF'ALREADYOPEN |
2 |
B,2 |
don't open; (already open) |
|
EMF'OPENONLY |
4 |
B,2 |
open only; ignore all but SERVER & HOST |
|
EMF'CLOSEONLY |
8 |
B,2 |
close only |
|
EMF’HDRCAT |
16 |
B,2 |
concatenate HEADER+BODY (no CRLF) |
|
EMF’HTMLBODY |
32 |
B,2 |
BODY contains <HTML> |
|
EMF_MIMEBODY |
64 |
|
BODY is a self-contained MIME part |
|
EMF_TLS |
1024 |
|
Use SSL/TLS for SMTP connection |
|
EMF_STARTTLS |
2048 |
|
Use STARTTLS (start with unencrypted connection, then elevate to TLS with the STARTTLS SMTP command) |
Note that in most cases you can get by with EMF’NORMAL. The next four flags (EMF’LEAVEOPEN, EMF’ALREADYOPEN, EMF’OPENONLY, and EMF’CLOSEONLY) are only of interest if you are sending a lot of emails in a batch and want to eliminate the overhead of having to open and close the connection with the SMTP server for each message. EMF’HDRCAT is only used when you want to include email header items in both the header and body parameters. And EMF’HTMLBODY is only recommended when you have used your own HTML formatting within the body of your message.