search for: recent

...I''m getting errors while live migrating a pv guest. I''m running Xen 3.4.3 on CentOS 5.5, DRBD 8.3.8.1 and OCFS2 1.4.7-1. The two servers are identical. After live migrating the Debian lenny PV guest(2.6.26-2-686-bigmem), it crashes, It prints this on console [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.6893...

...ot; > > a0020 IDLE > > > > then wait a second.. then paste the following 3 in a go: > > DONE > > a0030 UID STORE 1:3 +FLAGS (\Deleted) > > a0040 EXPUNGE > > > > Notice that the results from UID STORE + EXPUNGE gives: > > * 2 FETCH (UID 2 FLAGS (\Recent)) > > * 3 FETCH (UID 3 FLAGS (\Recent)) > > * 1 EXPUNGE > > * 3 RECENT > > a0030 OK Store completed (0.004 + 0.000 + 0.003 secs). > > a0040 OK Expunge completed (0.004 + 0.000 + 0.003 secs). > > > > > > Verify what's left in the mailbox with: >...

...sing it with the existing MBOX folders. My configuration is pretty much the default one, in particular I didn't touch to any of mbox_xxx options. The (hoped for) performance improvements were indeed quite noticeable and mostly it works just fine but I seem to have one strange problem with the recent messages: Dovecot seems to reset the RECENT flag on the message right *before* the mailbox is opened. So even if a message was just copied to a folder (e.g. by email client filtering), it doesn't have RECENT flag when the mailbox is opened. Here is an example of what I see: % telnet localhost...

...go: a0000 LOGIN "MY-USER" "MY-PASSWORD" a0010 SELECT "error1" a0020 IDLE then wait a second.. then paste the following 3 in a go: DONE a0030 UID STORE 1:3 +FLAGS (\Deleted) a0040 EXPUNGE Notice that the results from UID STORE + EXPUNGE gives: * 2 FETCH (UID 2 FLAGS (\Recent)) * 3 FETCH (UID 3 FLAGS (\Recent)) * 1 EXPUNGE * 3 RECENT a0030 OK Store completed (0.004 + 0.000 + 0.003 secs). a0040 OK Expunge completed (0.004 + 0.000 + 0.003 secs). Verify what's left in the mailbox with: a0050 UID FETCH 1:4 FLAGS * 1 FETCH (UID 2 FLAGS (\Recent)) * 2 FETCH (UID 3 FLAGS...

...SWORD" > a0010 SELECT "error1" > a0020 IDLE > > then wait a second.. then paste the following 3 in a go: > DONE > a0030 UID STORE 1:3 +FLAGS (\Deleted) > a0040 EXPUNGE > > Notice that the results from UID STORE + EXPUNGE gives: > * 2 FETCH (UID 2 FLAGS (\Recent)) > * 3 FETCH (UID 3 FLAGS (\Recent)) > * 1 EXPUNGE > * 3 RECENT > a0030 OK Store completed (0.004 + 0.000 + 0.003 secs). > a0040 OK Expunge completed (0.004 + 0.000 + 0.003 secs). > > > Verify what's left in the mailbox with: > a0050 UID FETCH 1:4 FLAGS > * 1 FETC...

Hello, we are using dovecot 2.0.13 with maildir++ (we migrated away from courrier just a few months ago) and the RECENT status doesn't seem to be working: . STATUS INBOX (MESSAGES UNSEEN RECENT) * STATUS "INBOX" (MESSAGES 35106 RECENT 0 UNSEEN 10) then 2 minutes later: . STATUS INBOX (MESSAGES UNSEEN RECENT) * STATUS "INBOX" (MESSAGES 35106 RECENT 0 UNSEEN 11) How can the UNSEEN count ch...

Is there any way to preserve \Recent, or am I out of luck? Some people have reported that my script which shuffles around expired or oversized mail also causes their clients to report it as already read. I guess those clients check \Recent instead of \Seen when they download. I wish I knew which clients. With Mail::IMAPClient I tr...

...ts wrong (zero) values for that new message. Afterward, it reports the information OK. This causes problems to our IMAP client. The problem is easily reproduced with a large message on a slow machine. I'm using dovecot 1.0.10 Here's a sample trace: 1 uid fetch 1:* fast * 1 FETCH (FLAGS (\Recent) INTERNALDATE "06-Mar-2008 17:20:50 +0200" RFC822.SIZE 3378380 UID 1) * 2 FETCH (FLAGS (\Recent) INTERNALDATE "06-Mar-2008 17:21:40 +0200" RFC822.SIZE 3378380 UID 2) * 3 FETCH (FLAGS (\Recent) INTERNALDATE "06-Mar-2008 17:23:38 +0200" RFC822.SIZE 3378380 UID 3) * 4 FET...

Op 2/22/2017 om 8:40 PM schreef Thomas Leuxner: > * Thomas Leuxner <tlx at leuxner.net> 2017.02.20 12:56: > >> Feb 20 07:00:23 nihlus dovecot: master: Dovecot v2.2.devel (8f42a89) starting up for imap, lmtp >> >> This one processed the dovecot-news mail for 2.2.28.rc1 fine which uses a similar sieve rule. I will monitor global rules with this build and report back.

...< * OK Dovecot ready. >> 1 LOGIN sandbox password ]] 1 OK Logged in. >> 2 SELECT INBOX >> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) >> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. >> * 100 EXISTS >> * 100 RECENT >> * OK [UNSEEN 1] First unseen. >> * OK [UIDVALIDITY 1228090943] UIDs valid >> * OK [UIDNEXT 101] Predicted next UID ]] 2 OK [READ-WRITE] Select completed. >> 3 UID STORE 1 +FLAGS (Flag1) >> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft Flag1) >> * OK...

