similar to: 2.0 beta4 (5d76f5b13883): Home directory not recognized

Hi, latest HG throws this error: May 8 06:42:33 spectre dovecot: master: Dovecot v2.0.beta4 (0a35407e6ff4) starting up May 8 06:48:01 spectre dovecot: imap(alias at domain.tld): Error: user alias at domain.tld: Couldn't drop privileges: Unknown mail_privileged_group: 5000 May 8 06:48:01 spectre dovecot: imap(alias at domain.tld): Error: Internal error occurred. Refer to server log for

Hi, converted my personal mailbox from 'maildir' to 'mdbox' for testing today: # dsync convert -u user at domain mdbox:~/mdbox Set mail location to mdbox in 'mail.conf' and restarted server: mail_location = mdbox:~/mdbox Dovecot panicked instantly upon login with different clients. Tried to disable several plugins to no avail: Feb 28 14:43:02 spectre dovecot:

Appears some change between 2.2.6 and 2.2.7 altered the response codes for LMTP user verification probes. Dovecot 2.2.6: Nov 2 15:50:48 spectre postfix/qmgr[627]: 3dBjr80wMgz1s: from=<double-bounce at spectre.leuxner.net>, size=271, nrcpt=1 (queue active) Nov 2 15:50:48 spectre postfix/cleanup[6226]: 3dBjr80xbYz1w: message-id=<20131102145047.2D3C6824147 at sam.dfn-cert.de> Nov 2

Let me say this is a rather cosmetic issue, but it appears with the latest commits (around 2.2.5 release) the scheme of 'Received' headers has changed for LMTP: 1) Inet socket: Return-Path: <dfn-adv-bounces at dfn-cert.de> Delivered-To: <tlx at leuxner.net> Received: from spectre.leuxner.net ([188.138.0.199]) by spectre.leuxner.net (Dovecot) with LMTP id

Latest HG reproducibly crashes when accessing a virtual namespace: Apr 22 14:49:38 spectre dovecot: master: Dovecot v2.2.12 (09c114091c88) starting up for imap, lmtp [?] Apr 22 14:50:05 spectre dovecot: imap(tlx at leuxner.net): Panic: file mail-storage.c: line 1735 (mailbox_notify_changes): assertion failed: (box->opened) Apr 22 14:50:05 spectre dovecot: imap(tlx at leuxner.net): Error: Raw

Suppose this one breaks it: http://hg.dovecot.org/dovecot-2.2/rev/c4a85c9df948 ==> /var/log/mail.log <== Jun 1 14:01:30 spectre postfix/lmtp[456]: 3bN0qP5kwFzSy: to=<tlx at leuxner.net>, relay=spectre.leuxner.net[private/dovecot-lmtp], delay=1481, delays=1481/0/0.01/0.01, dsn=4.3.0, status=deferred (host spectre.leuxner.net[private/dovecot-lmtp] said: 451 4.3.0 <tlx at

Since updating to the latest HG these errors occur. Nothing else changed in the config: $ dovecot --version 2.2.beta1 (62a930eb22b5) ==> /var/log/dovecot/dovecot.log <== Feb 18 09:47:32 spectre dovecot: lmtp(14340): Connect from local Feb 18 09:47:32 spectre dovecot: lmtp(14340, tlx at leuxner.net): Error: mkdir_parents(/var/vmail/domains/leuxner.net/tlx/mdbox) failed: File exists Feb 18

