Re: JMAP support

[Tanstaafl]

Fyi, JMAP support is now officially on Thunderbirds roadmap for 2021...

Ok, I'll say it...

Pretty please?!

On 7/9/2019, 1:36:58 AM, Aki Tuomi via dovecot  wrote:
> No ETA yet.
> 
> Aki
> 
> On 7.7.2019 1.12, Martynas Bendorius via dovecot wrote:
>> Hello,
>>
>> Is there any ETA set for JMAP support?
>>
>> Thank you!
>>
 On 11/27/2016 5:28 AM, Aki Tuomi  wrote:
 Hi!
 We are working on including JMAP support to Dovecot. At this moment I 
 cannot give any promise for exact version, but hopefully it will be part 
 of v2.3

 Aki Tuomi
 Dovecot Oy
>> --
>> Best regards,
>> Martynas Bendorius
>>
>>
> 

Re: Apple mail works but thunderbird unable to connect

[Alexander Dalloz]

Am 23.06.2020 um 17:38 schrieb Dshah:

I disabled postscreen and enabled logging, I have all ports working except
993,  in log when I try to connect on port 993

dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>,
rip=10.244.0.24, lip=10.244.0.108, TLS handshaking: SSL_accept() failed:
error:1408F10B:SSL routines:ssl3_get_record:wrong version number,
session=

