Updated March 2020; see History
This is an improved alternative to the original direct-to-SMTP mode, Method,2 (aka Type,3 in PDFXv3). Enhancements and characteristics include:
| • | Displays details about failures to connect with the SMTP server |
| • | SSL/TLS is supported |
| • | Requires AshNet.DLL. |
| • | A-Shell will maintain a log file of Method 4 message sent. The default log file is OPR:SMTP.LOG. You can change that with the above statement. To deactivate the log entirely, set logfile to "". |
| • | Email.Method,4 will override subsequent Email.Method directives, so you can effectively convert existing program-generated files to use Method 4 without modifying the programs. For example, you could create a prefix file, say, ASHCFG:PDFX.PFX which contains: //PDFX,Email.Method,4 and then add PREFIX=ASHCFG:PDFX.PFX to any printer init files that use DEVICE=PDFX... |
Three directives are implemented for Method 4 only; they do not work with the other mail types.
//PDFX, Email.ID, idstring
This just attaches an arbitrary idstring (up to 32 chars) to the message. Currently the only purpose of this is to identify the message in the log (described below). Conceptually, applications that send a lot of messages may want to assign unique identifiers to them for tracking/follow-up purposes.
//PDFX,Email.Header,hdr,hdrvalue
e.g.
//PDFX,Email.Header,Disposition-Notification-To,jack@microsabio.com
This statement allows you to add an arbitrary header to the message. The example given is a particularly useful one, requesting a return receipt from the recipient when she reads the message. Definitions of standard headers can be found on the Internet, but keep in mind that it is up to the particular SMTP server and/or email client to properly interpret them. Also note that contrary the standard //PDFX,Email.xxx,value directive, this one effectively takes two arguments - the header name and its value. You can, however, enclose the last two arguments in quotes if you prefer to maintain the single argument syntax.
//PDFX,Email.LogFile,logfile
History
2021 March, A-Shell 6.5.1700 PDFX enhancement: you can now use the EMAIL capabilities of PDFX for sending emails without any PDF attachment. This is an extension of a capability introduced in 6.4.1548.8 which allowed sending of a set of attachments without sending the primary PDF. In both cases, the key is for the print file to not contain anything that will generate output—i.e. plain text or //GDI commands that generate output. For the body of the email message, you have to use the //PDFX,Email.Content directives. As with all other cases involving Email.Content directives, the last one must be followed by some other Email.xxx directive.
2017 April, A-Shell 6.4.1548: Email Type/Method 4: if nothing is in the created PDF, and there is at least one additional attachment, then the created PDF will not be included in the attachment list. This allows PDFX to be used, with Email Type/Method 4, as a means of emailing pre-existing documents without the need to generate a new PDF.
