Re: managesieve server not answering?

[joe a]

On 1/21/2024 19:00:28, Benny Pedersen wrote:

joe a skrev den 2024-01-21 22:20:


Now, where are my notes? . . . oh, right, my bad.


check the maillist then :=)

protocols = imap lmtp

add sieve there

more help then i need "netstat -natpu | grep dovecot" output

tux ~ # netstat -natpu | grep dovecot
tcp    0  0 0.0.0.0:993 0.0.0.0:* LISTEN  
3554/dovecot
tcp    0  0 127.0.0.1:12340 0.0.0.0:* LISTEN  
3554/dovecot
tcp    0  0 127.0.0.1:24    0.0.0.0:* LISTEN  
3554/dovecot
tcp    0  0 127.0.0.1:143   0.0.0.0:* LISTEN  
3554/dovecot
tcp    0  0 127.0.0.1:4190  0.0.0.0:* LISTEN  
3554/dovecot


from my own tux, i love it :)

note all the love to 127.0.0.1


___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org



No netstat here only ss.  But similar options it seems.  Only port 143 
is bound to dovecot.



___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: "Connection reset by peer" errors with Outlook

[Benny Pedersen]

Steve Dondley via dovecot skrev den 2024-01-22 02:18:
I have a mail server using dovecot that has  been running without issue 
for quite a couple of years now. It serves email for about 30 
individuals.


But since Jan 14th, users have been reporting spurious errors in MS 
Outlook:


  324 Jan 21 00:38:17 ip-172-30-0-131 dovecot: pop3-login: Disconnected 
(no auth attempts in 0 secs): user=<>, rip=118.xxx.xxx.xxx, 
lip=172.30.0.131, TLS handshaking: read(size=596) failed: Connection 
reset by peer, session=


there is no user in the above line


Some characteristics of the problem that may offer a clue:

* happening with multiple users, not just the same one
* happens from different IP addresses.


bots detected

* happens about 3 to 5 times per day and the errors come in batches 
like above

* MS Outlook error is:


why is it a microsoft problem now ?

reported error (0x80042109): ‘Outlook cannot conect to your outgoing 
SMTP email server. If you continue to receive this message….blah blah 
blah


disable pop3 in dovecot, problem is then gone


I googled the error code but didn’t find anything particularly helpful.


we all use minimal tls1.2, the bots still use ssl, with username fails


I’m running Debian bullseye, version 11.8.


irelevant info

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

"Connection reset by peer" errors with Outlook

[Steve Dondley via dovecot]

I have a mail server using dovecot that has  been running without issue for 
quite a couple of years now. It serves email for about 30 individuals.

But since Jan 14th, users have been reporting spurious errors in MS Outlook:

  316 Jan 21 00:38:12 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 1 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=783) failed: Connection reset by peer, 
session=
  317 Jan 21 00:38:12 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 0 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=598) failed: Connection reset by peer, 
session=
  318 Jan 21 00:38:13 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 0 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=598) failed: Connection reset by peer, 
session=<9rWIHm4PtuF2wSuN>
  319 Jan 21 00:38:13 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 0 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=677) failed: Connection reset by peer, 
session=
  320 Jan 21 00:38:14 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 0 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=691) failed: Connection reset by peer, 
session=
  321 Jan 21 00:38:15 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 1 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=610) failed: Connection reset by peer, 
session=
  322 Jan 21 00:38:16 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 1 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=609) failed: Connection reset by peer, 
session=
  323 Jan 21 00:38:16 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 0 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=596) failed: Connection reset by peer, 
session=
  324 Jan 21 00:38:17 ip-172-30-0-131 dovecot: pop3-login: Disconnected (no 
auth attempts in 0 secs): user=<>, rip=118.xxx.xxx.xxx, lip=172.30.0.131, TLS 
handshaking: read(size=596) failed: Connection reset by peer, 
session=


Some characteristics of the problem that may offer a clue:

* happening with multiple users, not just the same one
* happens from different IP addresses. 
* happens about 3 to 5 times per day and the errors come in batches like above
* MS Outlook error is: 

reported error (0x80042109): ‘Outlook cannot conect to your outgoing SMTP email 
server. If you continue to receive this message….blah blah blah