I found that I could disable ssl3 by "ssl_protocols = !SSLv2 !SSLv3" but
this option is not working (dovecot 2.3.10.1 (a3d0e1171)


Likely you have configured your mail client to issue a STARTTLS 
connection rather than a SSL one (implicit versue explicit SSL).


Port 143 -> STARTTLS
Port 993 -> SSL / TLS

Alexander

Re: Apple mail works but thunderbird unable to connect

[Alexander Dalloz]

Am 23.06.2020 um 11:25 schrieb Dshah:

Hi all,

First I would like to Thank you all, it is such a responsive and wonderful
community here.

I started to debug the issue by streaming logs and figured that EHLO was
being sent when I click "Re-Test" button on thunderbird, another issue I
encountered I was not able to connect ports 465/993, It was not blocked by
firewall cause I could see live streaming logs, I think it's more on
postfix side which I have sent for help.

here are my logs

https://pastebin.com/7xRHax4q


You issue has nothing to do with dovecot.

From the log it is to be seen that Postfix rejects the attempt on 
sumissions port 465 because from client side not SMTP AUTH info is being 
sent. Because you properly configured 
"smtpd_recipient_restrictions=permit_sasl_authenticated,reject" within 
Postfix's master.cf



and config ( postfix, dovecot)
https://pastebin.com/M3XG9DXA

In case someone could help, I can pay a small amount for figuring out this
issue.

Thanks again


Alexander

Re: Apple mail works but thunderbird unable to connect

[Dshah]

I disabled postscreen and enabled logging, I have all ports working except
993,  in log when I try to connect on port 993

dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>,
rip=10.244.0.24, lip=10.244.0.108, TLS handshaking: SSL_accept() failed:
error:1408F10B:SSL routines:ssl3_get_record:wrong version number,
session=

I found that I could disable ssl3 by "ssl_protocols = !SSLv2 !SSLv3" but
this option is not working (dovecot 2.3.10.1 (a3d0e1171)

On Tue, Jun 23, 2020 at 6:27 PM Michael Peddemors 
wrote:

> On 2020-06-23 8:24 a.m., Alexander Dalloz wrote:
> > Am 23.06.2020 um 07:33 schrieb Bernardo Reino:
> >> If you use postfix a "workaround" is to temporarily disable
> >> postscreen, which IIRC is the one (rightly) complaining about the
> >> improper pipelining.
> >>
> >> Cheers,
> >> Bernardo Reino
> >
> > No, submitting on SMTP port 25 would be the wrong step. There's
> > submission on port 587 or submissions (formerly called smtps) on port
> > 465 for taking MUA requests authenticating and submitting a message.
> >
> > Alexander
> >
>
> +1, you should even go farther and disable authentication on port 25
>
>
> --
> "Catch the Magic of Linux..."
> 
> Michael Peddemors, President/CEO LinuxMagic Inc.
> Visit us at http://www.linuxmagic.com @linuxmagic
> A Wizard IT Company - For More Info http://www.wizard.ca
> "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
> 
> 604-682-0300 Beautiful British Columbia, Canada
>
> This email and any electronic data contained are confidential and intended
> solely for the use of the individual or entity to which they are addressed.
> Please note that any views or opinions presented in this email are solely
> those of the author and are not intended to represent those of the company.
>

Re: Apple mail works but thunderbird unable to connect

[Michael Peddemors]

On 2020-06-23 8:24 a.m., Alexander Dalloz wrote:

Am 23.06.2020 um 07:33 schrieb Bernardo Reino:
If you use postfix a "workaround" is to temporarily disable 
postscreen, which IIRC is the one (rightly) complaining about the 
improper pipelining.


Cheers,
Bernardo Reino


No, submitting on SMTP port 25 would be the wrong step. There's 
submission on port 587 or submissions (formerly called smtps) on port 
465 for taking MUA requests authenticating and submitting a message.


Alexander



+1, you should even go farther and disable authentication on port 25


--
"Catch the Magic of Linux..."

Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.

Re: Apple mail works but thunderbird unable to connect

[Alexander Dalloz]

Am 23.06.2020 um 07:33 schrieb Bernardo Reino:
If you use postfix a "workaround" is to temporarily disable postscreen, 
which IIRC is the one (rightly) complaining about the improper pipelining.


Cheers,
Bernardo Reino


No, submitting on SMTP port 25 would be the wrong step. There's 
submission on port 587 or submissions (formerly called smtps) on port 
465 for taking MUA requests authenticating and submitting a message.


Alexander

Re: LMTP-Process stays in RCPT TO state

[Pascal Christen]

Hi Stephan

We tried it again last week with the latest dovecot version and still having 
the same issue. The whole setup works perfectly fine with the latest version of 
dovecot 2.2

The problem only exists if the quota of the user is full, every other message 
gets delivered without a problem, and the lmtp process change back to READY 
state. But in this case, it stays in the "RCPT TO” forever. I’ve talked to 
‘cmouse’ today on the IRC and he recommended continue here.

kdump and lmtp debug logs: https://pastebin.com/raw/MSVcj6qN 
 & And from the backend I only have a 
tcpdump from another process but it's always the same behaviour: 
https://pastebin.com/tVj842Dq 

If it doesn’t help, please let me know which logfiles exactly would help and 
would make the difference ;)

Greetings Pascal



> On 6 Dec 2019, at 21:26, Stephan Bosch via dovecot  
> wrote:
> 
> 
> 
> On 06/12/2019 11:08, Pascal Christen via dovecot wrote:
>> Hi
>> 
>> I tried to get some logs: https://pastebin.com/Z8xVzpzW
>> 
>> As you can see the process isn't shutdown and still in transaction as
>> long dovecot is running. It destroyed the transaction when I stopped
>> Dovecot. And this behavior only happens when the mailbox of user is full...
>> 
>> Any Ideas how to debug this correctly?
> 
> The provided logs look incomplete. The reception of the RCPT command by the 
> server-side is not in the log, only the generation of the response. Also much 
> of the client-side activity is not in the logs.
> 
> Also, a raw log of the TCP protocol exchange between Dovecot and Exim and 
> also between proxy and backend can be useful. If  the connections are 
> plaintext you can use wireshark or - if not - you can use the Dovecot rawlog 
> facilities.
> 
> Regards,
> 
> Stephan.
>>> So far, I haven't been able to reproduce anything weird at this end.
>>> Can you provide:
>>> 
>>> - Output from `dovecot -n'
>>> - Protocol logs from the connections between Exim and Dovecot
>>> director/proxy and between Dovecot director/proxy and Dovecot backend
>>> (e.g. using ngrep when connections are plaintext or using the rawlog
>>> facility).
>>> - Dovecot debug logs produced with `log_debug=category:lmtp' for both
>>> director/proxy and backend
>>> 
>>> Regards,
>>> 
>>> Stephan.
>>> 
>>> 
> 

problem with warnings

[Maciej Milaszewski]

Hi
I have a problem with warrnings in log

Yesterday "big gays" change datastore

and After this time i get warrnings in dovecot like:

Warning: Created dotlock file's timestamp is different than current time
(1592878268 vs 1592871191): /vmail/us/username/Maildir/dovecot-uidlist

Before that there was no problem with warnnings

I have dovecot director with 5 dovecot-nodes and storage always was
mounted via nfs

/vmail on /vmail type nfs
(rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.100.41,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=xxx.xxx.xxx.xxx)



# 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.24.rc1 (debaa297)
# OS: Linux 3.16.0-10-amd64 x86_64 Debian 8.11

Re: [EXT] Re: from field encoding

[Aki Tuomi]

Would it be possible at least to provide headers from such mail? Mostly I am 
interested in what content encodings are specified? You can remove 
sender/recipient/subject/message-id and such identifying information, but would 
prefer if you'd leave that ""Ing. Markéta Kleinová"' bit intact.

Aki


> On 23/06/2020 14:01 Jan Jurko  wrote:
> 
> 
> unfortunately im not authorized to publish the whole headers and content, but 
> as an example:
> 
> in headers:
> To:""Ing. Markéta Kleinová"' 
> 
> view in the webmail or outlook
> "Ing. Markéta Kleinová"
> 
> and it should be Ing. Markéta Kleinová
> 
> The problem is with From and To headers.
> 
> 
> 
> 
> 
> 
> > 23. 6. 2020 v 10:43, Aki Tuomi :
> > 
> > 
> > 
> > 
> > > On 23/06/2020 11:31 Jan Jurko  wrote:
> > > 
> > > 
> > > Good day.
> > > I have a dovecot 2.3.4.1 on debian 10 as an imap server. I found there 
> > > are emails where the header field From has no encoding even if there is a 
> > > name with special characters like Žlutý Kůň. The header looks like:
> > > 
> > > From: "Žlutý Kůň" 
> > > 
> > > In this case the email client - roundcube, outlook etc. will show the 
> > > From with wrong characters. This behaviour is typical only for dovecot, 
> > > not for courier-imap - it was installed before dovecot with no problems.
> > > 
> > > If there is corretly encoded From filed, the client shows the From 
> > > correctly.
> > > 
> > > Is there a way to set up the dovecot to show the field correctly even 
> > > without encoding stuff? Some default/fallback settings?
> > > 
> > > Thank you very much for your help
> > > 
> > > Jan Jurko
> > 
> > Is it possible to get a sample mail corpus?
> > 
> > Aki
>

dovecot fts configuration without solr

[Danilo Tomasoni]

Hello All, 


I always used dovecot and I'm pretty happy with it, but recently I
changed OS (to ubuntu 18) and to get dovecot LTS with lucene (the
default I was using on my previous arch installation) I needed to build
from source the version 2.3.10 (the one that came with the repos was
older and clucene was not actually supported) 


The problem is that the Clucene is not behaving well, It indexes only
some mails but definitely not all according to my tests (there are also
strange assertion errors in the logs) 


I also tried xapian fts index but is very slow indexing and definitely
doesn't seem to work. 


The problem with solr fts is that solr doesn't even start on my tiny
system (odroid C2 with 2GB RAM) 


and anyway I don't want to bloat all the system for the indexing if
possible.. 

Anyone can suggest me a proper minimal and working configuration? 

Thank you 


Danilo

Re: from field encoding

[Jan Jurko]

unfortunately im not authorized to publish the whole headers and content, but 
as an example:

in headers:
To: ""Ing. Markéta Kleinová"' 

view in the webmail or outlook
"Ing. Markéta Kleinová" 

and it should be Ing. Markéta Kleinová

The problem is with From and To headers.





> 23. 6. 2020 v 10:43, Aki Tuomi :
> 
> 
>> On 23/06/2020 11:31 Jan Jurko  wrote:
>> 
>> 
>> Good day.
>> I have a dovecot 2.3.4.1 on debian 10 as an imap server. I found there are 
>> emails where the header field From has no encoding even if there is a name 
>> with special characters like Žlutý Kůň. The header looks like:
>> 
>> From: "Žlutý Kůň" 
>> 
>> In this case the email client - roundcube, outlook etc. will show the From 
>> with wrong characters. This behaviour is typical only for dovecot, not for 
>> courier-imap - it was installed before dovecot with no problems.
>> 
>> If there is corretly encoded From filed, the client shows the From correctly.
>> 
>> Is there a way to set up the dovecot to show the field correctly even 
>> without encoding stuff? Some default/fallback settings?
>> 
>> Thank you very much for your help
>> 
>> Jan Jurko
> 
> Is it possible to get a sample mail corpus?
> 
> Aki



signature.asc
Description: Message signed with OpenPGP

Re: nodelay passdb extra field does not work?

[Joe Wong]

On Tue, Jun 23, 2020 at 5:23 PM Aki Tuomi 
wrote:

>
> > On 23/06/2020 12:19 Joe Wong  wrote:
> >
> >
> >
> >
> > On Tue, Jun 23, 2020 at 5:17 PM Aki Tuomi 
> wrote:
> > >
> > >  > On 23/06/2020 12:15 Joe Wong  wrote:
> > >  >
> > >  >
> > >  > Hello, I have added 'y' as nodelay in my passdb query and I see the
> following in log:
> > >  >
> > >  > dovecot: imap-login: Debug: Ignoring unknown passdb extra field:
> nodelay
> > >  >
> > >  > does it mean this option is no longer supported in 2.3.10 ?
> > >  >
> > >  > - Joe
> > >  >
> > >
> > >  It is supported in 2.3.10. The extra field is ignored by imap-login
> process.
> > >
> > >  Aki
> >
> > I see. how can I not to delay the login on failure condition ? I have
> specific needs for doing so.
>
> If you want it to work for unknown users as well, try adding this before
> other passdbs:
>
> passdb {
>   driver = static
>   args = noauthenticate nodelay
> }
>
> Aki
>

Thanks Aki, it works! :)

