similar to: Push Notification clarification (MessageNew w/o LMTP or LDA)

Hello, On Thu, 9 May 2019 09:14:13 +0300 Aki Tuomi via dovecot wrote: > On 9.5.2019 9.01, Christian Balzer via dovecot wrote: > > Hello, > > > > Both the examples on the Push Notification wiki page and the XAPS plugin > > docs seem to suggest or state that LMTP/LDA is required. > > It is required. > Thanks for the quick, but unwelcome reply. There's a

On 9.5.2019 9.01, Christian Balzer via dovecot wrote: > Hello, > > Both the examples on the Push Notification wiki page and the XAPS plugin > docs seem to suggest or state that LMTP/LDA is required. It is required. > However IMAP IDLE notifications work without either of these (please no > religious discussion of why Dovecot LMTP is the best thing since sliced > bread and

Another concern is that Apple is planning to discontinue the binary notification-submission endpoint late this year --- it's been replaced by a (significantly nicer, IMHO) http2-based endpoint, but a quick look at the xaps daemon looks like it's using the old protocol.

Hi, I just updated my Dovecot to the new build in Fedora 26, which is based on 2.2.31. After I did that, Evolution (3.24.3) is no longer receiving notifications about new mail in folders other than inbox (the same version of Evo that worked fine against Dovecot 2.2.30.2). The only folder that still gets notifications is inbox. I see there have been changes to NOTIFY code in this release. What

Hi list, The NOTIFY extension (RFC 5465) works fine for mailboxes in the "virtual/" namespace, but it crashes the IMAP client when used with a mailbox in the empty "" namespace: ~$ /usr/lib/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 ? NOTIFY SPECIAL-USE] Logged in as guilhem a NAMESPACE * NAMESPACE (("" "/")("virtual/"

https://github.com/st3fan/dovecot-xaps-daemon Works PERFECTLY. I use it on CentOS 6 and 7. Thanks, Steffan Cline steffan at hldns.com 602-793-0014 > On Jan 8, 2020, at 2:39 PM, infoomatic <infoomatic at gmx.at> wrote: > > ?I have no idea about that Mac proprietary stuff ... however, > https://doc.dovecot.org/configuration_manual/push_notification/ might be > a

Quoting RFC 5465 (NOTIFY): ?If the NOTIFY command enables MessageNew, MessageExpunge, AnnotationChange, or FlagChange notifications for a mailbox other than the currently selected mailbox, and the client has specified the STATUS indicator parameter, then the server MUST send a STATUS response for that mailbox before NOTIFY's tagged OK. [?] If either AnnotationChange or

I?m posting this here and will in a couple other places to see if anyone has any experience with this and knows what I can do. My setup is CentOS 6 with postfix, procmail and dovecot administered via Virtualmin. Postfix of course receives the email. Procmail uses it?s hooks to run the email through spam assassin and clamd. After than procmail hands it off to dovecot/deliver to drop it in the

I?ve been hacking on a personal side project to support native iOS Push Email in Dovecot. This is specifically for people who are migrating their mail away from OS X Server while keeping their existing Push Email functionality. Native Push Email has some great advantages: it speeds up email notifications (usually within seconds of being handled by dovecot-lda) and it improves battery life since

> 1500 IMAP sessions will eat up about 3GB alone. Are you saying that Dovecot needs 2MB of physical memory per IMAP session? If I want to support a max 100,000 IMAP sessions per server, I should configure the server to have at least 200GBs of SWAP? > On Feb 10, 2017, at 3:58 AM, Christian Balzer <chibi at gol.com> wrote: > > On Fri, 10 Feb 2017 01:13:20 +0530 Rajesh M wrote:

> 1. 256GB of real RAM, swap is for chums. Are you sure that 100,000 IMAP sessions wouldn?t work well with SWAP, especially with fast SSD storage (which is a lot cheaper than RAM)? Seems that these IMAP processes are long lived processes (idling most of the time) that don?t need that much of the contents of real memory available for much of the life of the process. I use a database proxy in

Hello, On Thu, 6 Apr 2017 09:24:23 +0300 Aki Tuomi wrote: > On 06.04.2017 07:02, Christian Balzer wrote: > > > > Hello, > > > > this is on Debian Jessie box, dovecot 2.2.27 from backports, > > imap-hibernate obviously enabled. > > > > I've been seeing a few of these since starting this cluster (see previous > > mail), they all follow the

Thanks for the info. I do have one further question for you. On your servers that are currently handling 50k IMAP sessions, how many users does that correspond to? Since many users will have multiple IMAP sessions on multiple devices, I?d like to hear about some real-world numbers that could be used for budgeting a new project like mine. Also, do you use Dovecot IMAP proxies in front of your

Daniel, thanks so much for the detailed pointers. So it turns out to be both the evil that is systemd and an overzealous upgrade script. Apollon, should I raise a Debian bug for this? As for reasons, how do 50k proxy session on the proxy servers and 25k imap processes on the mailbox servers sound? Even on a server with just 6k users and 7k imap processes that causes a massive load spike and a

Hi, I've very old Dovecot version so I'm trying to migrate new disk and current version of dovecot. But POP3 accounts have "version 1" .INBOX/dovecot-uidlist files so clients download the messages again. How can achieve not to download to mailbox after copy to new disk? Is there any script or something to migrate index v1 to v3? thanks for your suggestions.

thanks for your help happy to say that the performance dramatically improved after i use the high performance settings from here http://wiki.dovecot.org/LoginProcess grep Login: /var/log/mail.log.1 |wc -l with the mail.log being of a typical, busy day. 412992 i also picked up the imap and pop3 connections during peak hours [root at ns1 domains]# doveadm who | awk

While it's documented that the OX push_notification_driver only supports MessageNew events, it does NOT generate any event if a Sieve script moves the message on arrival to an other folder, neither in INBOX were it original arrives by LMTP, nor in the folder Sieve moves the message. Is that a misconfiguration on my side, or a know / desired limitation or just a bug? I use LMTP to deliver

Hello, as the tin says. I have several servers running 2.2.27 (Debian stretch) and am adding new ones with 2.3.4.1 (Debian buster). The configs were upgraded where needed but neither 10-mail.conf nor 15-mailboxes.conf were changed. 15-mailboxes is all commented out (I guess the default is auto-create, which isn't documented anywhere I could find) and the only non-comments in 10-mail.conf are

christian the servers i currently own are dell servers. The servers i plan to buy are Dell R530, 2U rack servers with 8 x 3.5 inch drives, with 64 gb ram each, Hardware raid. I am thinking of 2 X 300 gb ssds raid1 and 6 x 2 tb drives in raid10 for data. I do not have any experience in setting up drdb (that would be my next step) ... primarily using standalone servers with hardware level

Hello, Dovecot 2.2.27 (Debian Jessie backports). When issuing a "doveadm kick" for a specific user I was greeted by: --- "warning: other connections would also be kicked from following users:" --- and a list of 22odd thousand users. As it turns out, kick wants to smack the hibernation proces(ses) that have hibernated sessions for this user, obviously the wrong approach here.