Displaying 20 results from an estimated 800 matches similar to: ""NOTIFY SET (mailboxes INBOX (...))" crashes the IMAP client"
2015 Jul 26
1
NOTIFY regression: 2.18 no longer notifies of events in INBOX
Here is an example with APPEND
$ /usr/lib/dovecot/imap
S1: * PREAUTH [CAPABILITY IMAP4rev1 ? MOVE NOTIFY SPECIAL-USE] Logged in as guilhem
C1: a1 NOTIFY SET (INBOXES (MessageNew MessageExpunge FlagChange))
S1: a1 OK NOTIFY completed (0.000 secs)
$ /usr/lib/dovecot/imap
S2: * PREAUTH [CAPABILITY IMAP4rev1 ? MOVE NOTIFY SPECIAL-USE] Logged in as guilhem
C2: a2 APPEND
2015 Jul 19
1
RFC 5465 (NOTIFY) violation: missing HIGHESTMODSEQ in initial STATUS responses
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
2015 Jul 26
0
"NOTIFY SET (mailboxes INBOX (...))" crashes the IMAP client
On Sun, 19 Jul 2015 at 19:21:16 +0200, Guilhem Moulin wrote:
> The "subtree" mailbox filter has the same problem, but the
> non-parameterized ones ("inboxes", "personal" and "subscribed") work
> fine.
Actually there are further problem with the INBOX namespace, to which I'm
subscribed:
$ /usr/lib/dovecot/imap
S1: * PREAUTH [CAPABILITY
2017 Jun 29
3
NOTIFY broken in 2.2.31?
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
2016 Apr 27
2
Crash: setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" NIL)
On 27.04.2016 11:00, Heiko Schlittermann wrote:
> Hi,
>
>> ? login ?
>> C: 2 setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" NIL)
>>
>> Apr 27 09:29:16 backend1 dovecot: imap-login: Login: user=<heiko>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=6651, secured
>> Apr 27 09:29:16 backend1 dovecot: imap(heiko):
2019 May 25
0
Race condition in IMAP NOTIFY for events received NOTIFY_DELAY_MSECS apart
Hi there,
There seem to be a race condition in IMAP NOTIFY: when two events for
the SELECTED mailbox are received soon after one another, sometimes only
the first one is being reported to clients that enabled IMAP NOTIFY. On
closer look it seems like this is most often reproducible when the delay
between the two events is NOTIFY_DELAY_MSECS (500ms). This is with
2.3.4.1 from Debian sid.
$
2015 Sep 15
1
2.2.18 Regression: Incorrect STATUS response for virtual mailboxes
As shown below, adding a message to TRASH doesn't increase
virtual/test's MESSAGES count. However SELECTing virtual/test triggers
the increase; so does running `doveadm mailbox status vsize
virtual/test` in another shell.
$ mkdir -m0700 ~/mail/virtual/test
$ echo -e "TRASH\n\tall" > ~/mail/virtual/test/dovecot-virtual
$ /usr/lib/dovecot/imap
S: * PREAUTH [CAPABILITY
2012 Feb 26
0
IMAP NOTIFY extension
http://hg.dovecot.org/dovecot-2.2-notify/ contains the initial implementation of IMAP NOTIFY extension. It's less than half-working, but the difficult part of it is done I think. If I give it a command like:
x notify set (personal (messagenew messageexpunge flagchange))
and then in another session I copy a message to another mailbox, it sends:
* STATUS "foobar" (MESSAGES 77
2017 Jun 30
0
NOTIFY broken in 2.2.31?
On 29 Jun 2017, at 13.27, Bojan Smojver <bojan at rexursive.com> wrote:
>
> 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
2019 Nov 12
1
IMAP session hangs on 8k-long commands if COMPRESS=DEFLATE is enabled
Hi there,
Dovecot 2.3.7 appears to hang when the client sends a long command after
enabling the IMAP COMPRESS extension [RFC 4978]. PoC script attached
along with the doveconf(1) output.
Without COMPRESS=DEFLATE, and with the default ?imap_max_line_length?
value (64k) I'm able send commands up to 65539 bytes long (that's 3
bytes more than 2??, so maybe the leading tag and the trailing
2016 Aug 22
1
RFC 3501 violation in FETCH BODY responses
Hi there,
Quoting RFC 3501 sec. 7.4.2 ?FETCH Response? (data item BODYSTRUCTURE):
?A body type of type MESSAGE and subtype RFC822 contains,
immediately after the basic fields, the envelope structure, body
structure, and size in text lines of the encapsulated message.?
According the ABNF (RFC 3501 sec. 9) the envelope structure is that of
the ENVELOPE FETCH data item, and the
2018 Aug 05
1
Assertion failure with IMAP NOTIFY
Hi,
For a few weeks I've been running a custom notification script[1] that
uses IMAP NOTIFY. The script uses a single connection, sets up a NOTIFY
watch on a couple of mailboxes + automatic FETCH for the selected
mailbox. If a status update arrives for a different mailbox, it selects
that box and fetches the mail.
Today I got the following error in the log:
> Aug 5 14:56:12 karif
2020 Jun 21
0
Bug[?]report: duplicate response
hi,
i'm not sure if i've discovered a bug or if i'm not following the IMAP
specs correctly.
observations:
{ echo -en "a1 login foo bar\r\na2 notify set (subscribed (FlagChange SubscriptionChange MessageNew MessageExpunge))\r\n"; cat - } | openssl s_client -connect [my_dovecot_server]:993
produces the following output (aside from the openssl s_client
cert-inspection
2009 Jun 18
2
Hatched symbols
Hello,
I would like to build rectangles in a plot and use color and different type
of hatching for filling rectangles. I don't find the way to draw hatchings.
I'm thinking to build segment by segment inside each rectangle but I'm sure
that exists a better way to do that. I didn't find any documentation about
that.
> symbols(1,1,rectangles=cbind(1,1),bg="red", ...
2021 Jan 02
6
[Bug 3246] New: Include directive doesn't support variable expansion
https://bugzilla.mindrot.org/show_bug.cgi?id=3246
Bug ID: 3246
Summary: Include directive doesn't support variable expansion
Product: Portable OpenSSH
Version: 8.4p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
Assignee:
2015 Mar 06
3
[Bug 2362] New: Please add a possibility to disable IdentityFiles
https://bugzilla.mindrot.org/show_bug.cgi?id=2362
Bug ID: 2362
Summary: Please add a possibility to disable IdentityFiles
Product: Portable OpenSSH
Version: 6.7p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
Assignee: unassigned-bugs
2015 Nov 04
1
samba4 server member of a samba 3 domain
Hi,
I try to configure a samba 4.1.17 server member of a samba3.5.6 (ldap
backend ) domain.
i can mount the smb share on a windows client but i cant modify the acl.
this is the samba server logs:
create_canon_ace_lists: unable to map SID
S-1-5-21-856890099-1868262392-538272213-2012 to uid or gid
when i try to manually map SID to UID with wbinfo:
wbinfo -S
2019 May 09
2
Push Notification clarification (MessageNew w/o LMTP or LDA)
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.
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 that everybody should use it).
The LUA part of the push notification docs however states that events other
2006 Nov 06
4
Event listeners
Hi!
Your plugin is really great! Thanks.
One more little question.
Is it possible to add event listeners to the maps via your plugin?
greetings
/till
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ym4r-user/attachments/20061106/6b1c6f4f/attachment.html
2013 Apr 29
2
CATENATE allows empty messages
Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE:
b1 append inbox catenate (text {0+}
)
b1 OK [APPENDUID 1366726248 12] Append completed.
Contrast this with regular APPEND:
b2 append inbox {0+}
b2 NO Can't save a zero byte message.
Note that zero-size literals are OK but zero-size messages are not. So while "b1" above should fail like "b2",