Re: Apple mail works but thunderbird unable to connect

[Dshah]

Hi all,

First I would like to Thank you all, it is such a responsive and wonderful
community here.

I started to debug the issue by streaming logs and figured that EHLO was
being sent when I click "Re-Test" button on thunderbird, another issue I
encountered I was not able to connect ports 465/993, It was not blocked by
firewall cause I could see live streaming logs, I think it's more on
postfix side which I have sent for help.

here are my logs

https://pastebin.com/7xRHax4q

and config ( postfix, dovecot)
https://pastebin.com/M3XG9DXA

In case someone could help, I can pay a small amount for figuring out this
issue.

Thanks again

On Tue, Jun 23, 2020 at 8:33 AM Bernardo Reino  wrote:

> On 22/06/2020 18:19, Dshah wrote:
>
> > I am stuck on this issue for days, I am able to connect on my IMAP
> > server using Apple mail client but thunderbird shows me this error:
> > "improper command pipelining after EHLO"
>
> The problem is, AFAIK, Thunderbird's autoconfiguration. It tries to
> detect your SMTP settings (note: SMTP, i.e. for mail sending, not for
> receiving, which would actually involve dovecot), but does it violating
> the protocol (does pipelining without waiting for confirmation).
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=832457
>
> The bug is old and considered to be resolved. And nobody cares :(
> If you use postfix a "workaround" is to temporarily disable postscreen,
> which IIRC is the one (rightly) complaining about the improper pipelining.
>
> Cheers,
> Bernardo Reino
>

Re: nodelay passdb extra field does not work?

[Aki Tuomi]

> On 23/06/2020 12:19 Joe Wong  wrote:
> 
> 
> 
> 
> On Tue, Jun 23, 2020 at 5:17 PM Aki Tuomi  wrote:
> > 
> >  > On 23/06/2020 12:15 Joe Wong  wrote:
> >  > 
> >  > 
> >  > Hello, I have added 'y' as nodelay in my passdb query and I see the 
> > following in log:
> >  > 
> >  > dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay
> >  > 
> >  > does it mean this option is no longer supported in 2.3.10 ?
> >  > 
> >  > - Joe
> >  >
> >  
> >  It is supported in 2.3.10. The extra field is ignored by imap-login 
> > process.
> >  
> >  Aki
> 
> I see. how can I not to delay the login on failure condition ? I have 
> specific needs for doing so.

If you want it to work for unknown users as well, try adding this before other 
passdbs:

passdb {
  driver = static
  args = noauthenticate nodelay
}

Aki

Re: nodelay passdb extra field does not work?

[Joe Wong]

On Tue, Jun 23, 2020 at 5:17 PM Aki Tuomi 
wrote:

>
> > On 23/06/2020 12:15 Joe Wong  wrote:
> >
> >
> > Hello, I have added 'y' as nodelay in my passdb query and I see the
> following in log:
> >
> > dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay
> >
> > does it mean this option is no longer supported in 2.3.10 ?
> >
> > - Joe
> >
>
> It is supported in 2.3.10. The extra field is ignored by imap-login
> process.
>
> Aki
>

I see. how can I not to delay the login on failure condition ? I have
specific needs for doing so.

Re: nodelay passdb extra field does not work?

[Aki Tuomi]

> On 23/06/2020 12:15 Joe Wong  wrote:
> 
> 
> Hello, I have added 'y' as nodelay in my passdb query and I see the following 
> in log:
> 
> dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay
> 
> does it mean this option is no longer supported in 2.3.10 ?
> 
> - Joe
>

It is supported in 2.3.10. The extra field is ignored by imap-login process.

Aki

nodelay passdb extra field does not work?

[Joe Wong]

Hello, I have added 'y' as nodelay in my passdb query and I see the
following in log:

dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay

does it mean this option is no longer supported in 2.3.10 ?

- Joe

Re: from field encoding

[Aki Tuomi]

> On 23/06/2020 11:31 Jan Jurko  wrote:
> 
>  
> Good day.
> I have a dovecot 2.3.4.1 on debian 10 as an imap server. I found there are 
> emails where the header field From has no encoding even if there is a name 
> with special characters like Žlutý Kůň. The header looks like:
> 
> From: "Žlutý Kůň" 
> 
> In this case the email client - roundcube, outlook etc. will show the From 
> with wrong characters. This behaviour is typical only for dovecot, not for 
> courier-imap - it was installed before dovecot with no problems.
> 
> If there is corretly encoded From filed, the client shows the From correctly.
> 
> Is there a way to set up the dovecot to show the field correctly even without 
> encoding stuff? Some default/fallback settings?
> 
> Thank you very much for your help
> 
> Jan Jurko

Is it possible to get a sample mail corpus?

Aki

from field encoding

[Jan Jurko]

 Good day.
I have a dovecot 2.3.4.1 on debian 10 as an imap server. I found there are 
emails where the header field From has no encoding even if there is a name with 
special characters like Žlutý Kůň. The header looks like:

From: "Žlutý Kůň" 

In this case the email client - roundcube, outlook etc. will show the From with 
wrong characters. This behaviour is typical only for dovecot, not for 
courier-imap - it was installed before dovecot with no problems.

If there is corretly encoded From filed, the client shows the From correctly.

Is there a way to set up the dovecot to show the field correctly even without 
encoding stuff? Some default/fallback settings?

Thank you very much for your help

Jan Jurko


signature.asc
Description: Message signed with OpenPGP