Re: Health check curl example

2019-11-25 Thread Markus Valentin via dovecot
Hi, you can use telnet or netcat to send input to that port and receive the answer. echo "PING" | nc localhost 5001 Best regards Markus On 11/24/19 2:43 PM, Marc Roos via dovecot wrote: > > How do I check the standard script then on this port 5001 from the > command line? > > > This one

RE: Health check curl example

2019-11-25 Thread Marc Roos via dovecot
Thanks, Markus, maybe we should add this to the admin_manual? However I am now getting the error 'script: Fatal: Missing script path' Similar as when I try via the command line bash-5.0# /usr/libexec/dovecot/script -e /bin/health-check.sh Fatal: Missing script path bash-5.0# /usr/libexec/dov

RE: Health check curl example

2019-11-25 Thread Markus Valentin via dovecot
The -e parameter is used to define a "list of environment variables", so the error message telling you that you did not define a script is right. So far i understood that you wanted to use passthrough mode, so do not use -e but -p. (except you need to define some environment-variables for your

RE: proxy dual server setup clarification

2019-11-25 Thread Marc Roos via dovecot
Hi Sami, I have this proxy on pop3/imap working however, I can't get this lmtp to work. In theory only these configuration changes, should allow messages to be directed for account: test to server svr1 not? lmtp_proxy = yes protocol lmtp { # Space separated list of plugins to load (defaul

RE: Health check curl example

2019-11-25 Thread Marc Roos via dovecot
:) I really starting to feel a bit like an idiot, but all these 3 configs[0] give error 'Client not compatible with this binary' [0] service health-check { executable = script /bin/health-check.sh inet_listener health-check { port = 5001 } } service health-check { executable = sc

Lmtp logging, does not log

2019-11-25 Thread Marc Roos via dovecot
Looks like dovecot is not sending stuff to syslog anymore I am getting some message in /tmp/dovecot.log. However the lmtp log files are not even created. bash-5.0# doveconf | grep log_ auth_policy_log_only = no debug_log_path = deliver_log_format = msgid=%m: %$ doveadm_http_rawlog_dir = imapc_

RE: Health check curl example

2019-11-25 Thread Markus Valentin via dovecot
No worries. Now you are not using the passthrough(-p) mode. That is why dovecot is telling you that your client is not compatible. Using "script" without -p would require you to implement that protocol: http://doc.dovecot.org/admin_manual/health_check.html#script-protocol. I believe all you wan

RE: Health check curl example

2019-11-25 Thread Marc Roos via dovecot
I can't yet use -p, the version I have is not supporting it still :( Maybe it is better to wait until alpine linux updates the package. -Original Message- Subject: RE: Health check curl example No worries. Now you are not using the passthrough(-p) mode. That is why dovecot is telli

RE: Health check curl example

2019-11-25 Thread Markus Valentin via dovecot
Ah right i did not see that. The minimal equivalent call for the normal script mode would be: echo "VERSION\tscript\t4\t0\nnoreply\n\nPING\n" | nc 127.0.0.1 5001 > On November 25, 2019 1:30 PM Marc Roos via dovecot > wrote: > > > I can't yet use -p, the version I have is not supporting it

Accessing the -a and -d from dovecot-lda

2019-11-25 Thread Aristedes Maniatis via dovecot
I've got exim set up to deliver like this: command = /usr/local/libexec/dovecot/dovecot-lda -a $original_local_part@$original_domain -d $local_part@$domain -f $sender_address If an email to is bob+sa...@ish.com.au then we should have "-a bob+sa...@subdomain.ish.com.au -d b...@ish.com.au".