The Java submission binding is the second of five in the chapter: pmta.jar is added to the classpath, and for working through JavaMail the supplied javamail.providers file is installed.
The description is in JavaDoc format: on Linux — /opt/pmta/api/java/doc/javadoc/index.html, on Windows — the pmtajavadoc.zip archive in the api\java folder. Java 6 or later is required, and for JavaMail also the JavaMail and Java Activation Framework libraries.
The JavaMail provider is the main convenience: an application written for JavaMail can submit through the node without being rewritten for the binding’s own interface.
What is where:
| What | Where |
|---|---|
| library | pmta.jar in the classpath |
| working through JavaMail | the javamail.providers file |
| description on Linux | /opt/pmta/api/java/doc/javadoc/index.html |
| description on Windows | pmtajavadoc.zip in api\java |
| version | Java 6 and later |
# add the binding library when starting the application java -cp pmta.jar:app.jar com.example.Sender
1 relation
ls /opt/pmta/api/java/doc/javadoc/index.html
3 articles
◇How a message gets into the engineSix described submission methods: extended SMTP, four language bindings and a directory the node watches on disk.◇Who is allowed to submit mail and for whom to accept itOut of the box, the node accepts submission only from the machine itself; two different questions — “who can send through us” and “for whose addresses we accept mail” — are answered by different directives.◇Headers the sender uses to control deliverySix control headers let the submitting side choose a stream, tag a message with a job, set signing options and the key, the envelope identifier and the schedule; each is allowed separately and per source.