I googled the error code but didn’t find anything particularly helpful. 

I’m running Debian bullseye, version 11.8. 




___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[Benny Pedersen]

joe a skrev den 2024-01-21 22:20:


Now, where are my notes? . . . oh, right, my bad.


check the maillist then :=)

protocols = imap lmtp

add sieve there

more help then i need "netstat -natpu | grep dovecot" output

tux ~ # netstat -natpu | grep dovecot
tcp0  0 0.0.0.0:993 0.0.0.0:*   
LISTEN  3554/dovecot
tcp0  0 127.0.0.1:12340 0.0.0.0:*   
LISTEN  3554/dovecot
tcp0  0 127.0.0.1:240.0.0.0:*   
LISTEN  3554/dovecot
tcp0  0 127.0.0.1:143   0.0.0.0:*   
LISTEN  3554/dovecot
tcp0  0 127.0.0.1:4190  0.0.0.0:*   
LISTEN  3554/dovecot


from my own tux, i love it :)

note all the love to 127.0.0.1


___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[joe a]

On 1/21/2024 16:37:26, Christian Kivalo wrote:




I should add, I compiled dovecot locally, it is not the vendor supplied 
package.  Could that matter?

Have you also compiled pigeonhole / managesieve
https://pigeonhole.dovecot.org/download.html
This provides the managesieve server functionality


Ah, seems I lied. Apologies. Cognitive decline affects all it seems.

I am using the openSuse package for LEAP 15.5 which declares itself to 
be Dovecot 2.3.21 and Pigeonhole version 0.5.21


Early on I did download the packages via the dovecot site, but, upon 
further study (as in RTFDocs) read that openSuse provided everything 
prepackaged.


dovecot -n, does indicate Pigeonhole exists, so one presumes managesieve 
is there.  Should I be able to find a managesieve binary somewhere?


Perhaps I need to follow this up with OpenSuse rather than annoy people 
here?









___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[Larry Rosenman]

oh, I see.  I thought I saw FreeBSD mentioned.  Sorry for the confusion.

On Sun, Jan 21, 2024 at 4:10 PM joe a  wrote:
 On 1/21/2024 16:25:02, Larry Rosenman wrote:
 > Joe A: If you are on FreeBSD, is there a reason you're not using
 the
 > Ports version (either via pkg or compiled from ports?
 > I'm the FreeBSD port maintainer and am more than happy to help
 privately
 > if necessary.
 >
 > On Sun, Jan 21, 2024 at 3:21 PM joe a  > wrote:
 >
 >     On 1/21/2024 15:05:13, Benny Pedersen wrote:
 >      > joe a skrev den 2024-01-21 20:47:
 >      >
 >      >> Ah, I see what you meant now.
 >      >
 >      > good to see progress
 >      >
 >      >> I added the local host and the bound NIC IP, restarted
 dovecot,
 >     but,
 >      >> still no love from 4190
 >      >
 >      > check your doveconf -n, if missing what i posted, unsure ?
 >      >
 >      > pm me your doveconf -n, i have lost if you already did, does
 not
 >     matter
 >      > if you have made progress, the addrss is pr service, not
 global in
 >      > dovecot.conf, order does mater
 >      >
 >      > ___
 >      > dovecot mailing list -- dovecot@dovecot.org
 >     
 >      > To unsubscribe send an email to dovecot-le...@dovecot.org
 >     
 >
 >     Attached is that most recent.
 >
 >     I should add, I compiled dovecot locally, it is not the vendor
 supplied
 >     package.  Could that matter?
 >
 >     Now setting up a VM as a test with the vendor package and will
 attempt
 >     to set things up as identically as I can.  Just to see what
 happens.
 >
 >     Now, where are my notes? . . . oh, right, my
 >     bad.___
 >     dovecot mailing list -- dovecot@dovecot.org 
 >     To unsubscribe send an email to dovecot-le...@dovecot.org
 >     
 >
 >
 >
 > --
 > Larry Rosenman http://www.lerctr.org/~ler 
 > Phone: +1 214-642-9640 (c)     E-Mail: larry...@gmail.com
 > 
 > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

 Thanks.  I am on openSuse LEAP 15.5.

 joe a.


--
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c)     E-Mail: larry...@gmail.com
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[joe a]

