Posted by Jim Guerber on March 16, 2005 at 09:17:31:
In Reply to: Email Printer posted by Stephen Auerbach on March 15, 2005 at 13:22:33:
1. I do not currently know how we can give the attachment a name. I will research this. Future enhancement perhaps.
2. Experimentation shows that. We do spell out text vs. attachment strategy for each doc type.
3. When designing the email printer, we spent much time trying to use the MS MAPI interface to the user's email program to send the email. There is currently so much protection of this interface that we could not avoid a windows message box popping up each time an email was sent using this interface. So, we decided to use the SMTP protocol ourselves. The result is that you see no record of the email being sent in your email program. Hense the log file.
The log file is not too bad to interpret. It is composed of lines describing actions performed by the email printer and lines of responses from the SMTP server. The SMTP server lines are all preceeded by numbers. The explanation for those response numbers can be found in RFC 821 and RFC 2821. Here is a list.
NUMERIC ORDER LIST OF REPLY CODES
211 System status, or system help reply
214 Help message
[Information on how to use the receiver or the meaning of a
particular non-standard command; this reply is useful only
to the human user]
220
221
250 Requested mail action okay, completed
251 User not local; will forward to
354 Start mail input; end with
421
closing transmission channel
[This may be a reply to any command if the service knows it
must shut down]
450 Requested mail action not taken: mailbox unavailable
[E.g., mailbox busy]
451 Requested action aborted: local error in processing
452 Requested action not taken: insufficient system storage
500 Syntax error, command unrecognized
[This may include errors such as command line too long]
501 Syntax error in parameters or arguments
502 Command not implemented
503 Bad sequence of commands
504 Command parameter not implemented
550 Requested action not taken: mailbox unavailable
[E.g., mailbox not found, no access]
551 User not local; please try
552 Requested mail action aborted: exceeded storage allocation
553 Requested action not taken: mailbox name not allowed
[E.g., mailbox syntax incorrect]
554 Transaction failed
maybe you could write an enter program that interprets the log file and builds a single line success/fail log.