Re: Change dovecot hostname
"Scott W. Sander" writes: I have noticed that the name of my private server running dovecot appears in email headers rather than the public-friendly name of my server. Which headers are you taking about? If you're talking about Received: headers, that's usually inserted by your MTA, not dovecot. Joseph Tam
Re: Crash on opening mailbox
> On August 19, 2016 at 10:00 PM Ladislav Laska wrote: > > > Hi! > > I'm currently experiencing a crash of dovecot 2.2.25 on Gentoo, upon opening > mailbox. The crash only triggers on opening inbox, other mailboxes seem to > work > fine. It happens every time, and can be reproduced on request. I also briefly > tried 2.2.19, and it behaves the same. > > The bug seems to be triggered by some mail, as I encountered it previously > and > fixed by removing some spam. I guess it might be malformed header of some > kind. > I can open the mailbox locally using mutt, but fail to do so remotely (using > mutt or K-9 mail on android). Unforunately, I haven't been able to isolate > the > specific mail, as when I create a new mailbox, dovecot refuses to open it: > > [CANNOT] Mailbox isn't a valid mbox file (0.000 + 0.000 secs). > > I'm not really sure what's going on and will investigate further once I find > some time to do so. > > I also experienced a similar problem on opening a specific mail, but it's > much > harder to reproduce and I currently don't have an example. The crash looks > very > similar, and only happens on first attempt to open a specific mail, it always > works later on. > > I'm attaching a stack trace and dovecot -n. I'm also willing to send the > binary > and core dump, but not publicly, as I'm not eager to share whatever's inside > with the whole world. > > Other than what I mentioned, I'm running pretty standard setup, with postfix > on > Gentoo x86_64, ext4 fs, quota and disk space is plentiful. The delivery agent > is > dovecot itself, in postfix/main.cf I have: > > mailbox_command = /usr/libexec/dovecot/deliver > > I'm using sieve script to file my mail, but the problem manifested even > before > when I was still using procmail to deliver my mail (I migrated because I had > doubts about procmail and dovecot lock cooperation) > > I'll keep my mailbox corrupted for a few more days, and access the mail only > locally, hoping to test a potential fix. Let me know if you need any more > info/experimentation. Also, if you know a good way to find the mail that > causes > the trouble out of the core, let me know, I'd be glad to forward it for > testing. > > Thanks and I hope we can find (and fix) the problem! > > -- > S pozdravem Ladislav Láska > Katedra Aplikované Matematiky, MFF UK tel.: +420 739 464 167 Hi! Please provide doveconf -n relevant log files (or at least anything you care to share) gdb /path/to/binary /path/to/core bt full --- Aki Tuomi Dovecot Oy
Re: [patch] Improved error checking for the dovecot-antispam-plugin
Robert, First, thanks! Second, I'm not a committer on the dovecot project. But I've written a lot of software where if an end user has a problem and either they want to know why or if they report it and ask for help, I've found it is MUCH better to have enough info in the message given to the user/logged somewhere. Something like: "subroutine: open(%s) failed: %m" It reduces our support load and gives us the information we need to quickly resolve issues. Sent from my iPhone - please excuse brevity and typos > On Aug 18, 2016, at 8:16 AM, Robert Munteanu > wrote: > > (snip) > >> I have no issue in resending a new version of the patch with better >> error reporting, will do so in the following days. >> >> Robert > > I've attached a second version of the patch, feel free to consider any > of them for inclusion. > > Thanks, > > Robert > > > -- > http://robert.muntea.nu/ >
Crash on opening mailbox
Hi!
I'm currently experiencing a crash of dovecot 2.2.25 on Gentoo, upon opening
mailbox. The crash only triggers on opening inbox, other mailboxes seem to work
fine. It happens every time, and can be reproduced on request. I also briefly
tried 2.2.19, and it behaves the same.
The bug seems to be triggered by some mail, as I encountered it previously and
fixed by removing some spam. I guess it might be malformed header of some kind.
I can open the mailbox locally using mutt, but fail to do so remotely (using
mutt or K-9 mail on android). Unforunately, I haven't been able to isolate the
specific mail, as when I create a new mailbox, dovecot refuses to open it:
[CANNOT] Mailbox isn't a valid mbox file (0.000 + 0.000 secs).
I'm not really sure what's going on and will investigate further once I find
some time to do so.
I also experienced a similar problem on opening a specific mail, but it's much
harder to reproduce and I currently don't have an example. The crash looks very
similar, and only happens on first attempt to open a specific mail, it always
works later on.
I'm attaching a stack trace and dovecot -n. I'm also willing to send the binary
and core dump, but not publicly, as I'm not eager to share whatever's inside
with the whole world.
Other than what I mentioned, I'm running pretty standard setup, with postfix on
Gentoo x86_64, ext4 fs, quota and disk space is plentiful. The delivery agent
is
dovecot itself, in postfix/main.cf I have:
mailbox_command = /usr/libexec/dovecot/deliver
I'm using sieve script to file my mail, but the problem manifested even before
when I was still using procmail to deliver my mail (I migrated because I had
doubts about procmail and dovecot lock cooperation)
I'll keep my mailbox corrupted for a few more days, and access the mail only
locally, hoping to test a potential fix. Let me know if you need any more
info/experimentation. Also, if you know a good way to find the mail that causes
the trouble out of the core, let me know, I'd be glad to forward it for testing.
Thanks and I hope we can find (and fix) the problem!
--
S pozdravem Ladislav Láska
Katedra Aplikované Matematiky, MFF UK tel.: +420 739 464 167
# 2.2.25 (7be1766): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.15 (97b3da0)
# OS: Linux 4.0.4-gentoo x86_64 Gentoo Base System release 2.2
auth_username_format = %n
hostname = ibex.krakonos.org
login_greeting = dove...@krakonos.org ready.
mail_debug = yes
mail_location = mbox:~/.mbox
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 = *
driver = pam
}
passdb {
args = scheme=CRYPT username_format=%u /etc/dovecot/users
driver = passwd-file
}
plugin {
sieve = file:~/sieve;active=~/.dovecot.sieve
sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute
sieve_execute_socket_dir = sieve-execute
sieve_extensions = +vnd.dovecot.filter +editheader
sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter
sieve_filter_socket_dir = sieve-filter
sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe
sieve_pipe_socket_dir = sieve-pipe
sieve_plugins = sieve_extprograms
}
postmaster_address = postmas...@krakonos.org
protocols = imap
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
ssl_cert = [New LWP 23407]
Core was generated by `dovecot/imap'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7f328cf22297 in raise () from /lib64/libc.so.6
#0 0x7f328cf22297 in raise () from /lib64/libc.so.6
No symbol table info available.
#1 0x7f328cf2362a in abort () from /lib64/libc.so.6
No symbol table info available.
#2 0x7f328d317916 in default_fatal_finish (type=,
status=status@entry=0) at failures.c:201
backtrace = 0x7a48a0 "/usr/lib64/dovecot/libdovecot.so.0(+0x8d91e)
[0x7f328d31791e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8da0a)
[0x7f328d317a0a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f328d2b5fce] -> /usr"...
#3 0x7f328d317a0a in i_internal_fatal_handler (ctx=0x7ffc6c9df360,
format=, args=) at failures.c:670
status = 0
#4 0x7f328d2b5fce in i_panic (format=format@entry=0x7f328d655ce8 "file %s:
line %d (%s): assertion failed: (%s)") at failures.c:275
ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0,
timestamp_usecs = 0}
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7ffc6c9df460, reg_save_area = 0x7ffc6c9df3a0}}
#5 0x7f328d617e56 in array_idx_i (idx=, array=) at ../../../src/lib/array.h:219
No locals.
#6 index_mail_get_parsed_header (field_idx=, mail=) at index-mail-headers.c:585
value = 0x7f328d331616
"H\205\300t\025[\303\017\037"
lines_count =
value_st
Change dovecot hostname
I have noticed that the name of my private server running dovecot appears
in email headers rather than the public-friendly name of my server.
Is there a method to specify an alternate server name for the dovecot
server to use for itself in the dovecot configuration files? I performed a
few Google searches and was not able to find the answer to my question.
---
user@server1:~$ dovecot --version
2.2.9
user@server1:~$ dovecot -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.16.0-77-generic x86_64 Ubuntu 14.04.4 LTS ext4
auth_mechanisms = plain login
info_log_path = /var/log/dovecot.log
log_path = /var/log/dovecot.log
mail_location = maildir:/var/mail/vhosts/%d/%n
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 = scheme=PLAIN username_format=%u /etc/dovecot/dovecot-users
driver = passwd-file
}
protocols = " imap lmtp pop3"
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
}
}
service imap-login {
inet_listener imaps {
port = 993
ssl = yes
}
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
}
service pop3-login {
inet_listener pop3s {
port = 995
ssl = yes
}
}
ssl = required
ssl_cert =
dovecot-lda core-dumps when antispam pipe script calls it
On 2016-08-19 12:17, b...@indietorrent.org wrote:
Aha! Clearly, the vmail user cannot read from nor write to /tmp. (Why
that is, I have no idea, as the /tmp directory's permissions certainly
allow for both; maybe Dovecot implements this as a security measure.)
This prompted me to change all references to /tmp in the pipe script
to ~/tmp, and create this directory:
$ whoami
vmail
$ mkdir ~/tmp && chmod 770 ~/tmp
$ /bin/bash /usr/local/bin/sa-learn-pipe.sh --ham <
/var/vmail/gtube.txt
No errors this time (at least not on the console).
But I do get this in /var/log/mail.err:
Aug 19 12:04:24 example.com dovecot: lda(sa-train...@example.com):
Fatal: Can't open delivery mail as raw: Permission denied
I'm not sure how to interpret this message. Where is permission being
denied? More importantly, what's the fix?
Thanks for any hints!
-Ben
Apologies for the rapid-fire replies here.
The strace output that I'm capturing in the pipe script pinpointed the
problem:
open("/root/~/tmp/sendmail-msg-26272.txt", O_RDONLY) = -1 EACCES
(Permission denied)
There seems to be some expansion occurring that assumes the root user,
despite executing the pipe script as the vmail user, so I changed all
references to ~/tmp in the pipe script to /var/vmail/tmp and permission
is no longer denied.
But, now dovecot-lda is core-dumping. Here is the strace output:
http://pastebin.com/RrKmFhzC
So, I'm back to where I was with this problem two years ago.
At that time, I gave-up, because I couldn't invest the time required to
compile the latest versions of Dovecot and all plugins from scratch in
an effort to prove that the bug exists in the latest source.
"Dovecot always logs a detailed error message if something goes wrong.
If it doesn't, it's considered a bug and will be fixed." -
http://wiki2.dovecot.org/Logging
I'm happy to help identify the root-cause, but I need some guidance
here.
Thank you,
-Ben
Re: antispam plugin pipe script seems not to be called when it "should be"
Sent from my iPhone
> On Aug 19, 2016, at 11:17 AM, b...@indietorrent.org wrote:
>
>> On 2016-08-18 22:58, Edgar Pettijohn wrote:
>>> On 16-08-18 22:43:32, Ben Johnson wrote:
>>> On 8/18/2016 10:26 PM, Ben Johnson wrote:
>>> > Hello,
>>> >
>>> > (Full "doveconf -n" output is at the end of this message.)
>>> >
>>> > I'm attempting to recreate a "recipe" I had used successfully for quite
>>> > some time (in Ubuntu 12.04 LTS), which allowed me to train
>>> > SpamAssassin's Bayes database when someone dragged an email message from
>>> > one sub-folder of the account to another.
>>> >
>>> > I later tried to re-implement it (in Ubuntu 14.04 LTS), and core-dumps
>>> > resulted. I posted to this list about it several times, but nobody was
>>> > ever able to help me solve the problem.
>>> >
>>> > I just tried the same (in Ubuntu 16.04 LTS), hoping that the source had
>>> > evolved since then, and while I don't see a core-dump, the pipe script
>>> > doesn't seem to be called.
>>> >
>>> > I've booby-trapped the pipe script with quite a bit of debugging output,
>>> > which should be written to a file, but I don't see any indication that
>>> > the pipe script is ever executed.
>>> >
>>> > When logged-in as an IMAP user, and I drag a message from the user's
>>> > Inbox into the "Spam" folder, I do see the following activity in the
>>> > syslog:
>>> >
>>> > Aug 18 22:12:15 example.com imap: antispam: mailbox_is_unsure(Junk): 0
>>> > Aug 18 22:12:15 example.com imap: antispam: mailbox_is_trash(INBOX): 0
>>> > Aug 18 22:12:15 example.com imap: antispam: mailbox_is_trash(Junk): 0
>>> > Aug 18 22:12:15 example.com imap: antispam: mail copy: from trash: 0, to
>>> > trash: 0
>>> > Aug 18 22:12:15 example.com imap: antispam: mailbox_is_spam(INBOX): 0
>>> > Aug 18 22:12:15 example.com imap: antispam: mailbox_is_spam(Junk): 1
>>> > Aug 18 22:12:15 example.com imap: antispam: mailbox_is_unsure(INBOX): 0
>>> > Aug 18 22:12:15 example.com imap: antispam: mail copy: src spam: 0, dst
>>> > spam: 1, src unsure: 0
>>> > Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend
>>> > program /bin/bash
>>> > Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend
>>> > program /bin/bash
>>> > Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend
>>> > program parameter 1 /usr/local/bin/sa-learn-pipe.sh
>>> > Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend
>>> > program parameter 2 --spam
>>> >
>>> > But the piped message is never delivered to the target mailbox.
>>> > The mail log at /var/log/mail.log does not register any activity when I
>>> > move messages (and maybe that's expected).
>>> >
>>> > Here are the contents of the /usr/local/bin/sa-learn-pipe.sh script:
>>> >
>>> > http://pastebin.com/7vm74jmk
>>> >
>>> > The permissions and mode on the script seem appropriate:
>>> >
>>> > $ stat /usr/local/bin/sa-learn-pipe.sh
>>> > File: '/usr/local/bin/sa-learn-pipe.sh'
>>> > Size: 1765Blocks: 8 IO Block: 4096 regular file
>>> > Device: fd01h/64769dInode: 669345 Links: 1
>>> > Access: (0755/-rwxr-xr-x) Uid: ( 5000/ vmail) Gid: ( 5000/ vmail)
>>> > Access: 2016-08-18 19:09:47.307392919 -0400
>>> > Modify: 2016-08-18 19:09:31.231391749 -0400
>>> > Change: 2016-08-18 19:09:31.231391749 -0400
>>> > Birth: -
>>> >
>>> > What might I be doing incorrectly here?
>>> >
>>> > Please let me know if I can provide any other information.
>>> >
>>> > Thank you in advance,
>>> >
>>> > -Ben
>>> >
>>> >
>>> >
>>> > Full "doveconf -n" output:
>>> >
>>> > $ doveconf -n
>>> > # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf
>>> > # Pigeonhole version 0.4.13 (7b14904)
>>> > # OS: Linux 4.4.0-34-generic x86_64 Ubuntu 16.04.1 LTS
>>> > auth_mechanisms = plain login
>>> > disable_plaintext_auth = no
>>> > listen = *,[::]
>>> > log_timestamp = "%Y-%m-%d %H:%M:%S "
>>> > mail_max_userip_connections = 100
>>> > mail_plugins = " quota"
>>> > mail_privileged_group = vmail
>>> > passdb {
>>> > args = /etc/dovecot/dovecot-sql.conf
>>> > driver = sql
>>> > }
>>> > plugin {
>>> > antispam_backend = pipe
>>> > antispam_debug_target = syslog
>>> > antispam_pipe_program = /bin/bash
>>> > antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh
>>> > antispam_pipe_program_notspam_arg = --ham
>>> > antispam_pipe_program_spam_arg = --spam
>>> > antispam_pipe_tmpdir = /tmp
>>> > antispam_spam_pattern_ignorecase = SPAM;JUNK
>>> > antispam_trash_pattern_ignorecase = trash;Deleted *
>>> > antispam_verbose_debug = 1
>>> > quota = dict:user::file:/var/vmail/%d/%n/.quotausage
>>> > quota_rule2 = Trash:storage=+100M
>>> > quota_rule3 = Junk:ignore
>>> > quota_rule4 = INBOX:storage=+100M
>>> > quota_warning = storage=100%% quota-reached 100 %u %d
>>> > quota_warning2 = storage=95%% quota-warning 95 %u %d
>>> > quota_warning3 = storage=80%% quota-warning 80 %u %d
>>> > quota_warning4 = -storage=100%% quota-below below %u %d
>>> > sieve
Re: antispam plugin pipe script seems not to be called when it "should be"
On 2016-08-18 22:58, Edgar Pettijohn wrote:
On 16-08-18 22:43:32, Ben Johnson wrote:
On 8/18/2016 10:26 PM, Ben Johnson wrote:
> Hello,
>
> (Full "doveconf -n" output is at the end of this message.)
>
> I'm attempting to recreate a "recipe" I had used successfully for quite
> some time (in Ubuntu 12.04 LTS), which allowed me to train
> SpamAssassin's Bayes database when someone dragged an email message from
> one sub-folder of the account to another.
>
> I later tried to re-implement it (in Ubuntu 14.04 LTS), and core-dumps
> resulted. I posted to this list about it several times, but nobody was
> ever able to help me solve the problem.
>
> I just tried the same (in Ubuntu 16.04 LTS), hoping that the source had
> evolved since then, and while I don't see a core-dump, the pipe script
> doesn't seem to be called.
>
> I've booby-trapped the pipe script with quite a bit of debugging output,
> which should be written to a file, but I don't see any indication that
> the pipe script is ever executed.
>
> When logged-in as an IMAP user, and I drag a message from the user's
> Inbox into the "Spam" folder, I do see the following activity in the syslog:
>
> Aug 18 22:12:15 example.com imap: antispam: mailbox_is_unsure(Junk): 0
> Aug 18 22:12:15 example.com imap: antispam: mailbox_is_trash(INBOX): 0
> Aug 18 22:12:15 example.com imap: antispam: mailbox_is_trash(Junk): 0
> Aug 18 22:12:15 example.com imap: antispam: mail copy: from trash: 0, to
> trash: 0
> Aug 18 22:12:15 example.com imap: antispam: mailbox_is_spam(INBOX): 0
> Aug 18 22:12:15 example.com imap: antispam: mailbox_is_spam(Junk): 1
> Aug 18 22:12:15 example.com imap: antispam: mailbox_is_unsure(INBOX): 0
> Aug 18 22:12:15 example.com imap: antispam: mail copy: src spam: 0, dst
> spam: 1, src unsure: 0
> Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend
> program /bin/bash
> Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend
> program /bin/bash
> Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend
> program parameter 1 /usr/local/bin/sa-learn-pipe.sh
> Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend
> program parameter 2 --spam
>
> But the piped message is never delivered to the target mailbox.
> The mail log at /var/log/mail.log does not register any activity when I
> move messages (and maybe that's expected).
>
> Here are the contents of the /usr/local/bin/sa-learn-pipe.sh script:
>
> http://pastebin.com/7vm74jmk
>
> The permissions and mode on the script seem appropriate:
>
> $ stat /usr/local/bin/sa-learn-pipe.sh
> File: '/usr/local/bin/sa-learn-pipe.sh'
> Size: 1765Blocks: 8 IO Block: 4096 regular file
> Device: fd01h/64769dInode: 669345 Links: 1
> Access: (0755/-rwxr-xr-x) Uid: ( 5000/ vmail) Gid: ( 5000/ vmail)
> Access: 2016-08-18 19:09:47.307392919 -0400
> Modify: 2016-08-18 19:09:31.231391749 -0400
> Change: 2016-08-18 19:09:31.231391749 -0400
> Birth: -
>
> What might I be doing incorrectly here?
>
> Please let me know if I can provide any other information.
>
> Thank you in advance,
>
> -Ben
>
>
>
> Full "doveconf -n" output:
>
> $ doveconf -n
> # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.13 (7b14904)
> # OS: Linux 4.4.0-34-generic x86_64 Ubuntu 16.04.1 LTS
> auth_mechanisms = plain login
> disable_plaintext_auth = no
> listen = *,[::]
> log_timestamp = "%Y-%m-%d %H:%M:%S "
> mail_max_userip_connections = 100
> mail_plugins = " quota"
> mail_privileged_group = vmail
> passdb {
> args = /etc/dovecot/dovecot-sql.conf
> driver = sql
> }
> plugin {
> antispam_backend = pipe
> antispam_debug_target = syslog
> antispam_pipe_program = /bin/bash
> antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh
> antispam_pipe_program_notspam_arg = --ham
> antispam_pipe_program_spam_arg = --spam
> antispam_pipe_tmpdir = /tmp
> antispam_spam_pattern_ignorecase = SPAM;JUNK
> antispam_trash_pattern_ignorecase = trash;Deleted *
> antispam_verbose_debug = 1
> quota = dict:user::file:/var/vmail/%d/%n/.quotausage
> quota_rule2 = Trash:storage=+100M
> quota_rule3 = Junk:ignore
> quota_rule4 = INBOX:storage=+100M
> quota_warning = storage=100%% quota-reached 100 %u %d
> quota_warning2 = storage=95%% quota-warning 95 %u %d
> quota_warning3 = storage=80%% quota-warning 80 %u %d
> quota_warning4 = -storage=100%% quota-below below %u %d
> sieve = /var/vmail/%d/%n/.sieve
> sieve_max_redirects = 25
> }
> postmaster_address = postmas...@example.com
> protocols = imap pop3
> service auth {
> unix_listener /var/spool/postfix/private/auth {
> group = postfix
> mode = 0660
> user = postfix
> }
> unix_listener auth-userdb {
> group = vmail
> mode = 0600
> user = vmail
> }
> user = root
> }
> service imap-login {
> client_limit = 1000
> process_limit = 512
> }
> service lmtp {
> unix_listener /var/spool/postfix/private/dovecot-lmtp {
> gro
Re: a question about certificates from letsencrypt
On 08/19/2016 04:30 PM, Sven Strickroth wrote: Am 19.08.2016 um 14:40 schrieb Adrian Minta: The cert doesn't work with old clients. What do you understand under old? Ok, Windows XP clients might be problematic regarding SNI and used ciphers, but starting with Vista all clients which use the Windows CryptoAPI and Trust Store are working. Take Mozilla, there is it supported since Firefox 2.0 (I don't know right now which is the corresponding Thunderbird version, but I expect it to be supported since really early versions). Java clients are problematic as you need the latest version. Android works with >= 2.3.6 and iOS iOS >= 3.1. See https://community.letsencrypt.org/t/which-browsers-and-operating-systems-support-lets-encrypt/4394?u=mrtux for a fuller list and feel free to report more working or not working clients, I'll add them there. MTAs usually don't validate the certificates, so there should be no problem. I did encounter some problems last year with Outlook on older Windows XP machines. The problem seems to be discussed here: https://community.letsencrypt.org/t/help-needed-windows-xp-support/8756 https://community.letsencrypt.org/t/upcoming-intermediate-changes/13106 -- Best regards, Adrian Minta
Re: Dovecot & Thunderbird on shared mbox
Dovecot's log (mail_debug=yes) is clear.
The error occurs systematically on a shared mbox with subfolders: selection of
subfolders is ok, selection of the root shared folder triggers the error. the
root shared folder does not contain any mail, which is a wanted feature.
On Fri, Aug 19, 2016 at 1:04 PM, Aki Tuomi <'aki.tu...@dovecot.fi'> wrote:
On 19.08.2016 14:00, Ruga wrote:
> Occasional error from TB when selecting a dovecot's shared mbox:
>
> "Unable to open the summary file for [shared]"
> "Perhaps there was an error on disk, or the full path is too long."
>
> The server's disk is clear, and the longest full path is [a-zA-Z/.]{46}.
>
> The error occurs occasionally.
Hi!
Is there anything in your server's logfiles?
Aki
POP3 strange logging behavior after upgrade from 2.2.13 to 2.2.25
Hello, I've tested the patch and can confirm that the issue is resolved. Thank you for your assistance! Iavor Stoev Project Manager // Head of System & Network Administration Department ICDSoft Ltd - http://icdsoft.com On 18.8.2016 г. 18:14 ч., dovecot-requ...@dovecot.org wrote: Hi! This has been now fixed in https://github.com/dovecot/core/commit/7424d35ff1b7d17c0caf7b426c0ef3c2b8229afc Aki Tuomi Dovecot Oy
Re: a question about certificates from letsencrypt
Hi, On 08/19/2016 03:11 PM, Andreas Meyer wrote: > Certificates from letsencrypt are renewed every three months. I'm using a Let's Encrypt certificate w/o problems for > 6 months now (three times renewed) for web, SMTP and IMAP. As I'm also using DANE I wrote my own script for also updating the TLSA records. I don't recommend to use the official CertBot client, but use a different one (I use acmetiny; see https://community.letsencrypt.org/t/list-of-client-implementations/2103?u=mrtux for a list). Am 19.08.2016 um 14:40 schrieb Adrian Minta: > The cert doesn't work with old clients. What do you understand under old? Ok, Windows XP clients might be problematic regarding SNI and used ciphers, but starting with Vista all clients which use the Windows CryptoAPI and Trust Store are working. Take Mozilla, there is it supported since Firefox 2.0 (I don't know right now which is the corresponding Thunderbird version, but I expect it to be supported since really early versions). Java clients are problematic as you need the latest version. Android works with >= 2.3.6 and iOS iOS >= 3.1. See https://community.letsencrypt.org/t/which-browsers-and-operating-systems-support-lets-encrypt/4394?u=mrtux for a fuller list and feel free to report more working or not working clients, I'll add them there. MTAs usually don't validate the certificates, so there should be no problem. -- Best regards, Sven Strickroth PGP key id F5A9D4C4 @ any key-server
Re: a question about certificates from letsencrypt
On 19.08.2016 14:12, Aki Tuomi wrote: > Depends how your MUA validates the certificate. > > If it just checks CA, then no. Also I don't think the private key > changes, so it should not cause recheck either. Other checks, maybe. Last time I checked, the LetsEncrypt client generated a fresh key pair whenever the user requested a certificate to be renewed, unless the user explicitly opted to use the existing keys (which required some extra configuration). That should not matter much for Dovecot or other IMAP servers, but it is very important for Mail Exchangers when using DANE. -Ralph
Re: a question about certificates from letsencrypt
The cert doesn't work with old clients. On 08/19/2016 03:11 PM, Andreas Meyer wrote: Hello! Certificates from letsencrypt are renewed every three months. Does that mean a MUA has to accept the renewed certificates manually everytime it is renewed? Sorry if this is OT! Greetings Andreas -- Best regards, Adrian Minta
Re: a question about certificates from letsencrypt
On 19.08.2016 15:11, Andreas Meyer wrote: > Hello! > > Certificates from letsencrypt are renewed every three months. > > Does that mean a MUA has to accept the renewed certificates manually > everytime it is renewed? > > Sorry if this is OT! > > Greetings > > Andreas Depends how your MUA validates the certificate. If it just checks CA, then no. Also I don't think the private key changes, so it should not cause recheck either. Other checks, maybe. Aki
a question about certificates from letsencrypt
Hello! Certificates from letsencrypt are renewed every three months. Does that mean a MUA has to accept the renewed certificates manually everytime it is renewed? Sorry if this is OT! Greetings Andreas
Re: Dovecot & Thunderbird on shared mbox
On 19.08.2016 14:00, Ruga wrote:
> Occasional error from TB when selecting a dovecot's shared mbox:
>
> "Unable to open the summary file for [shared]"
> "Perhaps there was an error on disk, or the full path is too long."
>
> The server's disk is clear, and the longest full path is [a-zA-Z\/\.]{46}.
>
> The error occurs occasionally.
Hi!
Is there anything in your server's logfiles?
Aki
Dovecot & Thunderbird on shared mbox
Occasional error from TB when selecting a dovecot's shared mbox:
"Unable to open the summary file for [shared]"
"Perhaps there was an error on disk, or the full path is too long."
The server's disk is clear, and the longest full path is [a-zA-Z\/\.]{46}.
The error occurs occasionally.