On 1/21/2024 16:25:02, Larry Rosenman wrote:
Joe A: If you are on FreeBSD, is there a reason you're not using the 
Ports version (either via pkg or compiled from ports?
I'm the FreeBSD port maintainer and am more than happy to help privately 
if necessary.


On Sun, Jan 21, 2024 at 3:21 PM joe a > wrote:


On 1/21/2024 15:05:13, Benny Pedersen wrote:
 > joe a skrev den 2024-01-21 20:47:
 >
 >> Ah, I see what you meant now.
 >
 > good to see progress
 >
 >> I added the local host and the bound NIC IP, restarted dovecot,
but,
 >> still no love from 4190
 >
 > check your doveconf -n, if missing what i posted, unsure ?
 >
 > pm me your doveconf -n, i have lost if you already did, does not
matter
 > if you have made progress, the addrss is pr service, not global in
 > dovecot.conf, order does mater
 >
 > ___
 > dovecot mailing list -- dovecot@dovecot.org

 > To unsubscribe send an email to dovecot-le...@dovecot.org


Attached is that most recent.

I should add, I compiled dovecot locally, it is not the vendor supplied
package.  Could that matter?

Now setting up a VM as a test with the vendor package and will attempt
to set things up as identically as I can.  Just to see what happens.

Now, where are my notes? . . . oh, right, my
bad.___
dovecot mailing list -- dovecot@dovecot.org 
To unsubscribe send an email to dovecot-le...@dovecot.org




--
Larry Rosenman http://www.lerctr.org/~ler 
Phone: +1 214-642-9640 (c)     E-Mail: larry...@gmail.com 


US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106


Thanks.  I am on openSuse LEAP 15.5.

joe a.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[Christian Kivalo]

>I should add, I compiled dovecot locally, it is not the vendor supplied 
>package.  Could that matter?
Have you also compiled pigeonhole / managesieve
https://pigeonhole.dovecot.org/download.html
This provides the managesieve server functionality 
-- 
Christian Kivalo
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: lda or lmtp for sieve?

[Patrick Domack via dovecot]

If postfix is adding it, your not using lmtp.

Only virtual and local adds it in postfix, lmtp is a symlink to smtp  
and does not add that header.
If your somehow delivering the mail through local, then forwarding it  
again via lmtp, that would be a bad thing.
Maybe look how you have spam/virus/... configured? Are they configured  
in some kind of loopback config using a lda that it shouldn't be  
using? I do know in older postfix versions (I haven't tested it in  
3.x) if an email came into my postfix server with a return-path  
header, postfix would strip it out before delivering it via lmtp/smtp




Quoting Michael Peddemors :


On 2024-01-21 04:43, Patrick Domack via dovecot wrote:


Quoting Benny Pedersen :


Christian Kivalo skrev den 2024-01-21 02:08:


Just wish LMTP would not end up with duplicate Return-Path headers..
Duplicate return path headers? I don't see them on my system. All  
mail is sent from postfix to dovecot with lmtp


it simply works better with lda ? :)

return-path is std postfix envelope sender pseudo header, bugs ?


it's not a pseudo header, it is defined starting in rfc-822, as to  
be added at time of delievery.


The LDA should add it, postfix lda add it (virtual/local) and  
dovecots do also (lda/lmtp)


I have used most postfix versions from 2.1 to 3.8 and dovecot lda  
and lmtp and haven't have never seen duplicate headers


Maybe it is just a Zimbra thing.. but we definitely see this  
occurring in the wild..   Maybe just poor configuration, but of  
course as per RFC, to be clear, is only supposed to be added by the  
'final' delivery mechanism.


So, the logic that implies duplicate Return-Path either indicates a  
broken system, looping issue, or email replay fails in those  
situations.


Postfix adds...

Return-path: 
Envelope-to: 
Delivery-date: Fri, 06 Oct 2023 08:56:07 -0300


After which it get handled by lmtp, which adds the following..

