rust-opensmtpd/opensmtpd/Cargo.toml

[package]
name = "opensmtpd"
version = "0.1.0"
authors = ["Rodolphe Bréard <rodolphe@what.tf>"]
edition = "2018"
description = "Interface for OpenSMTPD filters"
keywords = ["opensmtpd", "filter", "mail"]
documentation = "https://docs.rs/opensmtpd/"
repository = "https://github.com/breard-r/rust-opensmtpd"
readme = "README.md"
license = "MIT OR Apache-2.0"
include = ["src/**/*", "Cargo.toml", "LICENSE-*.txt"]

[dependencies]
log = {version = "0.4", features = ["std"]}
nom = "4.1"
opensmtpd_derive = { path = "../opensmtpd-derive", version = "0.1" }

[[example]]
name = "dummy"
path = "examples/dummy.rs"

[[example]]
name = "counter"
path = "examples/session_event_counter.rs"
Use procedural macros to define events The construction of an EventHandler object should not be directly done by the client. Instead, it is easier to use procedural macro to automatize the process, hence exposing a nice and simple interface. Such use of procedural macros requires to crate an additional crate. 2019-01-06 15:41:30 +01:00			`[package]`
			`name = "opensmtpd"`
			`version = "0.1.0"`
			`authors = ["Rodolphe Bréard <rodolphe@what.tf>"]`
			`edition = "2018"`
			`description = "Interface for OpenSMTPD filters"`
			`keywords = ["opensmtpd", "filter", "mail"]`
			`documentation = "https://docs.rs/opensmtpd/"`
			`repository = "https://github.com/breard-r/rust-opensmtpd"`
			`readme = "README.md"`
Switch to the MIT or Apache 2.0 license 2019-01-18 19:08:40 +01:00			`license = "MIT OR Apache-2.0"`
			`include = ["src/*/", "Cargo.toml", "LICENSE-*.txt"]`
Use procedural macros to define events The construction of an EventHandler object should not be directly done by the client. Instead, it is easier to use procedural macro to automatize the process, hence exposing a nice and simple interface. Such use of procedural macros requires to crate an additional crate. 2019-01-06 15:41:30 +01:00
			`[dependencies]`
Add a logger OpenSMTPD plans to gather all logs from filters. Therefore, a default logger that implements the smtpd (future) log interface has to be available. 2019-01-17 19:53:04 +01:00			`log = {version = "0.4", features = ["std"]}`
Use procedural macros to define events The construction of an EventHandler object should not be directly done by the client. Instead, it is easier to use procedural macro to automatize the process, hence exposing a nice and simple interface. Such use of procedural macros requires to crate an additional crate. 2019-01-06 15:41:30 +01:00			`nom = "4.1"`
Add a logger OpenSMTPD plans to gather all logs from filters. Therefore, a default logger that implements the smtpd (future) log interface has to be available. 2019-01-17 19:53:04 +01:00			`opensmtpd_derive = { path = "../opensmtpd-derive", version = "0.1" }`
Use procedural macros to define events The construction of an EventHandler object should not be directly done by the client. Instead, it is easier to use procedural macro to automatize the process, hence exposing a nice and simple interface. Such use of procedural macros requires to crate an additional crate. 2019-01-06 15:41:30 +01:00
			`[[example]]`
			`name = "dummy"`
			`path = "examples/dummy.rs"`

Allow the use of custom context The main goal of events/reports is to update a context object, which will be used in filters to generate a response. It is now possible to use any object implementing both Clone and Default as a context object. It is also possible to define no context at all. 2019-01-12 23:43:02 +01:00			`[[example]]`
			`name = "counter"`
			`path = "examples/session_event_counter.rs"`