search for: 33056

Hi, Why did my 'doveadm expunge' command not clear the Trash out of a mailbox? The oldest messages was put into the Trash on the 26th June 2018 as shown in the file timestamp. -rw------- 1 vmail mail 33056 Jun 26 16:46 1530031582.M768773P18242.mx10,S=33056,W=33510:2,RS # doveadm -D expunge -u testuser at example.org mailbox Trash savedbefore 2d Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot...

...Wed, 18 Jul 2018, Sophie Loewenthal wrote: > >> Why did my 'doveadm expunge' command not clear the Trash out of a mailbox? >> >> The oldest messages was put into the Trash on the 26th June 2018 as shown in the file timestamp. >> >> -rw------- 1 vmail mail 33056 Jun 26 16:46 1530031582.M768773P18242.mx10,S=33056,W=33510:2,RS >> >> # doveadm -D expunge -u testuser at example.org mailbox Trash savedbefore 2d > > I was going to suggest that you dump the savedbefore dates on all your > messages to see what Dovecot thinks your message'...

On Wed, 18 Jul 2018, Sophie Loewenthal wrote: > Why did my 'doveadm expunge' command not clear the Trash out of a mailbox? > > The oldest messages was put into the Trash on the 26th June 2018 as shown in the file timestamp. > > -rw------- 1 vmail mail 33056 Jun 26 16:46 1530031582.M768773P18242.mx10,S=33056,W=33510:2,RS > > # doveadm -D expunge -u testuser at example.org mailbox Trash savedbefore 2d I was going to suggest that you dump the savedbefore dates on all your messages to see what Dovecot thinks your message's timestamps are. I tri...

...; preds = %L_00000000_ call void @reach() %3 = load %struct.ThreadContext** %2, align 4 call void @reach() %4 = getelementptr inbounds %struct.ThreadContext* %3, i32 0, i32 1 call void @reach() %5 = getelementptr inbounds [32 x i32]* %4, i32 0, i32 2 call void @reach() * store i32 33056, i32* %5* call void @reach() br label %L_00008120_1 ..... -------------------------------------------------------------------------------------------------- Somehow, the storeInst is not successfully performed, it gets segmentation fault, I wonder if I miss something important. I pinpo...

...ach() > %3 = load %struct.ThreadContext** %2, align 4 > call void @reach() > %4 = getelementptr inbounds %struct.ThreadContext* %3, i32 0, i32 1 > call void @reach() > %5 = getelementptr inbounds [32 x i32]* %4, i32 0, i32 2 > call void @reach() > * store i32 33056, i32* %5* > call void @reach() > br label %L_00008120_1 > > > ..... > > -------------------------------------------------------------------------------------------------- > > > Somehow, the storeInst is not successfully performed, it gets > > segmentation f...

Hi, About a week ago I upgraded our reasonably heavily loaded mail servers from a pretty recent courier version to dovecot-1.1rc10. IMAP performance on dovecot is amazing, however POP3 performance is worse than courier :-( I have uploaded some munin graphs taken today to http://linweb.atlas.pipex.net/dovecot/; the dovecot server is handling about 2000 pop logins/sec and 300 imap sessions (but

Hi, I am not sure to report this as a bug. so mailing to the list. I have sshd(openssh3.5p1) server running on my router and when i run tcpjunk to that port, sshd gets killed after some time 192.168.71.1 is my sshd server and 192.168.71.4 is my client from where i send my dos attack This is the tcpjunk command i gave to the ssh server #tcpjunk -s 192.168.71.1 -p 22 -c req -i 100 req session

I regret the delay in replying to this topic but I am a digest subscriber so I only see list traffic once every 24 hours. When I moved from RHES3 to CentOS4 back in April/May of this year I was bitten by the SELinux gnat as well, and the temptation to swat a distracting irritation by killing it in its bed nearly proved irresistible. However, taking to heart the advice given to me here and

...bb.bbb.bbb my firewall''s internal ip is 192.168.0.254 i did snat: iptables -t nat -A POSTROUTING -o ppp0 -j SNAT --to aaa.aaa.aaa iptables -t nat -L -v gives: Chain POSTROUTING (policy ACCEPT 23663 packets, 2182K bytes) pkts bytes target prot opt in out source destination 33056 2084K SNAT all -- any ppp0 anywhere anywhere to:aaa.aaa.aaa.aaa but tcpdump both on ppp0 and on remote bbb.bbb.bbb.bbb gives: 10:35:27.564611 IP 192.168.0.254.5070 > bbb.bbb.bbb.bbb.5060: UDP, length 489 so snat is not working any idea ?