Hello, I''ve been using shorewall ever since Mandrake started shipping it, and am passably familiar with the config files and the simple setups. Recently I''ve discovered the "recent" module (no pun intended!) and want to setup a few rules that use this module. I searched all through the shorewall site (including http://www.google.com/search?q=site%3Alists.shorewall.net%20custom ) and cant figure out how to add a set of rule...

...79L, 76L, 60L, 82L, 91L)), .Names = c("prochi", "date_1st_event", "bp_date", "SBP", "DBP"), row.names = 108:117, class = "data.frame") It consists of repeated measures for the same individual. What I want to do is find the two most recent blood pressure readings (SBP and DBP) using date_1st_event and bp_date. What I would do to find the most recent date is to subtract date_1st_event-bp_date and then aggregate by min. I'm not sure how to find the two most recent dates. Are there some functions that can help me or will I have...

I can''t get my view to display the most recent parameters from an associated object in a view... here is a birds-eye of my app: I have two models, Ferms and Kinetics. Ferm has_many :kinetics, Kinetic belongs_to :ferm. Kinetic has the fields ferm_id, brix and temp. In my ferms/index view I have a table listing the attributes of each ferm insta...

...rash, spam etc., by deleting Seen messages older than X days. In order to protect against the edge case of a user reading a message right before the deletion task however I?d like to do something like the following: doveadm expunge -A OLD SEEN BEFORE 7d MAILBOX Trash doveadm flags -A remove '\Recent' SEEN BEFORE 7d MAILBOX Trash (except I?m actually doing this per-user with a script and per-user settings for flexibility, but you get the idea) Basically the expunge step only deletes messages without the Recent flag (and which haven?t been marked as unseen again). It then removes this flag...

...han> 1D/3FPsfs1ge/QAASZWA2w Saved Evaluating the results shows that there is still no problem here, since the last delivery is fine (I initially forgot to enable Sieve for LMTP): stephan at drieka:~$ doveadm -f table fetch "uid flags" mailbox "INBOX" uid flags 14 \Flagged \Recent $MailFlagBit1 15 \Flagged \Recent $MailFlagBit1 16 \Flagged \Recent $MailFlagBit1 17 \Flagged \Recent $MailFlagBit1 18 \Flagged \Recent $MailFlagBit1 19 \Recent 20 \Flagged \Recent $MailFlagBit1 stephan at drieka:~$ doveadm -f table fetch "uid flags" mailbox ":public/Newsletter...

Helo, we use recent to control ip traffic. kernel 2.6.18-308.13.1.el5 : all is OK kernel 2.6.18-308.16.1.el5 : the first recent statement causes an error. E.g.: iptables -A INPUT -m state --state NEW -m recent --set -p tcp --dport 80 iptables: Unknown error 18446744073709551615 The man pages say: recent is supported....

Good afternoon I would like to ask if is possible somehow give more relevance to the recent documents in search results. I dont want to sort results according to the date, I still prefer relevance, but I would like to see recent documents with better scoring. I was trying to add search query using AND_MAYBE, which should use relevance from both subqueries, but it didnt add any benefit to...

Hello, up to CentOS 5.3 it was possible, to control new ip connections by "recent", "seconds" and "hitcount" -A INPUT -m state --state NEW -m recent --set -p tcp --dport 80 -A INPUT -m state --state NEW -m recent --update --seconds 60 --hitcount 1000 -p tcp --dport 80 -j LOG --log-prefix "FW DROP IP Flood: " -A INPUT -p tcp -m tcp --dport 80...

Hello, all. I read this document about iptables recent module. http://blog.andrew.net.au/2005/02/16#ipt_recent_and_ssh_attacks and I would like to filter the excessive spam mail sending ip address by iptables recent module. and some questions. iptables -A INPUT -p tcp --dport 25 -m state --state NEW -m recent --set --name SPAM iptables -A INPUT -p...

I was wondering if anyone had implemented rules like this in shorewall: http://blog.andrew.net.au/tech I see tons of brute force attempts on the machines I administer, and I like the idea of limiting them without the need for extra daemons scanning for attacks. Thanks, Dale -- Dale E. Martin - dale@the-martins.org http://the-martins.org/~dmartin