dovecot-submission SMTP send error with Thunderbird (BODY=8BITMIME)

Hi, With latest 2.3 -git (and 2.3.0 release), I'm running into this error with Thunderbird: "An error occurred while sending mail. The mail server responded: 5.5.4 Unsupported mail BODY type. Please verify that your email address is correct in your account settings and try again." This is

ot: how to block persistent same invalid account, different IPs

"Voytek Eymont" I've installed fail2ban, it seems to be working as it identified my failed test logins, BUT, my question is: what can I do when I see same invalid name trying to login to dovecot, different IP each time, how can I say block each IP as used by this name ?

Re: Lua Auth

On Fri, Dec 22, 2017 at 5:18 AM, wrote: > > > On December 22, 2017 at 8:20 AM Mark Moseley > wrote: > > > > > > On Thu, Dec 21, 2017 at 9:51 PM, Aki Tuomi wrote: > > > > > > > > > On December 22, 2017 at 6:43 AM Mark Moseley

Re: ot: how to block persistent same invalid account, different IPs

On 2017-12-22 13:23, Jeff Abrahamson wrote: fail2ban isn't really the right tool to fight massive DDOS attacks.  On the other hand, you don't seem to have that problem, so things work out maybe. It's cleaner to know the future and ban the right things at the right times, but is there real harm

Re: Dovecot 2.3-rc1 SMTP submission proxy always gives TLS required error even when already using TLS

On 2017-12-22 11:22, Michael Marley wrote: > On 2017-12-21 16:48, Stephan Bosch wrote: > > Op 12/18/2017 om 9:44 PM schreef Michael Marley: > > First of all, I apologize for my accidental empty message earlier. > > I just set up the SMTP submission proxy in Dovecot 2.3, but whenever I > try

Re: Dovecot 2.3-rc1 SMTP submission proxy always gives TLS required error even when already using TLS

On 2017-12-21 16:48, Stephan Bosch wrote: > Op 12/18/2017 om 9:44 PM schreef Michael Marley: > >> First of all, I apologize for my accidental empty message earlier. >> >> I just set up the SMTP submission proxy in Dovecot 2.3, but whenever I >> try to connect to it, it always returns "530

Re: New Dovecot service: SMTP Submission (RFC6409)

On 22 Dec 2017, at 15.28, Tanstaafl wrote: > > On 12/22/2017, 1:19:45 AM, Aki Tuomi wrote: >> Tanstaafl, maybe you could explain what you think the BURL/URLAUTH >> stuff is for, or do you have some particular use case you would be using >> it?

v2.3.0 released

https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz.sig Some random notes: - This release is signed with a new PGP key 0x18A348AEED409DA1 (which is signed by the old key). - This fixes several compiling issues reported for the 2.3

Re: New Dovecot service: SMTP Submission (RFC6409)

On 12/22/2017, 1:19:45 AM, Aki Tuomi wrote: > Tanstaafl, maybe you could explain what you think the BURL/URLAUTH > stuff is for, or do you have some particular use case you would be using > it? Client support already is not required, and yes, it might take a > long time

Re: ot: how to block persistent same invalid account, different IPs

On 22/12/17 11:41, Voytek Eymont wrote: I've installed fail2ban, it seems to be working as it identified my failed test logins, BUT, my question is: what can I do when I see same invalid name trying to login to dovecot, different IP each time, how can I say block each IP as used by this name ?

Re: Lua Auth

> On December 22, 2017 at 8:20 AM Mark Moseley wrote: > > > On Thu, Dec 21, 2017 at 9:51 PM, Aki Tuomi wrote: > > > > > > On December 22, 2017 at 6:43 AM Mark Moseley > > wrote: > > > > > > > > > > > > > > > > > > > > > > >

Re: Fwd: v2.3.0 release candidate released

Sure: ./configure \ --with-pgsql \ --with-sql Two params I had once due to issues are not longer used: [ --with-ioloop=poll --with-notify=none ] Thanks and regards Goetz R. Schultz On 22/12/17 12:02, Odhiambo Washington wrote: > Okay, I was hoping it has something to do with

Re: Fwd: v2.3.0 release candidate released

Okay, I was hoping it has something to do with where I am stuck compiling. Could you kindly share your configure options? Mine which has always worked with Dovecot versions prior to 2.3 is refusing to work on FreeBSD i386. mv -f .deps/test_auth_cache-test-auth-cache.Tpo

Re: Fwd: v2.3.0 release candidate released

Hi Odhiambo, I referred to this: "Not looked yet, but is there a guide for the ssl_min_version setting? Seems only to wok when I set "SSLv3" which I really don't want." Have found literally 10 minutes after the post was send - so ignore that bit. It is just that error error that creeps up. But

Fwd: v2.3.0 release candidate released

Hi Goetz, I don't seem to understand what you mean by 'remove the last entry'. Do you mind clarifying please? On 18 December 2017 at 23:12, Goetz Schultz wrote: > Found the guide Can you remove last entry please ... works with TLSv1. > > > Thanks and regards > > Goetz

Re: v2.3.0 release candidate released

Found the guide Can you remove last entry please ... works with TLSv1. Thanks and regards Goetz R. Schultz On 18/12/17 20:05, Goetz Schultz wrote: > Hi > > From reeBSD 9.3-RELEASE amd64: > > Compiles ok > Installs ok > On startup 1: Error about new config settings (adjusted) > On

Re: v2.3.0 release candidate released

Hi From reeBSD 9.3-RELEASE amd64: Compiles ok Installs ok On startup 1: Error about new config settings (adjusted) On startup 2: doveadm(root): Error: net_connect_unix(/var/run/dovecot//stats-writer) failed: Connection refused It seems to work so far. I get messages from fetchmail being

ot: how to block persistent same invalid account, different IPs

I've installed fail2ban, it seems to be working as it identified my failed test logins, BUT, my question is: what can I do when I see same invalid name trying to login to dovecot, different IP each time, how can I say block each IP as used by this name ? or it that a bad idea ? I can see two