Return-Path: 
Delivered-To: 
Received: from 
by  with LMTP
id CMvDLNf1H2UcHQAAJRWI5g
(envelope-from )
for ; Fri, 06 Oct 2023 08:56:07 -0300

I guess this is a double issue, postfix should know that in this  
case, it is not the final delivery, lmtp is.. and lmtp should  
probably either remove the previous Return-Path, or copy that to a  
new header.. since it was not supposed to be there (but that has  
ramifications too.



--
"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 Reg. TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org




___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[Larry Rosenman]

Joe A: If you are on FreeBSD, is there a reason you're not using the Ports
version (either via pkg or compiled from ports?
I'm the FreeBSD port maintainer and am more than happy to help privately if
necessary.

On Sun, Jan 21, 2024 at 3:21 PM joe a  wrote:
 On 1/21/2024 15:05:13, Benny Pedersen wrote:
 > joe a skrev den 2024-01-21 20:47:
 >
 >> Ah, I see what you meant now.
 >
 > good to see progress
 >
 >> I added the local host and the bound NIC IP, restarted dovecot,
 but,
 >> still no love from 4190
 >
 > check your doveconf -n, if missing what i posted, unsure ?
 >
 > pm me your doveconf -n, i have lost if you already did, does not
 matter
 > if you have made progress, the addrss is pr service, not global in
 > dovecot.conf, order does mater
 >
 > ___
 > dovecot mailing list -- dovecot@dovecot.org
 > To unsubscribe send an email to dovecot-le...@dovecot.org

 Attached is that most recent.

 I should add, I compiled dovecot locally, it is not the vendor
 supplied
 package.  Could that matter?

 Now setting up a VM as a test with the vendor package and will
 attempt
 to set things up as identically as I can.  Just to see what happens.

 Now, where are my notes? . . . oh, right, my
 bad.___
 dovecot mailing list -- dovecot@dovecot.org
 To unsubscribe send an email to dovecot-le...@dovecot.org


--
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c)     E-Mail: larry...@gmail.com
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[joe a]

On 1/21/2024 15:05:13, Benny Pedersen wrote:

joe a skrev den 2024-01-21 20:47:


Ah, I see what you meant now.


good to see progress

I added the local host and the bound NIC IP, restarted dovecot, but, 
still no love from 4190


check your doveconf -n, if missing what i posted, unsure ?

pm me your doveconf -n, i have lost if you already did, does not matter 
if you have made progress, the addrss is pr service, not global in 
dovecot.conf, order does mater


___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org


Attached is that most recent.

I should add, I compiled dovecot locally, it is not the vendor supplied 
package.  Could that matter?


Now setting up a VM as a test with the vendor package and will attempt 
to set things up as identically as I can.  Just to see what happens.


Now, where are my notes? . . . oh, right, my bad.# 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.21 (f6cd4b8e)
# OS: Linux 5.14.21-150500.55.31-default x86_64
# Hostname: my-host
auth_username_format = %u
auth_verbose = yes
disable_plaintext_auth = no
first_valid_uid = 100
info_log_path = /var/log/dovecot-info.log
listen = 127.0.0.1, 192.168.xx.xxx
log_path = /var/log/dovecot.log
mail_location = maildir:~/Maildir
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character 
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy 
include variables body enotify environment mailbox date index ihave duplicate 
mime foreverypart extracttext
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix =
}
passdb {
  driver = pam
}
passdb {
  args = /etc/dovecot/passwd
  driver = passwd-file
}
plugin {
  sieve = 
file:/home/vmail/%u/sieve/scripts;active=/home/vmail/%u/sieve/.dovecot.sieve
  sieve_user_log = 
file:/home/vmail/%u/sieve/scripts;active=/home/vmail/%u/sieve/sieve_error.log
}
protocols = imap lmtp
service auth-worker {
  user = $default_internal_user
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
  }
}
service managesieve-login {
  inet_listener sieve {
address = 127.0.0.1, 192.168.xx.xxx
port = 4190
  }
  service_count = 1
}
service managesieve {
  process_limit = 1024
}
ssl = no
ssl_cipher_list = 
ALL:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH
ssl_options = no_compression
ssl_prefer_server_ciphers = yes
userdb {
  driver = passwd
}
userdb {
  args = uid=vmail gid=vmail home=/home/vmail/%u
  driver = static
}
protocol lmtp {
  mail_plugins = " sieve"
}
protocol sieve {
  managesieve_max_line_length = 64 k
}___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[Benny Pedersen]

