Does Chasquid support Sieve "vacation" extension?

[eubyte]

I looks like it does NOT. If it does, how do we enable 'reply delivery' at the MTA level?

Best!

[Alberto Bertogli]

On Fri, Jan 24, 2020 at 04:28:15PM -0800, eubyte wrote:
>I looks like it does NOT. If it does, how do we enable 'reply delivery' at
>the MTA level?

chasquid is independent from sieve and any vacation extensions, so in
theory they should work.

Looking a bit into it, I don't see them requiring anything specific from
the MTA. Maybe the sieve module is trying to send from=<> to=<someone
outside the local domain> and chasquid is rejecting that? If so, that
can be solved by the sieve sender authenticating to chasquid first.


If you have more details about the scenario, like an example of a
deployment where it isn't working for a particular reason, please let me
know and I'm happy to look into it.

Thanks,
Alberto

[eubyte]

Looking at the mail error logs we find the following error whenever Sieve is trying to send an auto-reply/vacation message.

Fatal: execvp(/usr/sbin/sendmail) failed: No such file or directory

I know that Postfix provides some sort of wrapper for the Sendmail binary. What about chasquid? Creating a simple symlink does not solve the issue. All other Sieve filters (that do not require outgoing messages) are working fine.

Any ideas are appreciated.

Thank you!

[Alberto Bertogli]

On Fri, Feb 12, 2021 at 12:21:58PM -0800, eubyte wrote:
>Looking at the mail error logs we find the following error whenever Sieve
>is trying to send an auto-reply/vacation message.
>
>Fatal: execvp(/usr/sbin/sendmail) failed: No such file or directory
>
>I know that Postfix provides some sort of wrapper for the Sendmail binary.
>What about chasquid? Creating a simple symlink does not solve the issue.

chasquid doesn't provide a /usr/sbin/sendmail wrapper.

My suggestion is to use either msmtp (in Debian, msmtp-mta) or ssmtp for
this.

You can create a chasquid user for local sending, and then configure
msmtp/ssmtp to send via localhost and authenticate as that user.

They both provide a sendmail-compatible interface, are well tested, and
can work with chasquid just fine for sending email locally.

Let me know if this works or you run into any other issue!

Thanks,
Alberto

[Alberto Bertogli]

On Sat, Feb 13, 2021 at 11:22:47AM -0800, eubyte wrote:
>Thank you for the great suggestion, and it almost solved the issue. Our
>setup has virtual users with Dovecot for multiple domains. When we
>configure msmtp-mta with a system-wide account that calls the server's own
>smtp via FQDN -- everything works. But unfortunately, we are not able to
>configure via localhost. Is there something obvious we are missing? Do you
>have a msmtp-mta config example by any chance? Should we add a chasquid
>user with chasquid-util user-add? Thank you again for all your help.

chasquid has (intentionally) no special provisions for localhost, so you
need to send email just like from an off-host connection.

So yes, you need to add a user to auth on with `chasquid-util user-add`,
and then use it to send emails.

This is an example msmtprc I just made, I didn't test it but it is based
on others I used, hopefully it helps as a basis:

```
account default

# The server is on localhost.
host localhost

# Don't check TLS certificate validation on a localhost connection.
# This is needed because chasquid won't take authentication over
# non-encrypted connections, and "host localhost" will prevent proper
# certificate validation on the client side, since the certificates
# offered will not be for "localhost" but for the named domains.
tls_certcheck off

# Log attempts to syslog.
syslog on

# Always auth as localsender.
auth on
user localsender@yourdomain
password yourpassword

# Let it build the "from" automatically from the running user.
auto_from on
maildomain yourdomain
```

I hope this helps!

Thanks,
Alberto