rust-opensmtpd/opensmtpd/Cargo.toml

[package]
name = "opensmtpd"
version = "0.2.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 = "5.0"
opensmtpd_derive = { path = "../opensmtpd-derive", version = "0.2" }

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

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

[[example]]
name = "counter"
path = "examples/report_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"`
Refactor the library Threads are a bad idea because for now the filter API is not guaranteed to be state-less. The interface is now synchronous, which should be enough for most filters. The refactoring brought other changes, the most important being the concept of modular input sources and output destination and the complete rewrite of the procedural macro. 2019-09-17 16:45:04 +02:00			`version = "0.2.0"`
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			`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"]}`
Upgrading to nom 5 2019-06-29 17:29:52 +02:00			`nom = "5.0"`
Refactor the library Threads are a bad idea because for now the filter API is not guaranteed to be state-less. The interface is now synchronous, which should be enough for most filters. The refactoring brought other changes, the most important being the concept of modular input sources and output destination and the complete rewrite of the procedural macro. 2019-09-17 16:45:04 +02:00			`opensmtpd_derive = { path = "../opensmtpd-derive", version = "0.2" }`
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
Add filter-level and session-level contexts 2019-09-18 20:43:46 +02:00			`[[example]]`
			`name = "hello"`
			`path = "examples/hello.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			`[[example]]`
Refactor the library Threads are a bad idea because for now the filter API is not guaranteed to be state-less. The interface is now synchronous, which should be enough for most filters. The refactoring brought other changes, the most important being the concept of modular input sources and output destination and the complete rewrite of the procedural macro. 2019-09-17 16:45:04 +02:00			`name = "echo"`
			`path = "examples/echo.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
Improve the simple_filter macro The simple_filter macro must accept the two different levels of contexts. In the same way, it should also accept the log level, and therefore replace the now removed simple_filter_log_level macro. 2019-09-18 14:52:21 +02:00			`[[example]]`
			`name = "counter"`
Add filter-level and session-level contexts 2019-09-18 20:43:46 +02:00			`path = "examples/report_counter.rs"`