@@ -37,7 +37,7 @@ introduction by the new developers/contributors. It is recommended to read
3737user documentation to understand how things work from the user perspective as
3838well.
3939
40- - User documentation: [ maddy.conf(5)] ( maddy.conf .5.scd )
40+ - User documentation: [ maddy.conf(5)] ( docs/man/ maddy.5.scd)
4141- Design rationale: [ Comments on design (Wiki)] [ 1 ]
4242
4343There are components called "modules". They are represented by objects
@@ -63,7 +63,7 @@ initialization path, so they are always initialized directly.
6363
6464## Error handling
6565
66- Familiarize yourself with the ` github.com/foxcpp/maddy/internal /exterrors `
66+ Familiarize yourself with the ` github.com/foxcpp/maddy/framework /exterrors `
6767package and make sure you have the following for returned errors:
6868- SMTP status information (smtp\_ code, smtp\_ enchcode, smtp\_ msg fields)
6969 - SMTP message text should contain a generic description of the error
@@ -109,7 +109,7 @@ If you don't need any per-message state, you can use `StatelessCheck` wrapper.
109109See ` check/dns ` directory for a working example.
110110
111111Here are some guidelines to make sure your check works well:
112- - RTFM, docs well tell you about any caveats.
112+ - RTFM, docs will tell you about any caveats.
113113- Don't share any state _ between_ messages, your code will be executed in
114114 parallel.
115115- Use ` github.com/foxcpp/maddy/check.FailAction ` to select behavior on check
0 commit comments