similar to: submission_host auth

> When using dovecot container with sieve plugin there is no sendmail to use for sending email for sieve redirect action for example. We can use submission_host instead https://doc.dovecot.org/settings/core/#core_setting-submission_host but there is no way to specify credentials for auth in remote MTA. Submission_relay_* settings e.g. submission_relay_master_user relate to dovecot submission

Thanks for the reply, postfix + dovecot sasl configured and working properly. My question is about "adding dovecot authentication when sending emails via submission_host". Let's say we have dovecot + sieve plugin container. Dovecot configured to use remote SMTP submission host to send messages: submission_host = postfix.example.com:587 User foo at example.com has the following

> Let's say we have dovecot + sieve plugin container. > Dovecot configured to use remote SMTP submission host to send messages: > submission_host = postfix.example.com:587 I reviewed my config to see how i did it. I think you are right and SASL isn't used here. I have dovecot and postfix on the same machine and in dovecot i set submission_host = localhost:25 Then in my

Hello dovecot-users, I have a question/suggestion regarding the submission_host feature of the lda (either via dovecot-lda binary or lmtp) in combination with sieve. When trying to deliver message to a mailbox and this message has a sieve redirect action applied to it, dovecot is using the configured smtp server to forward the message just fine. Unfortunately, if the server configured for

15-lda.conf: submission_host = 192.168.m.n:587 2011-03-21T14:43:49+01:00 prac/p-prac dovecot: [ID 583609 mail.debug] lmtp(12354, user at us.edu.pl): Debug: mcQ1NitVh01CMAAAuqlTtQ: sieve: executing script from /mails/sieve/user at us.edu.pl.svbin 2011-03-21T14:43:49+01:00 prac/p-prac dovecot: [ID 583609 mail.error] lmtp(12354, user at us.edu.pl): Error: smtp(192.168.m.n:587): RCPT TO failed:

director_mail_servers setting uses IP Adresses as values https://doc.dovecot.org/settings/core/#core_setting-director_mail_servers As described in the documentation, hostnames are converted to addresses when the configuration is read https://doc.dovecot.org/settings/types/#ip-addresses This is acceptable in host or virtual machine environment, but becomes a problem in a containerized environment.

Hello, I configured dovecot to use submission smtp host becouse of chroot. submission_host = 127.0.0.1 Unfortunatelly: Nov 12 05:11:15 myhost exim[23366]: 2011-11-12 05:11:15 SMTP protocol synchronization error (next input sent too soon: pipelining was not advertised): rejected "EHLO myhost" H=localhost [127.0.0.1] next input="MAIL FROM:<root at myhost>\\r\\n" Nov 12

Hello all, I'm attempting to implement a submission server with questions in regards to how Dovecot handles the backend hosts capabilities. To my understanding, Dovecot will connect to the host specified in either submission_host or submission_relay_host, and gather a list of capabilities. Once gathered, after the client sends the EHLO greeting Dovecot will respond back with capabilities

Op 1/6/2018 om 7:42 PM schreef Florian Pritz: > On 03.01.2018 18:14, Tony wrote: >> I downgraded dovecot to 2.2.33.2 and pigeonhole 0.4.21 and can confirm >> the reported problem does not exist with "permission denied" and >> sendmail getting hung up/timing out. > The issue is that sendmail/maildrop/postdrop uses setgid to change to > the maildrop group

Hi to all, i have dovecot 2.2.5 and i have implemented lda rejection through quota full this is my dovecot conf protocol lda { mail_fsync = optimized auth_socket_path = /usr/local/var/run/dovecot/auth-userdb deliver_log_format = msgid=<%f>-<%s>-%m: %$ hostname = mail.cgilfe.it info_log_path = /var/log/dovecot/dovecot-deliver.log log_path =

Hi everyone, I'm facing a small issue with the lda/lmtp "submission_host" feature in dovecot 2.0.14. When sending mail to MTA (in case of sieve filter forwarding for example), dovecot pass a RCPT TO command just after the EHLO. He's missing the MAIL FROM command. Therefore, my MTA show me a warning like this : "improper command pipelining after EHLO". How can i

Hello, I'm having trouble configuring the submission proxy. I have configured the submission service as follow: submission_host = smtp.example.com submission_relay_host = localhost submission_relay_port = 8587 submission_relay_rawlog_dir = /var/log/dovecot/ submission_relay_trusted = yes My main issue is that until I login, dovecot-submission won't connect to the backend and query the

> Le 27 juil. 2019 ? 14:30, Stephan Bosch <stephan at rename-it.nl> a ?crit : > > On 23/07/2019 17:13, Jean-Daniel Dupas via dovecot wrote: >> Hello, >> >> I'm having trouble configuring the submission proxy. >> >> I have configured the submission service as follow: >> >> submission_host = smtp.example.com >>

Op 28-1-2020 om 19:20 schreef azurit at pobox.sk: > Really no more info? You could do something with the sendmail_path or submission_host settings. Regards, Stephan. > > > > > Cit?t azurit at pobox.sk: > >> Thanks for idea but it won't work for me as 'internal domains' can be >> anything, including gmail.com (and i don't know which of them are

Hi Jacky, in postfix/main.cf you typically set something like smtpd_sasl_auth_enable=yes smtpd_sasl_type=cyrus smtpd_sasl_exceptions_networks=$mynetworks smtpd_sasl_security_options=noanonymous smtpd_sasl_authenticated_header=yes broken_sasl_auth_clients=yes smtpd_recipient_restrictions=permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination smtpd_recipient_restrictions might

Hi, We have mail server in production, with Exim + Dovecot + Mailman + OpenLDAP + Roundcube webmail server. Openldap keeps mail accounts in db, exim uses lmtp transport to deliver messages to dovecot. Mailman is responsible for mailing lists, Roundcube webmail has managsieve module to create sieve filters. Exim router,transport for dovecot > localuser: > driver = accept > domains =

I'm using dovecot in a multi server setup. Two directors forward pop3, imap and smtp to backend dovecots with their central storage on NFS. Yesterday I stumbled upon these log lines: 2019-11-18 20:17:51 lmtp(17274): Info: Connect from 172.22.1.6 2019-11-18 20:17:51 lmtp(17274): Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established): assertion failed:

Hi, I have just updated from Ubuntu 15.04 to 15.10. Unfortunately, sieve scripts are not recognized anymore. Here is my version: > dovecot --version > 2.2.18 > apt-cache policy dovecot-sieve > dovecot-sieve: > Installed: 1:2.2.18-2ubuntu2 > Candidate: 1:2.2.18-2ubuntu2 > Version table: > *** 1:2.2.18-2ubuntu2 0 > 500 http://us.archive.ubuntu.com/ubuntu/

adding a second, non-redirect action to the sieve rule in order to test, + require ["copy","fileinto"]; # rule:[SIEVETEST] if header :contains "subject" "SIEVETEST" { + fileinto :copy "testing"; redirect "user2 at example2.com"; } on send exec, the 'fileinto' action does work as expected. the 'redirect' fails

Hello mailing list subscribers! When I delete a message in Mac Mail 6.5 (OS X 10.8.4), with the option to move messages to the trash set in Mac Mail account preferences, the message is copied to the trash, and markes as trashed in the cur/inbox directory on the server (STa flag in the file name). My horde webmail then displays this messages correctly as trashed in the inbox. However, I want the