...
 
Commits (2)
  • Alberto Bertogli's avatar
    docs: Add a section on dovecot auth troubleshooting · fcbd20cd
    Alberto Bertogli authored
    This patch adds a section on dovecot authentication troubleshooting,
    with common suggestions that can help identify what is going on when
    the chasquid-dovecot interaction isn't working as expected.
    fcbd20cd
  • Alberto Bertogli's avatar
    smtpsrv: Don't consider client EOF an error · c8fbf2ec
    Alberto Bertogli authored
    When the client closes the connection, which is very common, chasquid
    logs it as an error ("exiting with error: EOF").
    
    That can be confusing and mislead users, and also makes a lot of
    traces be marked as errored, when nothing wrong occurred.
    
    So this patch changes the log to not treat it as an error.
    c8fbf2ec
......@@ -51,5 +51,23 @@ If chasquid can't find them, the paths can be set with the
`dovecot_userdb_path` and `dovecot_client_path` options.
## Troubleshooting
Dovecot authentication can be tricky to troubleshoot.
If you think it is not working as it should, or chasquid isn't correctly
talking with it, the easiest way to check is to [increase dovecot auth logging
verbosity](https://doc.dovecot.org/admin_manual/logging/?highlight=logging#logging-verbosity):
```
auth_verbose = yes
auth_debug = yes
```
One common gotcha is when dovecot is set up to use `user` instead of
`[email protected]`. In that case you can try setting `auth_username_format = %n` to
make it ignore the domain if present.
[dovecot]: https://dovecot.org
[chasquid]: https://blitiri.com.ar/p/chasquid
......@@ -280,7 +280,11 @@ loop:
}
if err != nil {
c.tr.Errorf("exiting with error: %v", err)
if err == io.EOF {
c.tr.Debugf("client closed the connection")
} else {
c.tr.Errorf("exiting with error: %v", err)
}
}
}
......