Re: imap-login segfaulting on 2.3.1
On 24.04.2018 00:40, Grant Keller wrote:
> Hello,
>
> I have a new director ring I am setting up on centos 7 with dovecot
> 2.3.1. I haven't been able to replecate this in testing, but as soon as
> I start pushing production traffic to the new ring I see dozens of these in
> the
> logs:
> Apr 18 00:34:00 d.director.imapd.sonic.net kernel: imap-login[163107]:
> segfault at 10 ip 7ff625698dd5sp 7ffe4b77bb28 error 4 in
> libdovecot.so.0.0.0[7ff6255bf000+16e000]
>
> My config:
> # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf
> # OS: Linux 3.10.0-693.21.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708
> (Core)
> # Hostname: c.director.imapd.sonic.net
> auth_master_user_separator = *
> auth_username_format = %Ln
> auth_verbose = yes
> default_client_limit = 2
> director_mail_servers = 64.142.111.75 64.142.111.43 64.142.111.76
> 64.142.111.39 64.142.111.81
> director_servers = c.director.imapd.sonic.net d.director.imapd.sonic.net
> disable_plaintext_auth = no
> doveadm_port = 1842
> login_trusted_networks = 64.142.18.0/24 64.142.105.2 64.142.111.67
> 64.142.111.36 64.142.105.3 64.142.111.35 64.142.111.68
> 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 {
> args = /etc/dovecot/master-users
> driver = passwd-file
> master = yes
> pass = yes
> }
> passdb {
> args = proxy=y nopassword=y
> driver = static
> }
> service anvil {
> client_limit = 40103
> }
> service auth {
> client_limit = 41704
> }
> service director {
> fifo_listener login/proxy-notify {
> mode = 0666
> }
> inet_listener {
> port = 9321
> }
> unix_listener login/director {
> mode = 0666
> }
> }
> service imap-login {
> executable = imap-login director
> process_limit = 2
> process_min_avail = 32
> }
> service imap {
> process_limit = 20480
> }
> service ipc {
> unix_listener ipc {
> user = dovecot
> }
> }
> service pop3-login {
> executable = pop3-login director
> process_limit = 2
> process_min_avail = 32
> }
> ssl_cert = ssl_cipher_list =
> ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA
> ssl_dh = # hidden, use -P to show it
> ssl_key = # hidden, use -P to show it
> syslog_facility = local0
> protocol imap {
> imap_max_line_length = 128 k
> ssl_cert =ssl_key = # hidden, use -P to show it
> }
> protocol pop3 {
> ssl_cert =ssl_key = # hidden, use -P to show it
> }
>
> backtrace:
> Stack trace of thread 56084:
> #0 0x7fe529be2dd5 i_stream_get_root_io (libdovecot.so.0)
> #1 0x7fe529be2e39 i_stream_set_input_pending
> (libdovecot.so.0)
> #2 0x7fe527415a59 openssl_iostream_bio_sync
> (libssl_iostream_openssl.so)
> #3 0x7fe527415c2a openssl_iostream_more
> (libssl_iostream_openssl.so)
> #4 0x7fe527415c6b openssl_iostream_destroy
> (libssl_iostream_openssl.so)
> #5 0x7fe529e8be72 client_unref (libdovecot-login.so.0)
> #6 0x7fe529e90441 login_proxy_free_full
> (libdovecot-login.so.0)
> #7 0x7fe529e90e07 login_proxy_finished
> (libdovecot-login.so.0)
> #8 0x7fe529becfb5 io_loop_call_io (libdovecot.so.0)
> #9 0x7fe529bee89f io_loop_handler_run_internal
> (libdovecot.so.0)
> #10 0x7fe529bed0b2 io_loop_handler_run (libdovecot.so.0)
> #11 0x7fe529bed2d8 io_loop_run (libdovecot.so.0)
> #12 0x7fe529b69673 master_service_run (libdovecot.so.0)
> #13 0x7fe529e93532 login_binary_run
> (libdovecot-login.so.0)
> #14 0x7fe529767c05 __libc_start_main (libc.so.6)
> #15 0x5567b256050a _start (imap-login)
>
>
>
> Grant Keller
> System Operations
> grant.kel...@sonic.com
Hi!
Can you provide bt full output?
Aki
Re: smtp crashing with "out of memory" for ONE particular user
> On 24 Apr 2018, at 9.08, Jacek Osiecki wrote: > > Finally, 512MB helped. But it is quite strange to me… Why one particular > mailbox, what could be causing it? Number of mails in INBOX. Sami
smtp crashing with "out of memory" for ONE particular user
Hi, I’m using dovecot 2.0.16 (I know, it’s ld, but I have too many users to risk the upgrade while so many things have changed since) and virtual users based on MySQL. Today I had some troubles with user, who’s mailbox stopped working. No emails were delivered, with just following error line in EXIM mainlog: LMTP connection closed after end of data When I checked dovecot’s main log, and here’s what I found: Apr 23 14:06:17 lmtp(9963, j...@silvercube.pl): Fatal: block_alloc(67108864): Out of memory Apr 23 14:06:17 lmtp(9963, j...@silvercube.pl): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3dbda) [0x7f92f3193bda] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3dc1e) [0x7f92f3193c1e] -> /usr /lib64/dovecot/libdovecot.so.0(i_error+0) [0x7f92f316d8cd] -> /usr/lib64/dovecot/libdovecot.so.0(+0x4cc45) [0x7f92f31a2c45] -> /usr/lib64/dovecot/libdovecot.so.0(+0x4cc7f) [0x7f92f31a2c7f] -> /usr/lib64/ dovecot/libdovecot.so.0(p_strdup+0x3e) [0x7f92f31ae08e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_next_uid+0xf9) [0x7f92f3653e69] -> /usr/lib64/dovecot/libdovecot-storage.so.0(ma ildir_uidlist_sync_next+0x12) [0x7f92f3654232] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x6bd3a) [0x7f92f3651d3a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x6c7d3) [0x7f92f36527d3] -> /usr/li b64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0x171) [0x7f92f3652d91] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x7f92f36173a1] -> /usr/lib64/dovecot/libdovec ot-storage.so.0(mailbox_sync+0x27) [0x7f92f36174b7] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(quota_count+0x132) [0x7f92f1f34fe2] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0x8430) [0 x7f92f1f36430] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0x863d) [0x7f92f1f3663d] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(quota_get_resource+0x72) [0x7f92f1f344c2] -> /usr/lib64/do vecot/plugins/lib10_quota_plugin.so(quota_test_alloc+0x175) [0x7f92f1f34d45] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0xb0ba) [0x7f92f1f390ba] -> /usr/lib64/dovecot/libdovecot-storage.so.0(ma ilbox_save_begin+0x46) [0x7f92f3617f56] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x7e) [0x7f92f361100e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_copy+0x51) [0x7f92f364 a8a1] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0xaefa) [0x7f92f1f38efa] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5a) [0x7f92f3617eba] -> /usr/lib64/dovecot/libdovecot-siev e.so.0(+0x36ed6) [0x7f92f1ae9ed6] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x2d83c) [0x7f92f1ae083c] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x2fd) [0x7f92f1ae1a0d] -> /usr/l ib64/dovecot/libdovecot-sieve.so.0(sieve_execute+0x7d) [0x7f92f1af0a9d] Apr 23 14:06:17 master: Error: service(lmtp): child 9963 returned error 83 (Out of memory (vsz_limit=256 MB, you may need to increase it)) What was interesting - it happenned only with this particular mailbox. It does not has large sieve file (actually, other mailboxes have muuuch bigger ones, actually nothing strange with the account - but it was failing. I have increased vsz_limit to 384MB - didn’t help. Finally, 512MB helped. But it is quite strange to me… Why one particular mailbox, what could be causing it? Greetings, — Jacek Osiecki josie...@silvercube.pl
imap-login segfaulting on 2.3.1
Hello,
I have a new director ring I am setting up on centos 7 with dovecot
2.3.1. I haven't been able to replecate this in testing, but as soon as
I start pushing production traffic to the new ring I see dozens of these in the
logs:
Apr 18 00:34:00 d.director.imapd.sonic.net kernel: imap-login[163107]: segfault
at 10 ip 7ff625698dd5sp 7ffe4b77bb28 error 4 in
libdovecot.so.0.0.0[7ff6255bf000+16e000]
My config:
# 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf
# OS: Linux 3.10.0-693.21.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708
(Core)
# Hostname: c.director.imapd.sonic.net
auth_master_user_separator = *
auth_username_format = %Ln
auth_verbose = yes
default_client_limit = 2
director_mail_servers = 64.142.111.75 64.142.111.43 64.142.111.76 64.142.111.39
64.142.111.81
director_servers = c.director.imapd.sonic.net d.director.imapd.sonic.net
disable_plaintext_auth = no
doveadm_port = 1842
login_trusted_networks = 64.142.18.0/24 64.142.105.2 64.142.111.67
64.142.111.36 64.142.105.3 64.142.111.35 64.142.111.68
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 {
args = /etc/dovecot/master-users
driver = passwd-file
master = yes
pass = yes
}
passdb {
args = proxy=y nopassword=y
driver = static
}
service anvil {
client_limit = 40103
}
service auth {
client_limit = 41704
}
service director {
fifo_listener login/proxy-notify {
mode = 0666
}
inet_listener {
port = 9321
}
unix_listener login/director {
mode = 0666
}
}
service imap-login {
executable = imap-login director
process_limit = 2
process_min_avail = 32
}
service imap {
process_limit = 20480
}
service ipc {
unix_listener ipc {
user = dovecot
}
}
service pop3-login {
executable = pop3-login director
process_limit = 2
process_min_avail = 32
}
ssl_cert =
Re: dovecot sieve duplicates detection
On 23/04/18 14:18, Stephan Bosch wrote: Op 11-4-2018 om 23:58 schreef André Rodier: Hello, I have tested the sieve duplicate script with success so far, but I have a question. Sieve duplicate script? You mean the Sieve duplicate extension (RFC 7352)? I would like to know if the "duplicate" sieve flag in Dovecot is global to all folders, or specific to one folder only. It uses the lda-dupes file in the user's home directory. So, it is not normally related to folders, although the identifier used for duplicate matching could be composed of the mailbox name if you want. For instance, if I copy an email from one folder to another, and I have a discard action on duplicate email, is this action will be applied (in this case, discard) or not. Are you talking about IMAPSieve now? I am not sure "duplicate" is currently even allowed in that context. If the duplicate is global to all folders, is there a way to restrict the search in one folder only. You can set the :uniqueid parameter accordingly. Regards, Stephan. Thank you, Stephan. Yes, I meant the Sieve duplicate extension. I am using a program to import email (mbsync), which use the IMAP append function. Sometimes, the import fail and I have to restart the program. Unfortunately, the same emails are imported again. I found a fix by using a dovecot IMAP sieve script executed on the APPEND action (https://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve). I wrote a custom sieve script that "discard" the ones that are detected as "duplicate". It worked very well and the emails were not any more imported twice. However, there was a huge side effect: archiving an email with Thunderbird is not working any more, and even lost! I have been able to understand the error as this: 1. When archiving an email with Thunderbird, it is first copied (APPEND) into the archive folder, but the original folder is not expunged. 2. The sieve script detect the email as duplicate, and discard it. 3. When the original folder is expunged, the source email is lost... My conclusion was the duplicate detection function is global to all folders. If I could restrict the detection of duplicates in the current folder only, this would let me run the import program again without error. Kind regards, André.
Re: question about using cram-md5 login passwords
On April 23, 2018 9:45:22 AM EDT, Aki Tuomi wrote: > >> On 23 April 2018 at 16:14 "Fabian A. Santiago" > wrote: >> >> >> hello dovecot community, >> >> question; if my user database and dovecot installation is currently >setup to use plain login passwords, and i want to convert to cram-md5, >after i configure dovecot accordingly and reset passwords into >cram-md5, if anyone uses plain login method again in the future, will >it still work? or must they always from this point on use encrypted >passwords? Thanks. > >Do not use CRAM-MD5/DIGEST-MD5 mechanisms if you are using SSL/TLS >connection. PLAIN/LOGIN is usually sufficiently secure over encrypted >transport, and STARTTLS is required over plaintext port too. > >In general, CRAM-MD5 is designed to authenticate over insecure >transport. > >Aki > >> >> -- >> >> Thanks, >> >> Fabian S. >> >> OpenPGP: >> >> 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) >> 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired / revoked) Ok I am using tls and have always been doing so. So I'll leave it alone then. Thanks for your thoughts. -- Fabian A. Santiago OpenPGP: 0x643082042dc83e6d94b86c405e3daa18a1c22d8f (current key) 0x3c3fa072accb7ac5db0f723455502b0eeb9070fc (to be retired / revoked)
Re: lost connection while sending end of data error
# 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.1 (d9bc6dfe)
# OS: FreeBSD 11.1-RELEASE-p8 amd64 ufs
# Hostname: server2.example.com
auth_mechanisms = plain login
auth_verbose = yes
disable_plaintext_auth = no
first_valid_gid = 0
first_valid_uid = 1001
mail_location = maildir:/home/mail/%d/%n:INDEX=/tmpfs/dovecot_%u
mail_privileged_group = mail
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 imapsieve vnd.dovecot.imapsieve
namespace inbox {
inbox = yes
location =
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Junk {
auto = subscribe
special_use = \Junk
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox "Sent Messages" {
auto = no
special_use = \Sent
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
}
passdb {
args = /usr/local/etc/dovecot/passwd.suspended
deny = yes
driver = passwd-file
}
passdb {
args = /usr/local/etc/dovecot/passwd
driver = passwd-file
}
plugin {
imapsieve_mailbox1_before =
file:/usr/local/lib/dovecot/sieve/report-spam.sieve
imapsieve_mailbox1_causes = COPY
imapsieve_mailbox1_name = Junk
imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve
imapsieve_mailbox2_causes = COPY
imapsieve_mailbox2_from = Junk
imapsieve_mailbox2_name = *
quota = maildir:User quota
quota_max_mail_size = 100M
quota_rule = *:storage=2048M
quota_status_nouser = DUNNO
quota_status_overquota = 552 5.2.2 Mailbox is full
quota_status_success = DUNNO
quota_warning = storage=80%% quota-warning 80 %u
sieve = file:~/sieve;active=~/sieve.active
sieve_before = /usr/local/lib/dovecot/sieve/antispam.sieve
sieve_global_extensions = +vnd.dovecot.pipe
sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve
sieve_plugins = sieve_imapsieve sieve_extprograms
}
protocols = imap pop3 lmtp sieve
service auth {
unix_listener auth-client {
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
port = 4190
}
}
service quota-status {
client_limit = 1
executable = quota-status -p postfix
inet_listener {
port = 12340
}
}
service quota-warning {
executable = script /root/cretapanel/quota-warning.sh
unix_listener quota-warning {
mode = 0666
user = dovecot
}
}
ssl_cert = On 23 Apr 2018, at 16:24, Stephan Bosch wrote:
>
> What is your configuration (`dovecot -n`)?
>
>
> Op 19-4-2018 om 20:45 schreef Christos Chatzaras:
>> I use dovecot-lmtp and postfix. When I send e-mail to 2 recipients (or more)
>> at the same time and if one of them is over quota (or under quota and the
>> message I send is bigger than his free space) mailq shows:
>>
>> -Queue ID- --Size-- Arrival Time -Sender/Recipient---
>> 20B03336F2226099 Thu Apr 19 18:02:47 supp...@example.com
>> (lost connection with server25.example.org[private/dovecot-lmtp] while
>> sending end of data -- message may be sent more than once)
>> us...@example.com
>> us...@example.com
>>
>> E-mails sent from the same domain on same server so it's a local delivery.
>>
>> If I send the e-mail to the over quota user ( only him on To: ) then I get a
>> bounce that says that user is over quota which is the correct behaviour.
>>
>> I think the problem started after I upgrade dovecot-2.2.35 to dovecot-2.3.1.
>>
>> Is this a known bug?
>
Re: question about using cram-md5 login passwords
> On 23 April 2018 at 16:14 "Fabian A. Santiago" > wrote: > > > hello dovecot community, > > question; if my user database and dovecot installation is currently setup to > use plain login passwords, and i want to convert to cram-md5, after i > configure dovecot accordingly and reset passwords into cram-md5, if anyone > uses plain login method again in the future, will it still work? or must they > always from this point on use encrypted passwords? Thanks. Do not use CRAM-MD5/DIGEST-MD5 mechanisms if you are using SSL/TLS connection. PLAIN/LOGIN is usually sufficiently secure over encrypted transport, and STARTTLS is required over plaintext port too. In general, CRAM-MD5 is designed to authenticate over insecure transport. Aki > > -- > > Thanks, > > Fabian S. > > OpenPGP: > > 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) > 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired / revoked)
Re: Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5
On 04/23/2018 03:22 PM, Stephan Bosch wrote: Op 20-4-2018 om 14:01 schreef Olaf Hopp: Hi (Stephan?), is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of a redirected mail or simply a bug ? A sends mail to B, B redirects to C C sees B (not A!) as envelope sender. It is not a problem if C gets the mail but if that mail bounces for various reasons it goes back to B and A will never know about this. I thick this is came with 2.3 / pigeonhole 0.5 ? # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) Probably same as issue in this thread: https://www.dovecot.org/pipermail/dovecot/2018-April/111482.html Yes maybe. But I didn't see any sieve errors in the logs. In my case there is exim sitting in front of dovecot lmtp and as said trusted_users = exim:dovecot in thge exim.conf resolved this issue for me. Regards, Olaf -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: olaf.h...@kit.edu atis.informatik.kit.edu www.kit.edu KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert. smime.p7s Description: S/MIME Cryptographic Signature
Re: lost connection while sending end of data error
What is your configuration (`dovecot -n`)? Op 19-4-2018 om 20:45 schreef Christos Chatzaras: I use dovecot-lmtp and postfix. When I send e-mail to 2 recipients (or more) at the same time and if one of them is over quota (or under quota and the message I send is bigger than his free space) mailq shows: -Queue ID- --Size-- Arrival Time -Sender/Recipient--- 20B03336F2226099 Thu Apr 19 18:02:47 supp...@example.com (lost connection with server25.example.org[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) us...@example.com us...@example.com E-mails sent from the same domain on same server so it's a local delivery. If I send the e-mail to the over quota user ( only him on To: ) then I get a bounce that says that user is over quota which is the correct behaviour. I think the problem started after I upgrade dovecot-2.2.35 to dovecot-2.3.1. Is this a known bug?
Re: Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5
Op 20-4-2018 om 14:01 schreef Olaf Hopp: Hi (Stephan?), is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of a redirected mail or simply a bug ? A sends mail to B, B redirects to C C sees B (not A!) as envelope sender. It is not a problem if C gets the mail but if that mail bounces for various reasons it goes back to B and A will never know about this. I thick this is came with 2.3 / pigeonhole 0.5 ? # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) Probably same as issue in this thread: https://www.dovecot.org/pipermail/dovecot/2018-April/111482.html Regards, Stephan.
Re: dovecot sieve duplicates detection
Op 11-4-2018 om 23:58 schreef André Rodier: Hello, I have tested the sieve duplicate script with success so far, but I have a question. Sieve duplicate script? You mean the Sieve duplicate extension (RFC 7352)? I would like to know if the "duplicate" sieve flag in Dovecot is global to all folders, or specific to one folder only. It uses the lda-dupes file in the user's home directory. So, it is not normally related to folders, although the identifier used for duplicate matching could be composed of the mailbox name if you want. For instance, if I copy an email from one folder to another, and I have a discard action on duplicate email, is this action will be applied (in this case, discard) or not. Are you talking about IMAPSieve now? I am not sure "duplicate" is currently even allowed in that context. If the duplicate is global to all folders, is there a way to restrict the search in one folder only. You can set the :uniqueid parameter accordingly. Regards, Stephan.
question about using cram-md5 login passwords
hello dovecot community, question; if my user database and dovecot installation is currently setup to use plain login passwords, and i want to convert to cram-md5, after i configure dovecot accordingly and reset passwords into cram-md5, if anyone uses plain login method again in the future, will it still work? or must they always from this point on use encrypted passwords? Thanks. -- Thanks, Fabian S. OpenPGP: 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired / revoked)
Re: Merging mailboxes with doveadm
The command you are looking for is doveadm import ---Aki TuomiDovecot oy Original message From: Carsten Schmitz Date: 23/04/2018 15:46 (GMT+02:00) To: dovecot@dovecot.org Subject: Merging mailboxes with doveadm Hello, I am trying to merge(=copy) all mails of all user mailboxes into one mailbox for one-time archival purposes. The command I am using is sudo doveadm -v copy -A arch...@somedomain.net ALL The error I get for every mailbox is: doveadm(someus...@somedomain.net): Error: Can't open mailbox 'a...@somedomain.net': Mailbox doesn't exist: arch...@somedomain.net doveadm(someus...@somedomain.net): Error: Can't open mailbox 'a...@somedomain.net': Mailbox doesn't exist: arch...@somedomain.net [etc...] I don't exactly understand why. I think I am don't understand the 'destination' parameter correctly, so somebody can enlighten me, please? Thank you Carsten
Merging mailboxes with doveadm
Hello, I am trying to merge(=copy) all mails of all user mailboxes into one mailbox for one-time archival purposes. The command I am using is sudo doveadm -v copy -A arch...@somedomain.net ALL The error I get for every mailbox is: doveadm(someus...@somedomain.net): Error: Can't open mailbox 'a...@somedomain.net': Mailbox doesn't exist: arch...@somedomain.net doveadm(someus...@somedomain.net): Error: Can't open mailbox 'a...@somedomain.net': Mailbox doesn't exist: arch...@somedomain.net [etc...] I don't exactly understand why. I think I am don't understand the 'destination' parameter correctly, so somebody can enlighten me, please? Thank you Carsten
Re: Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5
On 04/23/2018 07:28 AM, Steffen Kaiser wrote: Envelope *senders* should never ever be modified. If the domain of sender A has SPF records installed and B redirects to C, but keeps the envelope sender A, the SPF check will fail on C. That's the reason why I say SPF is broken by design. People using it, should hopefully know what they are doing. But that's a little bit OT for this list. Olaf -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: olaf.h...@kit.edu atis.informatik.kit.edu www.kit.edu KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert. smime.p7s Description: S/MIME Cryptographic Signature
