java zinger.mailer.Main [ ]+ <
properties file: SMTP properties file. Here's an example of a minimal configuration:
mail.user=alexey@cyclepages.com
mail.password=xxx
mail.smtp.auth=true
mail.smtp.host=mail.cyclepages.com
mail.from=alexey@cyclepages.com
Note: mail.smtp.auth is an almost undocumented "feature" of Java Mail that causes it to use authentication. If that property is not present or turned off, Java Mail won't attempt to authenticate its SMTP connections and therefore will be at the mercy of the SMTP server as to what it will be allowed to do (usually it ends up being only sending mail within the domain of the SMTP server).
Another thing to note here is that ZMailer backs up the properties read from the properties file with system properties. Therefore the properties file can be incomplete and the rest of the properties can be provided (or overriden) with normal Java -D options, a la:
java "-Dmail.from=joe@acme.com" zinger.mailer.Main mail.properties "I like you!" "mary@acme.com" < msg.txt
message file: a file containing the message body to be sent. For some reason, the way Java Mail is invoked by ZMailer, it will include all message headers in the message body it sends unless the file starts with a blank line. Of course, message body doesn't have to come from a file -- ZMailer simply reads it from STDIN. First blank line rule applies nevertheless though.
adressee: should be self-explanatory. The only potential point of interest is that multiple adressees can be given by providing as many of them as you want, each one as its own command line parameter. At least one has to be specified. ZMailer currently does not support "Cc:" or "Bcc:" adressees.
Most of the command line parameters here may require special characters, such as '@' and white spaces, so it's a good idea to wrap each parameter in quotes for good measure.
(
geocities.com/inline_four/java) (
geocities.com/inline_four)