joe a skrev den 2024-01-21 20:47:


Ah, I see what you meant now.


good to see progress

I added the local host and the bound NIC IP, restarted dovecot, but, 
still no love from 4190


check your doveconf -n, if missing what i posted, unsure ?

pm me your doveconf -n, i have lost if you already did, does not matter 
if you have made progress, the addrss is pr service, not global in 
dovecot.conf, order does mater


___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[joe a]

On 1/21/2024 14:13:14, Benny Pedersen wrote:

joe a skrev den 2024-01-21 19:42:


Do not know what you mean by "containers".


service managesieve-login {
   inet_listener sieve {
     address = 127.0.0.1
     port = 4190
   }
   process_min_avail = 0
   service_count = 1
   vsz_limit = 64 M
}
service managesieve {
   process_limit = 1024
}

what did you add ?

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org


Ah, I see what you meant now.

I added the local host and the bound NIC IP, restarted dovecot, but, 
still no love from 4190




___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[Benny Pedersen]

joe a skrev den 2024-01-21 19:42:


Do not know what you mean by "containers".


service managesieve-login {
  inet_listener sieve {
address = 127.0.0.1
port = 4190
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 64 M
}
service managesieve {
  process_limit = 1024
}

what did you add ?

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[joe a]

On 1/21/2024 13:00:25, Benny Pedersen wrote:

joe a skrev den 2024-01-21 17:55:

I don't see "login_access_sockets = tcpwrap" via dovecot -n
and am on openSuse Leap 15.5, not FreeBSD.

However output of socklist -l is attached.

Interestingly, I see tcp6 and udp6 listed.  Not sure what that means 
in this context as IPv6 is not enabled, supposedly, on this unit.


in this case you have still ipv6 binded services, to turn of add only 
"address = 127.0.0.1" to only listen on loopback ip, for more ip add more


check service containers in dovecot

if address missing in any containers, it equal to listing / binding to 
all ips


https://doc.dovecot.org/configuration_manual/service_configuration/#address

for dovecot developpers, is using hostnames good idea to use here ?




IPv6 does not seem to be bound for dovecot.

I set address =  in dovecot.conf. Did not affect the port 4190 not binding.

Do not know what you mean by "containers".


___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[Benny Pedersen]

joe a skrev den 2024-01-21 17:55:

I don't see "login_access_sockets = tcpwrap" via dovecot -n
and am on openSuse Leap 15.5, not FreeBSD.

However output of socklist -l is attached.

Interestingly, I see tcp6 and udp6 listed.  Not sure what that means in 
this context as IPv6 is not enabled, supposedly, on this unit.


in this case you have still ipv6 binded services, to turn of add only 
"address = 127.0.0.1" to only listen on loopback ip, for more ip add 
more


check service containers in dovecot

if address missing in any containers, it equal to listing / binding to 
all ips


https://doc.dovecot.org/configuration_manual/service_configuration/#address

for dovecot developpers, is using hostnames good idea to use here ?




___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: lda or lmtp for sieve?

[Michael Peddemors]

On 2024-01-21 04:43, Patrick Domack via dovecot wrote:


Quoting Benny Pedersen :


Christian Kivalo skrev den 2024-01-21 02:08:


Just wish LMTP would not end up with duplicate Return-Path headers..
Duplicate return path headers? I don't see them on my system. All 
mail is sent from postfix to dovecot with lmtp


it simply works better with lda ? :)

return-path is std postfix envelope sender pseudo header, bugs ?


it's not a pseudo header, it is defined starting in rfc-822, as to be 
added at time of delievery.


The LDA should add it, postfix lda add it (virtual/local) and dovecots 
do also (lda/lmtp)


I have used most postfix versions from 2.1 to 3.8 and dovecot lda and 
lmtp and haven't have never seen duplicate headers


