Re: CLOSE crash the imap server
Hi
I installed the 2.3.9 (the last openpkg) and got the same problem.
Regards
On 8/13/07, Alain Spineux <[EMAIL PROTECTED]> wrote:
>
> Here is a small piece of python that (crash the server) the trick
>
> import imaplib, sys, types
>
> imap_server='localhost'
> #imap_server='fc6-eg.asxnet.loc'
> imap_port=143
> imap_login='manager'
> imap_password='vishnou'
>
> mailbox='user/catchall.teta.loc/[EMAIL PROTECTED]'
> #mailbox=' user/catchall.alpha.loc/[EMAIL PROTECTED]'
>
> imap_con=imaplib.IMAP4(imap_server, imap_port)
> typ, dat=imap_con.login(imap_login, imap_password)
>
> typ, dat=imap_con.setacl(mailbox, imap_login, 'lrd')
> print '%s, %s=SETACL %s' % (typ, dat, mailbox)
> typ, dat=imap_con.select(mailbox)
> print '%s, %s=SELECT %s' % (typ, dat, mailbox)
> #typ, dat=imap_con.uid('search', None, 'ALL')
> #print '%s, %s=UID SEARCH %s' % (typ, dat, mailbox)
> typ, dat=imap_con.close()
> print '%s, %s=CLOSE %s' % (typ, dat, mailbox)
> typ, dat=imap_con.logout()
> print '%s, %s=LOGOUT %s' % (typ, dat, mailbox)
>
> and its output
>
>
> OK, ['Completed']=SETACL user/catchall.teta.loc/[EMAIL PROTECTED]
> OK, ['1']=SELECT user/catchall.teta.loc/[EMAIL PROTECTED]
> Traceback (most recent call last):
> File "cyrus_bug.py", line 21, in
> typ, dat=imap_con.close()
> File "/kolab/lib/python/imaplib.py", line 376, in close
> typ, dat = self._simple_command('CLOSE')
> File "/kolab/lib/python/imaplib.py", line 1055, in _simple_command
> return self._command_complete(name, self._command(name, *args))
> File "/kolab/lib/python/imaplib.py", line 887, in _command_complete
> raise self.abort('command: %s => %s' % (name, val))
> imaplib.abort: command: CLOSE => socket error: EOF
>
> Regards
>
>
>
> On 8/13/07, Alain Spineux <[EMAIL PROTECTED]> wrote:
> >
> >
> > Something strange append with my cyrus-imap 2.3.8 from openpkg
> > imapd-2.3.8-20070720
> >
> > When I CLOSE a mailbox, (after a SELECT), the server die and close the
> > connection !
> > Look the FIN (F) packet at 16:14:25.869642
> >
> > Here are the relevant the cyrus log (around 16:14:25)
> >
> > cyrmaster.log:Aug 13 16:14:25 eg01 master[32578]: process 21432
> > exited, signaled to death by 11
> > cyrmaster.log:Aug 13 16:14:25 eg01 master[32578]: service imap
> > pid 21432 in BUSY state: terminated abnormally
> > cyrmaster.log:Aug 13 16:14:25 eg01 master[21531]: about to exec
> > /kolab/bin/imapd
> >
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484170
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting
> > txn 2147484170
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484171
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn
> > 2147484171
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing
> > txn 2147484171
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484172
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting
> > txn 2147484172
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484173
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn
> > 2147484173
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing
> > txn 2147484173
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484174
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting
> > txn 2147484174
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484175
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn
> > 2147484175
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing
> > txn 2147484175
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484176
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting
> > txn 2147484176
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484177
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn
> > 2147484177
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing
> > txn 2147484177
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484178
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting
> > txn 2147484178
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > txn 2147484179
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn
> > 2147484179
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing
> > txn 2147484179
> > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: open: user manager
> > opened user/[EMAIL PROTECTED]
> >
> > Here is the ASCII's tcpdump
> >
> > ODPO12 SETACL " user/[EMAIL PROTECTED]" manager lrd..
> > 16:14:25.857715 IP eg01.imap > eg01.55867: P 457:478(21) ack 544 win 256
> >
> > ODPO12 OK Completed..
> > 16:14:25.858710 IP eg01.55867 > eg01.imap: P 544:588(44) ack 478 win 290
> >
> > ODPO13 SELECT "user/
Re: CLOSE crash the imap server
The same problem append with Thuderbird when : renaming, deleting, moving a
folder.
On 8/29/07, Alain Spineux <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I installed the 2.3.9 (the last openpkg) and got the same problem.
>
> Regards
>
> On 8/13/07, Alain Spineux < [EMAIL PROTECTED]> wrote:
> >
> > Here is a small piece of python that (crash the server) the trick
> >
> > import imaplib, sys, types
> >
> > imap_server='localhost'
> > #imap_server='fc6-eg.asxnet.loc'
> > imap_port=143
> > imap_login='manager'
> > imap_password='vishnou'
> >
> > mailbox='user/catchall.teta.loc/[EMAIL PROTECTED] '
> > #mailbox=' user/catchall.alpha.loc/[EMAIL PROTECTED]'
> >
> > imap_con=imaplib.IMAP4(imap_server, imap_port)
> > typ, dat=imap_con.login(imap_login, imap_password)
> >
> > typ, dat=imap_con.setacl(mailbox, imap_login, 'lrd')
> > print '%s, %s=SETACL %s' % (typ, dat, mailbox)
> > typ, dat=imap_con.select(mailbox)
> > print '%s, %s=SELECT %s' % (typ, dat, mailbox)
> > #typ, dat=imap_con.uid('search', None, 'ALL')
> > #print '%s, %s=UID SEARCH %s' % (typ, dat, mailbox)
> > typ, dat=imap_con.close()
> > print '%s, %s=CLOSE %s' % (typ, dat, mailbox)
> > typ, dat=imap_con.logout()
> > print '%s, %s=LOGOUT %s' % (typ, dat, mailbox)
> >
> > and its output
> >
> >
> > OK, ['Completed']=SETACL user/catchall.teta.loc/[EMAIL PROTECTED]
> > OK, ['1']=SELECT user/catchall.teta.loc/[EMAIL PROTECTED]
> > Traceback (most recent call last):
> > File "cyrus_bug.py", line 21, in
> > typ, dat=imap_con.close()
> > File "/kolab/lib/python/imaplib.py", line 376, in close
> > typ, dat = self._simple_command('CLOSE')
> > File "/kolab/lib/python/imaplib.py", line 1055, in _simple_command
> > return self._command_complete(name, self._command(name, *args))
> > File "/kolab/lib/python/imaplib.py", line 887, in _command_complete
> > raise self.abort('command: %s => %s' % (name, val))
> > imaplib.abort: command: CLOSE => socket error: EOF
> >
> > Regards
> >
> >
> >
> > On 8/13/07, Alain Spineux <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Something strange append with my cyrus-imap 2.3.8 from openpkg
> > > imapd-2.3.8-20070720
> > >
> > > When I CLOSE a mailbox, (after a SELECT), the server die and close the
> > > connection !
> > > Look the FIN (F) packet at 16:14:25.869642
> > >
> > > Here are the relevant the cyrus log (around 16:14:25)
> > >
> > > cyrmaster.log:Aug 13 16:14:25 eg01 master[32578]: process
> > > 21432 exited, signaled to death by 11
> > > cyrmaster.log:Aug 13 16:14:25 eg01 master[32578]: service imap
> > > pid 21432 in BUSY state: terminated abnormally
> > > cyrmaster.log:Aug 13 16:14:25 eg01 master[21531]: about to
> > > exec /kolab/bin/imapd
> > >
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484170
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn:
> > > aborting txn 2147484170
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484171
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing
> > > txn 2147484171
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit:
> > > committing txn 2147484171
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484172
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn:
> > > aborting txn 2147484172
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484173
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing
> > > txn 2147484173
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit:
> > > committing txn 2147484173
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484174
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn:
> > > aborting txn 2147484174
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484175
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing
> > > txn 2147484175
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit:
> > > committing txn 2147484175
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484176
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn:
> > > aborting txn 2147484176
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484177
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing
> > > txn 2147484177
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit:
> > > committing txn 2147484177
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484178
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn:
> > > aborting txn 2147484178
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting
> > > txn 2147484179
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing
> > > txn 2147484179
> > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit:
> > > committing txn 2147484179
> > > imapd.log:Aug 13 16:1
Re: sieve and date
Zitat von Robert Banz <[EMAIL PROTECTED]>: > > > Following on to the sieve & vacation discussion -- anyone have any > interest in the sieve "date" extension? Sounds like it'd be awfully > nice to have, for example, being able to wrap your vacation in a date- > range conditional... Definitely. We currently hack around this in Ingo with some wicked Received: header regexp that I really feel uncomfortable with. A date extension would be of great help. Jan. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: CLOSE crash the imap server
I opened this bug report https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2986 Regards On 8/13/07, Alain Spineux <[EMAIL PROTECTED]> wrote: > > > Something strange append with my cyrus-imap 2.3.8 from openpkg > imapd-2.3.8-20070720 > > When I CLOSE a mailbox, (after a SELECT), the server die and close the > connection ! > Look the FIN (F) packet at 16:14:25.869642 > > Here are the relevant the cyrus log (around 16:14:25) > > cyrmaster.log:Aug 13 16:14:25 eg01 master[32578]: process 21432 > exited, signaled to death by 11 > cyrmaster.log:Aug 13 16:14:25 eg01 master[32578]: service imap pid > 21432 in BUSY state: terminated abnormally > cyrmaster.log:Aug 13 16:14:25 eg01 master[21531]: about to exec > /kolab/bin/imapd > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484170 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > txn 2147484170 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484171 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > 2147484171 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > txn 2147484171 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484172 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > txn 2147484172 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484173 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > 2147484173 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > txn 2147484173 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484174 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > txn 2147484174 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484175 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > 2147484175 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > txn 2147484175 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484176 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > txn 2147484176 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484177 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > 2147484177 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > txn 2147484177 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484178 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > txn 2147484178 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting txn > 2147484179 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > 2147484179 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > txn 2147484179 > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: open: user manager > opened user/[EMAIL PROTECTED] > > Here is the ASCII's tcpdump > > ODPO12 SETACL "user/[EMAIL PROTECTED]" manager lrd.. > 16:14:25.857715 IP eg01.imap > eg01.55867: P 457:478(21) ack 544 win 256 > > ODPO12 OK Completed.. > 16:14:25.858710 IP eg01.55867 > eg01.imap: P 544:588(44) ack 478 win 290 > > ODPO13 SELECT "user/[EMAIL PROTECTED]".. > 16:14:25.859297 IP eg01.imap > eg01.55867: P 478:777(299) ack 588 win 256 > > * FLAGS (\Answered \Flagged \Draft \Deleted \Seen).. > * OK [PERMANENTFLAGS (\Deleted)] .. > * 0 EXISTS.. > * 0 RECENT.. > * OK [UIDVALIDITY 1187010780] .. > * OK [UIDNEXT 2] .. > * OK [NOMODSEQ] Sorry, modsequences have not been enabled on this > mailbox.. > * OK [URLMECH INTERNAL].. > ODPO13 OK [READ-WRITE] Completed.. > 16:14:25.860638 IP eg01.55867 > eg01.imap: P 588:611(23) ack 777 win 299 > > ODPO14 UID SEARCH ALL.. > 16:14:25.860913 IP eg01.imap > eg01.55867: P 777:831(54) ack 611 win 256 > > * SEARCH.. > ODPO14 OK Completed (0 msgs in 0.000 secs).. > 16:14:25.862171 IP eg01.55867 > eg01.imap : P 611:625(14) ack 831 win 299 > > ODPO15 CLOSE.. > 16:14:25.869642 IP eg01.imap > eg01.55867: F 831:831(0) ack 625 win 256 > > 16:14: 25.906271 IP eg01.55867 > eg01.imap: . ack 832 win 299 > > 16:14:25.933508 IP eg01.55867 > eg01.imap: P 625:638(13) ack 832 win 299 > > ODPO16 NOOP.. > 16:14:25.933539 IP eg01.imap > eg01.55867: R 3474995568:3474995568(0) win > 0 > 16:14:25.934034 IP eg01.55871 > eg01.imap: S 3508738700:3508738700(0) win > 32792 > 16:14:25.934062 IP eg01.imap > eg01.55871: S 3501230146:3501230146(0) ack > 3508738701 win 32768 47451750,nop,wscale 7> > 16:14:25.934081 IP eg01.55871 > eg01.imap: . ack 1 win 257 > > 16:14:25.964179 IP eg01.imap > eg01.55871: P 1:117(116) ack 1 win 256 > > * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID STARTTLS] eg01 Cyrus IMAP4 > v2.3.8-openpkg server ready.. > 16:14:25.964335 IP eg01.55871 > eg01.imap: . ack 117 win 257 > > 16:14:25.964595 IP eg01.55871 > eg01.imap: P 1:19(18) ack 117 win 257 > > IECD0 CAPABILITY.. > > > Here is another transcript and logs, but the SEARCH returned some emails, > I delete them then CLOSE
Re: sieve and date
Here's the extension I'm referring to: http://tools.ietf.org/wg/sieve/draft-freed-sieve-date-index-06.txt On Aug 29, 2007, at 09:38, Jan Schneider wrote: > Zitat von Robert Banz <[EMAIL PROTECTED]>: > >> >> >> Following on to the sieve & vacation discussion -- anyone have any >> interest in the sieve "date" extension? Sounds like it'd be awfully >> nice to have, for example, being able to wrap your vacation in a >> date- >> range conditional... > > Definitely. We currently hack around this in Ingo with some wicked > Received: header regexp that I really feel uncomfortable with. A date > extension would be of great help. > > Jan. > > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
cyrus 2.0.3 sieve?
What can sieve in cyrus 2.0.3 do? I know it can do 'fileinto'. I'm trying to test 'vacation' and 'imapflags'. Is there some way to see what sieve can do like a CAPABILITIES line? Mike Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: CLOSE crash the imap server
Is-it possible for someone running kolab to confirm this problem ? Can someone run my python script (dont forget to configure your owne server/mailbox) Here is the response a got from cyrus : http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2986 --- Comment #1 from Ken Murchison <[EMAIL PROTECTED]> 2007-08-29 12:09:14 --- I can't reproduce this problem with an unmodified 2.3.9. Perhaps this is a bug with the Kolab patches. Can you get me a backtrace from an imapd core dump? Regards On 8/29/07, Alain Spineux <[EMAIL PROTECTED]> wrote: > > I opened this bug report > > https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2986 > > Regards > > On 8/13/07, Alain Spineux <[EMAIL PROTECTED]> wrote: > > > > > > Something strange append with my cyrus-imap 2.3.8 from openpkg > > imapd-2.3.8-20070720 > > > > When I CLOSE a mailbox, (after a SELECT), the server die and close the > > connection ! > > Look the FIN (F) packet at 16:14:25.869642 > > > > Here are the relevant the cyrus log (around 16:14:25) > > > > cyrmaster.log:Aug 13 16:14:25 eg01 master[32578]: process 21432 > > exited, signaled to death by 11 > > cyrmaster.log:Aug 13 16:14:25 eg01 master[32578]: service imap > > pid 21432 in BUSY state: terminated abnormally > > cyrmaster.log:Aug 13 16:14:25 eg01 master[21531]: about to exec > > /kolab/bin/imapd > > > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484170 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > > txn 2147484170 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484171 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > > 2147484171 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > > txn 2147484171 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484172 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > > txn 2147484172 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484173 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > > 2147484173 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > > txn 2147484173 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484174 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > > txn 2147484174 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484175 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > > 2147484175 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > > txn 2147484175 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484176 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > > txn 2147484176 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484177 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > > 2147484177 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > > txn 2147484177 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484178 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: abort_txn: aborting > > txn 2147484178 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: myfetch: starting > > txn 2147484179 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mystore: reusing txn > > 2147484179 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: mycommit: committing > > txn 2147484179 > > imapd.log:Aug 13 16:14:25 eg01 imap[21432]: open: user manager > > opened user/[EMAIL PROTECTED] > > > > Here is the ASCII's tcpdump > > > > ODPO12 SETACL " user/[EMAIL PROTECTED]" manager lrd.. > > 16:14:25.857715 IP eg01.imap > eg01.55867: P 457:478(21) ack 544 win 256 > > > > ODPO12 OK Completed.. > > 16:14:25.858710 IP eg01.55867 > eg01.imap: P 544:588(44) ack 478 win 290 > > > > ODPO13 SELECT "user/[EMAIL PROTECTED]".. > > 16:14:25.859297 IP eg01.imap > eg01.55867 : P 478:777(299) ack 588 win > > 256 > > * FLAGS (\Answered \Flagged \Draft \Deleted \Seen).. > > * OK [PERMANENTFLAGS (\Deleted)] .. > > * 0 EXISTS.. > > * 0 RECENT.. > > * OK [UIDVALIDITY 1187010780] .. > > * OK [UIDNEXT 2] .. > > * OK [NOMODSEQ] Sorry, modsequences have not been enabled on this > > mailbox.. > > * OK [URLMECH INTERNAL].. > > ODPO13 OK [READ-WRITE] Completed.. > > 16:14:25.860638 IP eg01.55867 > eg01.imap: P 588:611(23) ack 777 win 299 > > > > ODPO14 UID SEARCH ALL.. > > 16:14:25.860913 IP eg01.imap > eg01.55867: P 777:831(54) ack 611 win 256 > > > > * SEARCH.. > > ODPO14 OK Completed (0 msgs in 0.000 secs).. > > 16:14:25.862171 IP eg01.55867 > eg01.imap : P 611:625(14) ack 831 win > > 299 > > ODPO15 CLOSE.. > > 16:14:25.869642 IP eg01.imap > eg01.55867: F 831:831(0) ack 625 win 256 > > > > 16:14: 25.906271 IP eg01.55867 > eg01.imap: . ack 832 win 299 > > > > 16:14:25.933508 IP eg01.55867 > eg01.imap: P 625:638(13) ack 832 win 299 > > > > ODPO16 NOOP.. > > 16:14:25.933539
Re: cyrus 2.0.3 sieve?
On Wed, 29 Aug 2007, Mike Eggleston wrote: > What can sieve in cyrus 2.0.3 do? I know it can do 'fileinto'. I'm trying > to test 'vacation' and 'imapflags'. Is there some way to see what sieve > can do like a CAPABILITIES line? When I use the sivtest program with Cyrus v2.2.13, I get: cyrus-fe1:~# sivtest -u morgan -a morgan localhost S: "IMPLEMENTATION" "Cyrus timsieved v2.2.13" S: "SASL" "PLAIN" S: "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex" S: "STARTTLS" S: OK It appears to be showing the various modules/capabilities. Andy Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyrus 2.0.3 sieve?
On Wed, 29 Aug 2007, Andrew Morgan might have said: > On Wed, 29 Aug 2007, Mike Eggleston wrote: > > >What can sieve in cyrus 2.0.3 do? I know it can do 'fileinto'. I'm trying > >to test 'vacation' and 'imapflags'. Is there some way to see what sieve > >can do like a CAPABILITIES line? > > When I use the sivtest program with Cyrus v2.2.13, I get: > > cyrus-fe1:~# sivtest -u morgan -a morgan localhost > S: "IMPLEMENTATION" "Cyrus timsieved v2.2.13" > S: "SASL" "PLAIN" > S: "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress > relational comparator-i;ascii-numeric regex" > S: "STARTTLS" > S: OK > > > It appears to be showing the various modules/capabilities. > > Andy Thanks. I thought of the same thing right after I sent the message. Mike Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
sieve and imapflags?
I'm still testing and still trying to get a response from vacation.
I came across that sieve had the functionality for modifying the
imap flags. For junk messages messages tagged as spam I want the
message file and the \\seen and \\deleted flags set. My script is:
-- sieve script
# load the necessary components
# fileinto is for filtering
# vacation is ... well ... just that
require ["fileinto", "vacation", "imapflags"];
# save a copy of inbound messages
fileinto "INBOX.backup";
# main filtering rules
if header :contains "Subject" "testing vacation" {
vacation :days 4 "I'm testing, ok?!";
fileinto "INBOX.howard";
} elsif address :contains ["to","from","cc","bcc"] ["@mac.com","[EMAIL
PROTECTED]"] {
vacation :days 4 "I'm testing, ok?! (2)";
} elsif header :contains "Subject" "*** SPAM ***" {
fileinto "INBOX.spam";
setflag ["\\seen", "\\deleted"];
} elsif header :contains "Subject" "*** VIRUS" {
fileinto "INBOX.spam";
} elsif header :contains "Subject" "/usr/bin/fetchmail" {
fileinto "INBOX.spam";
setflag ["\\seen", "\\deleted"];
} elsif header :contains "Subject" "[ppml]" {
fileinto "INBOX.arin";
setflag "\\seen";
} elsif address :contains ["to","from","cc","bcc"] "[EMAIL PROTECTED]" {
fileinto "INBOX.hobbit";
setflag ["\\seen", "\\deleted"];
} elsif address :contains ["to","from","cc","bcc"] "[EMAIL PROTECTED]" {
fileinto "INBOX.hobbit";
setflag ["\\seen", "\\deleted"];
} elsif address :contains ["to","from","cc","bcc"] "[EMAIL PROTECTED]" {
fileinto "INBOX.hobbit";
setflag ["\\seen", "\\deleted"];
} elsif address :contains ["to","from","cc","bcc"] "Mail Delivery Subsystem" {
fileinto "INBOX.messages";
setflag ["\\seen", "\\deleted"];
} elsif address :contains ["to","from","cc","bcc"] "Courier mail server" {
fileinto "INBOX.messages";
setflag ["\\seen", "\\deleted"];
} elsif header :contains "Subject" "NOTICE: mail delivery status" {
fileinto "INBOX.messages";
setflag ["\\seen", "\\deleted"];
} elsif header :contains "Subject" "Returned mail: see transcript for details" {
fileinto "INBOX.messages";
setflag ["\\seen", "\\deleted"];
} elsif header :contains "Subject" "Postmaster notify: see transcript for
details" {
fileinto "INBOX.messages";
setflag ["\\seen", "\\deleted"];
} else {
fileinto "INBOX";
}
-- sieve script
I'm testing the lines that are 'setflag' or 'addflag'. I've
changed the 'addflag' lines to 'setflag', but neither line
seems to work. I've also tried 'fileinto :flags "\\seen" INBOX.spam',
but this didn't work either.
See anything wrong?
fedora core 5
cyrus imap 2.3.1
Mike
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sieve and imapflags?
On Wed, 29 Aug 2007, Mike Eggleston might have said:
> I'm still testing and still trying to get a response from vacation.
> I came across that sieve had the functionality for modifying the
> imap flags. For junk messages messages tagged as spam I want the
> message file and the \\seen and \\deleted flags set. My script is:
>
> -- sieve script
> # load the necessary components
> # fileinto is for filtering
> # vacation is ... well ... just that
>
> require ["fileinto", "vacation", "imapflags"];
>
> # save a copy of inbound messages
> fileinto "INBOX.backup";
>
> # main filtering rules
> if header :contains "Subject" "testing vacation" {
> vacation :days 4 "I'm testing, ok?!";
> fileinto "INBOX.howard";
> } elsif address :contains ["to","from","cc","bcc"] ["@mac.com","[EMAIL
> PROTECTED]"] {
> vacation :days 4 "I'm testing, ok?! (2)";
> } elsif header :contains "Subject" "*** SPAM ***" {
> fileinto "INBOX.spam";
> setflag ["\\seen", "\\deleted"];
> } elsif header :contains "Subject" "*** VIRUS" {
> fileinto "INBOX.spam";
> } elsif header :contains "Subject" "/usr/bin/fetchmail" {
> fileinto "INBOX.spam";
> setflag ["\\seen", "\\deleted"];
> } elsif header :contains "Subject" "[ppml]" {
> fileinto "INBOX.arin";
> setflag "\\seen";
> } elsif address :contains ["to","from","cc","bcc"] "[EMAIL PROTECTED]" {
> fileinto "INBOX.hobbit";
> setflag ["\\seen", "\\deleted"];
> } elsif address :contains ["to","from","cc","bcc"] "[EMAIL PROTECTED]" {
> fileinto "INBOX.hobbit";
> setflag ["\\seen", "\\deleted"];
> } elsif address :contains ["to","from","cc","bcc"] "[EMAIL PROTECTED]" {
> fileinto "INBOX.hobbit";
> setflag ["\\seen", "\\deleted"];
> } elsif address :contains ["to","from","cc","bcc"] "Mail Delivery Subsystem" {
> fileinto "INBOX.messages";
> setflag ["\\seen", "\\deleted"];
> } elsif address :contains ["to","from","cc","bcc"] "Courier mail server" {
> fileinto "INBOX.messages";
> setflag ["\\seen", "\\deleted"];
> } elsif header :contains "Subject" "NOTICE: mail delivery status" {
> fileinto "INBOX.messages";
> setflag ["\\seen", "\\deleted"];
> } elsif header :contains "Subject" "Returned mail: see transcript for
> details" {
> fileinto "INBOX.messages";
> setflag ["\\seen", "\\deleted"];
> } elsif header :contains "Subject" "Postmaster notify: see transcript for
> details" {
> fileinto "INBOX.messages";
> setflag ["\\seen", "\\deleted"];
> } else {
> fileinto "INBOX";
> }
> -- sieve script
>
> I'm testing the lines that are 'setflag' or 'addflag'. I've
> changed the 'addflag' lines to 'setflag', but neither line
> seems to work. I've also tried 'fileinto :flags "\\seen" INBOX.spam',
> but this didn't work either.
>
> See anything wrong?
>
> fedora core 5
> cyrus imap 2.3.1
>
Well, part of the problem is 'setflag' must come before 'fileinot'. Now
the flags are being set right.
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Mailbox is locked by POP server
I am sorry for re-posting what Igor Belikov posted on this list two years ago (and unanswered) because I got the same problem and the answer isn't really obvious (googling around can lead me some really complex discussion on how to detect and shut down the expired/dead connection but not direct answer) here is the question: Hello info-cyrus, We have clients that get his (or her) mail via dial-up connections. If dial-up session terminates abnormally (while getting mail) and client redial and try to continue get his mail - he receive error: Mailbox is locked by POP server I understand what is the problem: Cyrus don't see ending previous POP session and think that client still using mailbox, and don't allow him begin new session. Is it possible to turn this behavior off? We have enough dial-up clients, and nobody of them using IMAP - only POP3. I know that POP3 do not allow concurrent connection, as written clearly in RFC. Problem being our customer use really damn stupid email client that looks occasionally dropping connection without notifying server, and other email service providers here in China seems to handle this particular email client pretty well. The email client also doesn't support any of TLS, IMAP or LDAP and is very popular here (popular for non-technical reason of course) that if we don't support it, customers prefer to choose another email service provider who can. "I am used to use xxx product" is such a strong reasoning from customer that service providers cannot simply ignore and suggest Thunderbird & IMAP (I already suggested many times). Best regards Zhang Weiwu Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
