a little bit late but now.
As far as I can see, no EXISTS, after idling
Even can't see the additional output in the logmessages.
Looks like the code is never reached?
telnet:
- OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=CRAM-MD5 AUTH=DIGEST-MD5] ready. a login xxx xxxxx a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in b select inbox
- FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk)
- OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk \*)] Flags permitted.
- 6 EXISTS
- 0 RECENT
- OK [UIDVALIDITY 1252958392] UIDs valid
- OK [UIDNEXT 41] Predicted next UID
- OK [HIGHESTMODSEQ 104] Highest b OK [READ-WRITE] Select completed. c idle
- idling
- OK Still here
- OK Still here
logfile
Nov 04 12:20:47 dovecot: Info: This is Dovecot's info log Nov 04 12:20:47 dovecot: Warning: This is Dovecot's warning log Nov 04 12:20:47 dovecot: Error: This is Dovecot's error log Nov 04 12:20:47 dovecot: Fatal: This is Dovecot's fatal log Nov 04 12:25:01 IMAP(ingo): Info: Effective uid=20000, gid=20000, home=/mnt/mail/home/ingo Nov 04 12:25:01 IMAP(ingo): Info: dbox: data=/mnt/mail/mail/ingo:INDEX=/var/spool/indexes/ingo Nov 04 12:25:01 IMAP(ingo): Info: fs: root=/mnt/mail/mail/ingo, index=/var/spool/indexes/ingo, control=, inbox= Nov 04 12:25:01 imap-login: Info: Login: user=<ingo>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: Loading modules from directory: /opt/dovecot/lib/dovecot/lda Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: Module loaded: /opt/dovecot/lib/dovecot/lda/lib90_sieve_plugin.so Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: auth input: home=/mnt/mail/home/ingo Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: auth input: mail=dbox:/mnt/mail/mail/ingo:INDEX=/var/spool/indexes/ingo Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: auth input: uid=20000 Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: auth input: gid=20000 Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: dbox: data=/mnt/mail/mail/ingo:INDEX=/var/spool/indexes/ingo Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: fs: root=/mnt/mail/mail/ingo, index=/var/spool/indexes/ingo, control=, inbox= Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: sieve: using sieve path for user's script: /mnt/mail/home/ingo/.dovecot.sieve Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: sieve: opening script /mnt/mail/home/ingo/.dovecot.sieve Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: sieve: executing compiled script /mnt/mail/home/ingo/.dovecot.sieve Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: sieve: msgid=OF7BC0B05A.AEFFD6E5-ONC1257664.003EC4A0-C1257664.003ECD23@conrad.de: forwarded to ingo@a263722.exchange-mail.eu Nov 04 12:26:28 deliver(ingo@ghostdive.org): Info: sieve: msgid=OF7BC0B05A.AEFFD6E5-ONC1257664.003EC4A0-C1257664.003ECD23@conrad.de: stored mail into mailbox 'INBOX'
after that nothing more. Must I change some switch?
raw-log in
<<
<< raw-log out <<
<<<* FLAGS (\Answered \Flagged \Deleted \Seen \Draft
NonJunk) OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk
\*)] Flags permitted. 6
EXISTS 0
RECENT OK [UIDVALIDITY 1252958392] UIDs
valid OK [UIDNEXT 41] Predicted next
UID OK [HIGHESTMODSEQ 104]
Highest b OK [READ-WRITE] Select
completed. <<<+
idling <<<* OK Still
here <<<* OK Still
here <<<* OK Still
here Timo Sirainen schrieb: You seem to have kind of mixed everything into one so I don't know what
happened. Rawlog (*.in, *.out files) isn't the same as where my patch
was logging the message, it went to Dovecot's error log
http://wiki.dovecot.org/Logging. Also do you mean there was no EXISTS
reply sent at all after IDLE was started in either rawlog or telnet
session? So the most important thing: After deliver logs the message, how long
does it take for "inotify triggered" message to get written to Dovecot's
log file? Or does it never get logged there? (Make sure you're looking
at the log file where dovecot --log-error writes "This is Dovecot's
warning log.")