Maybe it is just a Zimbra thing.. but we definitely see this occurring 
in the wild..   Maybe just poor configuration, but of course as per RFC, 
to be clear, is only supposed to be added by the 'final' delivery mechanism.


So, the logic that implies duplicate Return-Path either indicates a 
broken system, looping issue, or email replay fails in those situations.


Postfix adds...

Return-path: 
Envelope-to: 
Delivery-date: Fri, 06 Oct 2023 08:56:07 -0300


After which it get handled by lmtp, which adds the following..

Return-Path: 
Delivered-To: 
Received: from 
by  with LMTP
id CMvDLNf1H2UcHQAAJRWI5g
(envelope-from )
for ; Fri, 06 Oct 2023 08:56:07 -0300

I guess this is a double issue, postfix should know that in this case, 
it is not the final delivery, lmtp is.. and lmtp should probably either 
remove the previous Return-Path, or copy that to a new header.. since it 
was not supposed to be there (but that has ramifications too.



--
"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 Reg. TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: managesieve server not answering?

[joe a]

I don't see "login_access_sockets = tcpwrap" via dovecot -n
and am on openSuse Leap 15.5, not FreeBSD.

However output of socklist -l is attached.

Interestingly, I see tcp6 and udp6 listed.  Not sure what that means in 
this context as IPv6 is not enabled, supposedly, on this unit.


joe a.

On 1/21/2024 10:38:23, Aki Tuomi via dovecot wrote:

Another thing i noticed that you are using

login_access_sockets = tcpwrap

I wonder if tcpwrap might be interfering here?

Also, since you are using FreeBSD, can you use sockstat -l to determine if 4190 
is listed there anymore?

Did you check that you haven't firewalled the port off?

Aki


On 19/01/2024 18:36 EET joe a  wrote:

  
Where can one look to determine if managesieve "loaded"? Such as via

logs or other some means?

As indicated it did not, AFAICT, bind to 4190 as directed, and no errors
appear in logs, via "doveadm log errors".

If there were some configuration error or failure in some startup,
should there not be something?

joe a.


On 1/18/2024 18:30:06, Joe Acquisto wrote:

Trying to connect to managesieve server configured to port 4190. No go.

Roundcube is configured (thunderbird apparently having nothing current),
but selecting "Add Filter" (new since re-configured for managesieve)
produces "unable to connect to server".

Port 4190 does not seem to answer or be "bound" to anything. Telnet to
4190 produces "connection refused".

A "one box" solution.

If I had to guess, I would guess, operator error.    Otherwise, things
are looking up.  But, I remember a movie that said never to do that . . .


___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org~# socklist -l
type   port  inode uidpid   fd  name
tcp3306  17269  60   1231   64  mysqld
tcp 443  17146   0  150594  httpd-prefork
tcp  25  17500   0   1347   12  master
tcp  22  16854   0   12043  sshd
tcp  80  17143   0  150593  httpd-prefork
tcp 143  16762   0   1160   37  dovecot
tcp 143  56445 474  155397  imap
tcp 143  55746 474  155097  imap
tcp 143  56032 474  155187  imap
tcp 143  55736 474  155067  imap
tcp 143  56231 474  155287  imap
tcp 143  55885 474  155117  imap
tcp 143  55966 474  155147  imap
tcp 143  55925 474  155127  imap
tcp 143  56097 474  155207  imap
tcp 143  55952 474  155137  imap
tcp 143  56168 474  155237  imap
tcp  22  56509   0  155534  sshd
tcp 143  56042 474  155177  imap
tcp 143  56217 474  155277  imap
tcp 143  56418 474  155377  imap
tcp 143  55726 474  155057  imap
tcp 143  55716 474  155037  imap
tcp6 25  17501   0   1347   13  master
tcp6 22  16871   0   12044  sshd
tcp6143  16763   0   1160   38  dovecot
udp 323  16670   0   11805  chronyd
udp6323  16671   0   11806  chronyd___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: dsync with vurtial folder leads to mess of msg ID

[Kirill A . Korinsky]

On Sun, 21 Jan 2024 16:34:44 +0100,
Aki Tuomi wrote:
>
> Can you send output of doveconf -n?
> 

Sure, here it is:

  # 2.3.20 (80a5ac675d): /etc/dovecot/dovecot.conf
  # Pigeonhole version 0.5.20 (149edcf2)
  # OS: OpenBSD 7.4 amd64  
  # Hostname: mx1.catap.net
  default_vsz_limit = 10 G
  doveadm_password = # hidden, use -P to show it
  doveadm_port = 12345
  first_valid_uid = 1000
  mail_attribute_dict = file:%h/Maildir/dovecot-attributes
  mail_gid = vmail
  mail_location = maildir:~/Maildir
  mail_plugins = notify replication fts fts_flatcurve virtual
  mail_uid = vmail
  managesieve_notify_capability = mailto
  managesieve_sieve_capability = fileinto reject envelope encoded-character 
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy 
include variables body enotify environment mailbox date index ihave duplicate 
mime foreverypart extracttext
  mbox_write_locks = fcntl
  mmap_disable = yes
  namespace inbox {
inbox = yes
location = 
mailbox Archive {
  auto = subscribe
  special_use = \Archive
}
mailbox Drafts {
  auto = subscribe
  special_use = \Drafts
}
mailbox Junk {
  auto = subscribe
  autoexpunge = 60 days
  special_use = \Junk
}
mailbox Sent {
  auto = subscribe
  special_use = \Sent
}
mailbox Trash {
  auto = subscribe
  autoexpunge = 60 days
  special_use = \Trash
}
prefix = 
separator = .
  }
  namespace virtual {
location = virtual:/etc/dovecot/virtual:INDEX=~/virtual
mailbox All {
  comment = All messages without Trash and Junk
  special_use = \All
}
mailbox Flagged {
  comment = All flagged messages without Trash and Junk
  special_use = \Flagged
}
prefix = virtual.
separator = .
  }
  passdb {
args = username_format=%u /etc/dovecot/users
driver = passwd-file
  }
  plugin {
fts = flatcurve
fts_filters = normalizer-icu snowball stopwords
fts_filters_en = lowercase snowball english-possessive stopwords
fts_flatcurve_substring_search = yes
fts_languages = en de ru es
fts_tokenizer_generic = algorithm=simple
fts_tokenizers = generic email-address
mail_replica = tcps:mx2.catap.net
sieve = file:~/sieve;active=~/.dovecot.sieve
sieve_before = /etc/dovecot/sieve_before.d/
  }
  protocols = imap lmtp sieve
  replication_dsync_parameters = -d -l 30 -U -x virtual.
  service aggregator {
fifo_listener replication-notify-fifo {
  user = vmail
}
unix_listener replication-notify {
  user = vmail
}
  }
  service doveadm {
inet_listener {
  port = 12345
  ssl = yes
}
  }
  service imap-login {
inet_listener imap {
  port = 143
}
inet_listener imaps {
  port = 993
  ssl = yes
}
  }
  service lmtp {
unix_listener lmtp {
  mode = 0666
}
  }
  service managesieve-login {
inet_listener sieve {
  port = 4190
}
  }
  service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
  mode = 0600
  user = vmail
}
  }
  ssl_cert = 