On 6 February 2018 at 20:09, David Newall <openssh at davidnewall.com> wrote: > Do we need to do anything? It's not clear to me how SSH is vulnerable to > Spectre -- that is, how SSH can be used to execute a Spectre attack? I am more concerned with it being the target of a Spectre style attack. There's some long lived private data (host keys in the case of sshd, session keys

Hello, I have a Debian machine that is virtual-hosting 6 domains with exim4. I finally got exim4 working well enough where I can send and receive mail using the mail command on my machine. I would eventually like to have SquirrelMail (which requires IMAP) working on my website. For whatever reason, exim4 doesn't seem to support IMAP. I found out that Dovecot is a prominent IMAP server.

Hi, unfortunately no core was dumped. Let me know if you need more info to debug. ==> /var/log/dovecot.log <== Mar 27 08:13:38 spectre dovecot: lmtp(8362): Connect from local Mar 27 08:13:38 spectre dovecot: lmtp(8362): Panic: file settings-parser.c: line 1501 (settings_link_get_new): assertion failed: (diff + sizeof(*old_link->array) <= old_link->parent->info->struct_size)

Patch http://hg.dovecot.org/dovecot-2.1/rev/3d8a25a4394d breaks auth May 5 09:01:52 spectre dovecot: lmtp(24442): Connect from local May 5 09:01:52 spectre dovecot: lmtp(24442): Error: userdb lookup(tlx at leuxner.net): Disconnected unexpectedly May 5 09:01:52 spectre dovecot: auth: Fatal: master: service(auth): child 24443 killed with signal 11 (core not dumped) May 5 09:01:52 spectre

==> /var/log/dovecot/dovecot.log <== Jan 30 19:57:51 spectre dovecot: master: Warning: SIGHUP received - reloading configuration Jan 30 19:58:48 spectre dovecot: imap-login: Login: user=<tlx at leuxner.net>, method=PLAIN, rip=1.2.3.4, lip=5.6.7.8, mpid=15572, TLS, session=<o4WxGYbUsQBeT5Qc> Jan 30 19:58:48 spectre dovecot: imap(tlx at leuxner.netuid=5000): Error: user tlx at

Hi, I'm seeing these after the latest Mercurial updates: ==> /var/log/dovecot.info <== Feb 28 16:07:00 spectre dovecot: master: service(lmtp): child 17322 killed with signal 11 (core dumps disabled) Regards Thomas

Hi all! I'm running an up-to-date Centos-7 on an AMD Vishera 6300, 6 core CPU. I note that when I run the redhat script to test for spectre & meltdown I get this result for variant 2: Variant #2 (Spectre): Vulnerable CVE-2017-5715 - speculative execution branch target injection - Kernel with mitigation patches: OK - HW support / updated microcode: NO - IBRS: Not disabled on

Hi, not sure what change caused this but it first appeared when building HG a30a30d1e25a. LMTP dies intermittently. Aug 6 16:00:57 spectre dovecot: lmtp(5509, alias at domain.tld): b9ESKJkVXEyFFQAAqZii3w: sieve: msgid=<1281102852.6211.447.camel at kurkku.sapo.corppt.com>: stored mail into mailbox 'Public/Mailing-Lists/Dovecot' Aug 6 16:00:57 spectre dovecot: lmtp(5509):

I'm seeing core-dumps with both 2.0-beta4 and a fresh checkout from Mercurial. I'm very new to Dovecot, so there's a good chance this is caused by my limited experience with Dovecot configuration, but it's my understanding that any core-dump is considered a bug (nice policy by the way). The installation seemed to be working as expected until I added the two namespaces and

Hi, We don't normally do X.Y.2 releases, but there has been some interest in getting a 5.0.2 release out with the Spectre mitigations included, so I am proposing the following schedule for a 5.0.2 release: LLVM 5.0.2 -rc1 Mon Mar 19 -final Mon Mar 26 To keep things easy for testers, 5.0.2 will be for Spectre related fixes only and won't be opened up for general bugs. And here is

Hi Johnny, Thank you for your reply. It seems to me that my message may have came around as offensive but that was not my intend. I have basic understanding how things work and when I said CentOS I actually meant Red Hat and all its derivatives. I asked CentOS community because that's the community I'm member of. Not to say that CentOS is not secure or anything like that. Anyway,

By now, we're sure most everyone have heard of the Meltdown and Spectre attacks. If not, head over to https://meltdownattack.com/ and get an overview. Additional technical details are available from Google Project Zero. https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html The FreeBSD Security Team was notified of the issue in late December and received a

By now, we're sure most everyone have heard of the Meltdown and Spectre attacks. If not, head over to https://meltdownattack.com/ and get an overview. Additional technical details are available from Google Project Zero. https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html The FreeBSD Security Team was notified of the issue in late December and received a