Setup of E-Mail Client Blat

Examples    Content    Home    F.A.Q.    Help Me    Index    Online Help    Rules theory    Forms & Paper handling

There are two main reasons to install the ELP e-mail functionality:

    1. On errors during processing print data, ELP sends out an e-mail notifying that a problem occurred and that queue is perhaps stopped.
    2. E-Mail/Fax sending out the job as Tiff / PDF: ELP is able to send the output file to any e-mail address(es). So invoices can be sent automatically to the ordering person. Using a nice body text possible errors in quantity, shipment addresses can be eliminated, as well as phone calls for the tracking number, if the number is listed on the invoice or delivery note.

The e-mail communication is done using the SMTP protocol. The widely used software is called BLAT, which is a public domain software developed by a university.

License agreement:

License to use Blat copied out of the software readme file January 2003.

The authors of Blat have placed it in the public domain. This means you can use it free of charge for any purpose you like, with nearly no conditions being placed on its use by us. The source code is also available free of charge and under the same conditions as the executables.

You have permission to modify, redistribute, hoard, or even sell Blat in its executable or source form. If you sell Blat though, we'd appreciate it if you'd provide your own support (and send us a free copy). We cannot take any support load for Blat (we've got better things to do).

The only limitation we impose is that Blat not be used to send unsolicited commercial e-mail. Use of this software to send unsolicited commercial e-mail constitutes an agreement to pay the authors $10,000.

Various bits of the source code are copyrighted by other people/organizations. Look in the source code for copyright ownership.

The authors and contributors of the package are not responsible for any damage or losses that the usage of Blat may cause. We are especially not responsible for the misuse of the SMTP (or other) mail system.

Before ELP can send out any e-mail, the client blat needs to be configured. There are 2 ways to do this, the first method has the advantage, that it is menu driven, but also the disadvantage, that possible errors are only displayed indirectly.

1. Use Control Center menus to configure the e-mail client

Open the Admin Tab and click on the Configure Button. Fill out the opened Window. Enter the IP address of your SMTP / NNTP / POP3 or IMAP server. Then if the server does not check any e-mail sender address enter a free address, maybe keep WELP@...


Press the OK button and fill out the admin e-mail field. Those addresses will only get e-mails if W-ELP detects a problem through printing, or if the queue might hang. You may add several addresses separated by comma.

Finally press the buttons "Apply" and "Send test e-mail".

If within a short time the admins does not receive a test mail, their addresses are either entered wrong, or more likely the setup failed using the Control Center menu.

Hints:

2. Use the blat command line in order to configure the utility

blat -install 192.168.0.1 Info@stethos.com

(If info exists)

Now Try to send an e-mail to your attention: blat ..\em_body.txt -to Your e-mail address@your  company name.de

Any possible error message is now written to the console. For a short help on blat type blat for the full help type blat /? | more

If the e-mail was sent, you can return to the Control Center and retry sending the test e-mail to the admins.Do not forget to Apply the e-mail Names, before pressing the test button.

Complete set of command line arguments for Blat v2.6.2 w/GSS encryption (build : Feb 25 2007 12:06:19)

 Win32 console utility to send mail via SMTP or post to usenet via SNNTP by P.Mendes, M.Neal, G.Vollant, T.Charron, T.Musson, H.Pesonen, A.Donchey, C.Hyde http://www.blat.net syntax:

 Blat <filename> -to <recipient> [optional switches (see below)]

 Blat -SaveSettings -f <sender email addr> -server <server addr> [-port <port>] [-try <try>] [-profile <profile>] [-u <login id>] [-pwd <password>]

 or

 Blat -install <server addr> <sender's addr> [<try>[<port>[<profile>]]] [-q]

 Blat -profile [-delete | "<default>"] [profile1] [profileN] [-q]

 Blat -h

Installation ---------------------------------

-SaveSettings>   : store common settings to the Windows Registry. Takes the same parameters as -install, and is only for SMTP settings.

                : set server, sender, number of tries and port for profile
                  (<try n times> and <port> may be replaced by '-')
nbsp;                 port defaults are SMTP=25, NNTP=119, POP3=110, IMAP=143
                  default profile can be specified with a '-'
                  username and/or password may be stored to the registry
                  order of options is specific
                  use -installNNTP for storing NNTP information
                  use -installPOP3 for storing POP3 information
                      (sender and try are ignored, use '-' in place of these)
                  use -installIMAP for storing IMAP information
                      (sender and try are ignored, use '-' in place of these)

The Basics ----------------------------------

<filename> file with the message body to be sent if your message body is on the command line, use a hyphen (-) as your first argument, and -body followed by your message if your message will come from the console/keyboard, use the hyphen as your first argument, but do not use -body option.
-of <file> text file containing more options (also -optionfile)
-to <recipient> recipient list (also -t) (comma separated)
-tf <file> recipient list filename
-cc <recipient> carbon copy recipient list (also -c) (comma separated)
-cf <file> cc recipient list filename
-bcc <recipient> blind carbon copy recipient list (also -b) (comma separated)
-bf <file> bcc recipient list filename
-maxNames <x> send to groups of <x> number of recipients
-ur set To: header to Undisclosed Recipients if not using the -to and -cc options
-subject <subj> subject line, surround with quotes to include spaces(also -s)
-ss suppress subject line if not defined
-sf <file> file containing subject line
-bodyF <file> file containing the message body
-body <text> message body, surround with quotes (") to include spaces
-sig <file> text file containing your email signature
-tag <file> text file containing taglines, to be randomly chosen
-ps <file> final message text, possibly for unsubscribe instructions

Registry overrides ------------------------------

-pp <profile> send with server, user, and port defined in <profile>;use username and password if defined in <profile>
-profile list all profiles in the Registry
-server <addr> specify SMTP server to be used (optionally, addr:port)
-serverSMTP <addr> same as -server
-serverNNTP <addr> specify NNTP server to be used (optionally, addr:port)
-serverPOP3 <addr> specify POP3 server to be used (optionally, addr:port)when POP3 access is required before sending email
-serverIMAP <addr> specify IMAP server to be used (optionally, addr:port) when IMAP access is required before sending email
-f <sender> override the default sender address (must be known to server)
-i <addr> a 'From:' address, not necessarily known to the server
-port <port> port to be used on the SMTP server, defaults to SMTP (25)
-portSMTP <port> same as -port
-portNNTP <port> port to be used on the NNTP server, defaults to NNTP (119)
-portPOP3 <port> port to be used on the POP3 server, defaults to POP3 (110)
-portIMAP <port> port to be used on the IMAP server, defaults to IMAP (110)
-u <username> username for AUTH LOGIN (use with -pw)
-pw <password> password for AUTH LOGIN (use with -u)
-pu <username> username for POP3 LOGIN (use with -ppw)
-ppw <password> password for POP3 LOGIN (use with -pu)
-iu <username> username for IMAP LOGIN (use with -ppw)
-ipw <password> password for IMAP LOGIN (use with -pu)

---------------------- Miscellaneous RFC header switches ----------------------

-oorganization <organization> Organization field (also -o and -org)
-ua include User-Agent header line instead of X-Mailer
-x <X-Header: detail> custom 'X-' header. eg: -x "X-INFO: Blat is Great!"
-noh prevent X-Mailer/User-Agent header from showing Blat homepage
-noh2 prevent X-Mailer header entirely
-d request disposition notification
-r request return receipt
-charset <cs> user defined charset. The default is ISO-8859-1
-a1 <header> add custom header line at the end of the regular headers
-a2 <header> same as -a1, for a second custom header line
-dsn <nsfd> use Delivery Status Notifications (RFC 3461)n = never, s = successful, f = failure, d = delayed. can be used together, however N takes precedence
-hdrencb use base64 for encoding headers, if necessary
-hdrencq use quoted-printable for encoding headers, if necessary
-priority <pr> set message priority 0 for low, 1 for high
-sensitivity <s> set message sensitivity 0 for personal, 1 for private, 2 for company-confidential

Attachment and encoding options -----------------------

-aattach <file> attach binary file(s) to message (filenames comma separated)
-attacht <file> attach text file(s) to message (filenames comma separated)
-attachi <file> attach text file(s) as INLINE (filenames comma separated)
-embed <file> embed file(s) in HTML. Object tag in HTML must specifycontent-id using cid: tag. eg: <img src="cid:image.jpg">
-af <file> file containing list of binary file(s) to attach (comma separated)
-atf <file> file containing list of text file(s) to attach (comma separated)
-aef <file> file containing list of embed file(s) to attach (comma separated)
-base64 send binary files using base64 (binary MIME)
-uuencode send binary files UUEncoded
-enriched send an enriched text message (Content-Type=text/enriched)
-unicode message body is in 16- or 32-bit Unicode format
-html send an HTML message (Content-Type=text/html)
-alttext <text> plain text for use as alternate text
-alttextf <file> plain text file for use as alternate text
-mime MIME Quoted-Printable Content-Transfer-Encoding
-8bitmime ask for 8bit data support when sending MIME
-multipart <size> send multipart messages, breaking attachments on <size>KB boundaries, where <size> is per 1000 bytes
-nomps do not allow multipart messages

-------------------------------- SNTP specific options ----------------------------

-groups <usenet groups> list of newsgroups (comma separated)

-------------------------------- Other options --------------------------------

-xxtndxmit Attempt to use POP3 to transmit when accessing POP3 first
-h displays this help (also -?, /?, -help or /help)
-q suppresses all output to the screen
-debug echoes server communications to a log file or screen(overrides -q if echoes to the screen)
-log <file> log everything but usage to <file>
-timestamp when -log is used, a timestamp is added to each log line
-overwritelog when -log is used, overwrite the log file
-ti <n> set timeout to 'n' seconds. Blat will wait 'n' seconds forserver responses
-try <n times> how many times blat should try to send (1 to 'INFINITE')
-binary do not convort ASCII | (pipe, 0x7c) to CrLf in the messagebody
-hostname <hst> select the hostname used to send the message via SMTP this is typically your local machine name
-raw do not add CR/LF after headers
-delay <x> wait x seconds between messages being sent when used with-maxnames or -multipart
-comment <char> use this character to mark the start of commments inoptions files and recipient list files. The default is ;
-superdebug hex/ascii dump the data between Blat and the server
-superdebugT ascii dump the data between Blat and the server

Note that if the '-i' option is used, <sender> is included in 'Reply-to:' and 'Sender:' fields in the header of the message.

Optionally, the following options can be used instead of the -f and -ioptions:

-mmailfrom <addr> The RFC 821 MAIL From: statement
-from <addr> The RFC 822 From: statement
-replyto <addr> The RFC 822 Reply-To: statement
-returnpath <addr> The RFC 822 Return-Path: statement
-sender <addr> The RFC 822 Sender: statement

For backward consistency, the -f and -i options have precedence over these RFC 822 defined options.  If both -f and -i options are omitted then the RFC 821 MAIL FROM statement will be defaulted to use the installation-defined default sender address.

Macro Tab    Admin Tab    Configuration Tab    Install Tab    Archive Tab    Get IP Jobs Tab    LicenseTab    Copyright and Terms&Conditions