Re: managesieve server not answering?

[Aki Tuomi via dovecot]

Another thing i noticed that you are using 

login_access_sockets = tcpwrap

I wonder if tcpwrap might be interfering here?

Also, since you are using FreeBSD, can you use sockstat -l to determine if 4190 
is listed there anymore?

Did you check that you haven't firewalled the port off?

Aki

> On 19/01/2024 18:36 EET joe a  wrote:
> 
>  
> Where can one look to determine if managesieve "loaded"? Such as via 
> logs or other some means?
> 
> As indicated it did not, AFAICT, bind to 4190 as directed, and no errors 
> appear in logs, via "doveadm log errors".
> 
> If there were some configuration error or failure in some startup, 
> should there not be something?
> 
> joe a.
> 
> 
> On 1/18/2024 18:30:06, Joe Acquisto wrote:
> > Trying to connect to managesieve server configured to port 4190. No go.
> > 
> > Roundcube is configured (thunderbird apparently having nothing current), 
> > but selecting "Add Filter" (new since re-configured for managesieve) 
> > produces "unable to connect to server".
> > 
> > Port 4190 does not seem to answer or be "bound" to anything. Telnet to 
> > 4190 produces "connection refused".
> > 
> > A "one box" solution.
> > 
> > If I had to guess, I would guess, operator error.    Otherwise, things 
> > are looking up.  But, I remember a movie that said never to do that . . .
> > 
> > 
> > ___
> > dovecot mailing list -- dovecot@dovecot.org
> > To unsubscribe send an email to dovecot-le...@dovecot.org
> ___
> dovecot mailing list -- dovecot@dovecot.org
> To unsubscribe send an email to dovecot-le...@dovecot.org
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: replication timeout

