[snip]
Don't expect it to send mime attachments though.
(And in case you get the attachments working, please let me know
Hi Gerard. Are you saying that Blat doesn't have the feature to send mime
attachments? Or are you saying that feature is broke for some reason? If the
former, blat's help says it sends mime.
Rach
-------
Blat v2.1.0 (build : Jul 22 2003 21:32:48)
Win32 console utility to send mail via SMTP or post to usenet via NNTP
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 -install <server addr> <sender's addr> [<try>[<port>[<profile>]]]
[-q]
Blat -profile [-delete | "<default>"] [profile1] [profileN] [-q]
Blat -h
--------------------------------
Installation ---------------------------------
-install[SMTP|NNTP] <server addr> <sender's addr> [<try n times> [<port>
[<profile> [<username> [<password>]]]]]
: set's server, sender, number of tries and port for profile
(<try n times> and <port> may be replaced by '-')
port defaults are SMTP=25, NNTP=119
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
--------------------------------- The
Basics ----------------------------------
<filename> : file with the message body ('-' for console input, ^Z
ends)
-of <filename> : text file containing more options (also -optionfile)
-to <recipient> : recipient list (also -t) (comma separated)
-tf <recipient> : 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 -bcc)
(comma separated)
-bf <file> : bcc recipient list filename
-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
-body <text> : message body, surround with quotes to include spaces
-sig <filename> : text file containing your email signature
-tag <filename> : text file containing taglines, to be randomly chosen
-ps <filename> : final message text, possibly for unsubscribe instructions
----------------------------- Registry
overrides ------------------------------
-p <profile> : send with server, user, and port defined in <profile>
: use username and password if defined in <profile>
-profile : list all the profiles in the Registry
-server <addr> : specify SMTP server to be used (optionally, addr
ort)
-serverSMTP <addr>
: same as -server
-serverNNTP <addr>
: specify NNTP server to be used (optionally, addr
ort)
-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)
-u <username> : username for AUTH LOGIN (use with -pw)
-pw <password> : password for AUTH LOGIN (use with -u)
---------------------- Miscellaneous RFC header
switches ----------------------
-organization <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
----------------------- Attachment and encoding
options -----------------------
-attach <file> : attach binary file(s) to message (comma separated)
-attacht <file> : attach text file(s) to message (comma separated)
-embed <file> : embed file(s) in HTML. Object tag in HTML must specify
content-id using cid: tag. eg: <img src="cid:image.jpg">
-base64 : send binary files using base64 (binary MIME)
-uuencode : send binary files UUEncoded
-enriched : send an enriched text message (Content-Type=text/enriched)
-html : send an HTML message (Content-Type=text/html)
-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
---------------------------- NNTP specific
options ----------------------------
-groups <usenet groups>
: list of newsgroups (comma separated)
-------------------------------- Other
options --------------------------------
-h : displays this help
-q : suppresses *all* output
-debug : echoes server communications to screen
-log <filename> : log everything but usage to <filename>
-timestamp : when -log is used, a timestamp is added to each log line
-ti <n> : set timeout to 'n' seconds. Blat will wait 'n' seconds
for
server responses
-try <n times> : how many times blat should try to send (1 to 'INFINITE')
-binary : do not convert ASCII | (pipe, 0x7c) to CrLf in the message
body
-hostname <hst> : select the hostname used to send the message via SMTP
this is typically your local machine name
----------------------------------------------------------------------------
---
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 -i
options:
-mailfrom <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.
