search for: submissiond

..., Admin Beckspaced wrote: > If postfix is handling your submission service you can have a look at > postfwd > > https://www.postfwd.org/ > > I use it to limit sending of emails, recipients, etc, etc Thanks for the suggestion! I am using Postfix as the relay host behind dovecot-submissiond. Unfortunately, unless I'm missing something, submissiond does not seem to be able to add the SASL username to the message headers, so I don't have a good way to distinguish sending users on the relay server. Cheers, Gerry

For reasons of user privacy and security I usually configure submission servers to not include accurate IP address and HELO information of authenticated users. (Usually replacing it with a private-use domain / IPv6 address.) Dovecot submission (2.3.2) will produce a header something like this (where ?10.22.36.10" is a public IP address) Received: from [192.168.1.184] ([10.22.36.10]) by

Hello, I am trying to come up with a way to have individual quotas per user for the submission service. Similar to what I could achieve with Postfix and policyd. More specifically, the quota I am most interested in, is limiting the number of messages a single account can send within a given timeframe. Ideally, I'd also like to limit the number of total recipients within a given timeframe, to

...apply to submission, unless you're doing protocol-specific things, in which case you may need to amend your configuration for the new protocol. BURL support requires a working IMAP URLAUTH implementation. I've updated the automated Xi Debian package builder to create an additional dovecot-submissiond package. So, if you're using the Xi packages, you only need to install that package and configure the relay MTA. Regards, Stephan.

...> you're doing protocol-specific things, in which case you may need to > amend your configuration for the new protocol. BURL support requires a > working IMAP URLAUTH implementation. > > I've updated the automated Xi Debian package builder to create an > additional dovecot-submissiond package. So, if you're using the Xi > packages, you only need to install that package and configure the relay MTA. > > Regards, > > Stephan. > > > > >

...gt; you're doing protocol-specific things, in which case you may need to > amend your configuration for the new protocol. BURL support requires a > working IMAP URLAUTH implementation. > > I've updated the automated Xi Debian package builder to create an > additional dovecot-submissiond package. So, if you're using the Xi > packages, you only need to install that package and configure the relay MTA.

...ed.gpg.d/dovecot.gpg && \ echo "deb https://repo.dovecot.org/ce-2.3-latest/ubuntu/bionic bionic main" > /etc/apt/sources.list.d/dovecot.list && \ apt-get update && \ bash -c "apt-get install -y dovecot-{core,imapd,sqlite,managesieved,sieve,pop3d,lmtpd,submissiond,lua} lua-socket" CMD [ "/usr/sbin/dovecot","-F","-c","/etc/dovecot/dovecot.conf" ] I had to install lua-socket, which is used by the example script and not required by dovecot-lua, which is ok, you just need to know. Using Aki's code snippet as use...

...g protocol-specific things, in which case you may need to >> amend your configuration for the new protocol. BURL support requires a >> working IMAP URLAUTH implementation. >> >> I've updated the automated Xi Debian package builder to create an >> additional dovecot-submissiond package. So, if you're using the Xi >> packages, you only need to install that package and configure the relay MTA.

...<none> pn dovecot-managesieved <none> pn dovecot-mysql <none> pn dovecot-pgsql <none> pn dovecot-pop3d <none> pn dovecot-sieve <none> pn dovecot-solr <none> pn dovecot-sqlite <none> pn dovecot-submissiond <none> ii ntp 1:4.2.8p12+dfsg-4 Versions of packages dovecot-core is related to: ii dovecot-core [dovecot-common] 1:2.3.4.1-5+deb10u1 pn dovecot-dev <none> pn dovecot-gssapi <none> pn dovecot-imapd <...

Thanks Aki, I'll check it out :) Am 03.08.20 um 11:40 schrieb Aki Tuomi: >> On 03/08/2020 12:31 Ralf Becker <rb at egroupware.org> wrote: >> >> >> We're currently using the OX push driver, which is straight forward >> (simple web hook) and allows to store (multiple) push tokens of our >> webmailer direct in mailbox metadata. >> >>