[Aki Tuomi via dovecot]

Can you try with doveadm -D and send the log?

Aki

> On 20/01/2024 19:51 EET Andy Balholm  wrote:
> 
>  
> I forgot to mention in my original message that I'm running Dovecot
> 2.3.21 (47349e2482).
> 
> It seems like the stalls are more likely to happen
> when the type of sync is "incremental" rather than
> "normal" or "full".
> (I'm inclined to think they only happen for incremental syncs,
> but I'm not sure.)
> 
> Andy
> 
> 
> On Friday, January 19, 2024 9:26:29 AM PST, Andy Balholm wrote:
> > I have two Dovecot mail servers that replicate to each other.
> > Sometimes there are delays in the synchronization,
> > and I notice that the mail log has entries like this:
> >
> > Error: dsync(spokane): I/O has stalled, no activity for 600 
> > seconds (last sent=mailbox, last recv=mailbox_state)
> >
> > Five minutes seems like a long time to sit there waiting with 
> > nothing happening.
> > Is there a way to reduce this timeout so that I don't have so many
> > replicaton connections just sitting around doing nothing?
> >
> > (Of course, a way to prevent the I/O stalls would be great too,
> > but with my limited upload bandwidth, they may be unavoidable.)
> >
> > Andy
> >
> 
> ___
> dovecot mailing list -- dovecot@dovecot.org
> To unsubscribe send an email to dovecot-le...@dovecot.org
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: dsync with vurtial folder leads to mess of msg ID

[Aki Tuomi via dovecot]

> On 20/01/2024 17:00 EET Kirill A. Korinsky  wrote:
> 
>  
> I'd like to add that allowing to save messages via virtual folder to some 
> folder
> by change it defintion to
> 
>   *
>   !Archive
>   -Trash
>   -Trash/*
>   -Junk
>   -Junk/*
> all
> 
> doesn't help and syncronization fails as usual:
> 
>   Jan 20 15:34:06 mx1 dovecot: 
> doveadm(kir...@korins.ky)<75563>: Error: Can't create 
> mailbox virtual.All: Can't create virtual mailboxes
> 
> And to share my setup of virtual folder which is quite simple:
> 
>   mail_plugins = $mail_plugins virtual
> 
>   namespace virtual {
> separator = .
> prefix = virtual.
> 
> location = virtual:/etc/dovecot/virtual:INDEX=~/virtual
> 
> mailbox All {
>   special_use = \All
>   comment = All messages without Trash and Junk
> }
> 
> mailbox Flagged {
>   special_use = \Flagged
>   comment = All flagged messages without Trash and Junk
> }
>   }
> 
> --
> wbr, Kirill

Can you send output of doveconf -n?

Aki
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: lda or lmtp for sieve?

[Patrick Domack via dovecot]

Quoting Benny Pedersen :


Christian Kivalo skrev den 2024-01-21 02:08:


Just wish LMTP would not end up with duplicate Return-Path headers..
Duplicate return path headers? I don't see them on my system. All  
mail is sent from postfix to dovecot with lmtp


it simply works better with lda ? :)

return-path is std postfix envelope sender pseudo header, bugs ?


it's not a pseudo header, it is defined starting in rfc-822, as to be  
added at time of delievery.


The LDA should add it, postfix lda add it (virtual/local) and dovecots  
do also (lda/lmtp)


I have used most postfix versions from 2.1 to 3.8 and dovecot lda and  
lmtp and haven't have never seen duplicate headers



___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org