similar to: upgrade 1.0.15 -> 2.1.7: MBOX index compatibility and performance

Displaying 20 results from an estimated 4000 matches similar to: "upgrade 1.0.15 -> 2.1.7: MBOX index compatibility and performance"

2023 Mar 21
1
"doveadm altmove -r" not working ?
> On 21/03/2023 00:26 EET Benoit Branciard <benoit.branciard at univ-paris1.fr> wrote: > > > Hello, > > I have some trouble using "doveadm altmove -r". > > Regular "doveadm altmove" is OK, selected mails were moved to alternate > storage as expected. But I can't manage to get them back to original > location, "doveadm altmove
2012 Jun 22
1
cumulative userdb ?
in Dovecot 2.0, is it possible to have kind of "cumulative" multiple userdb ? that is, for all users: - extract some attributes (let's say: uid, gid, home) from a first userdb (Passwd for example), - an extract some other attributes (mail for example, but overwriting those from the first userdb in case of redundancy) from a second userdb (LDAP for example) ? This is *different*
2023 Mar 21
1
"doveadm altmove -r" not working ?
Hi, Your problem might be similar to mine a long time ago. IMO behavior of "doveadm altmove -r" command with mdbox format is different to sdbox format: - With sdbox format, when you move back a message to primary storage (aka default storage), only the message and the file containing it are affected. There is nothing impacted. - With mdbox format, a file in storage contains
2017 Jan 05
1
doveadm output format changes
It appears that doveadm output format changes every now and then, without particular notice. For example, the following command: doveadm -f pager mailbox status 'messages recent' '*' did output something like this until v2.2.24 : mailbox: Mailbox1 messages: 58 recent: 12 ^L mailbox: Mailbox2 messages: 128 recent: 0 but switched to that in v2.2.26 : Mailbox1 messages: 58
2023 Mar 20
3
"doveadm altmove -r" not working ?
Hello, I have some trouble using "doveadm altmove -r". Regular "doveadm altmove" is OK, selected mails were moved to alternate storage as expected. But I can't manage to get them back to original location, "doveadm altmove -r" has no effect. We are using Dovecot 2.3.4 (Debian Buster package). mail_location =
2017 Jan 25
1
2.2.26.0 : accessing "mdbox_deleted" content destroys indexes
Accessing or listing "mdbox_deleted" contents seems to destroy MDBOX indexes. Examples of commands which triggers this problem ($home being the home directory of $user, and mail_location being mdbox:~/mdbox): doveadm -o mail="mdbox_deleted:$home/mdbox" -f table mailbox status -u "$user" 'messages vsize' INBOX doveadm -v import -s -u "$user"
2006 Dec 13
2
Authorization client connect failing
Hello, and thank you in advance for your valuable time. I am running Dovecot v1.0.rc15 on an OpenBSD 3.9 i386 machine (no time to upgrade yet). I downloaded the source from the dovecot site, compiled and installed without any problem. The server starts up find and runs for a while. After a few hours to a few days, the server stops sending the CAPABILITY statement when a client tries to
2007 Mar 28
2
assertion failed (1.0-rc27)
Under Dovecot 1.0-rc27 on Solaris 10 we noticed this error today affecting one of our users repeatedly: Mar 28 14:02:01 myhost dovecot: IMAP(myuser): file mbox-sync-rewrite.c: line 423 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 28 14:02:01 myhost dovecot: IMAP(myuser): Raw backtrace: 0x7ac54 -> 0x42cd4 -> 0x3e968 -> 0x3f54c -> 0x3f980
2014 Apr 16
1
Connecting 2 asterisks, one with PJSIP and other SIP returning 401
It's my first post here, so I'll cut to the chase I have 2 Asterisk servers and want to connect them using sip on one and pjsip on the other one. One is running at home and another at a VPS. The first one will be the client (with dynamic ip) and the 2nd the server. The client uses sip and the server pjsip. This is the client's sip.conf [general] context = default allowguest = no
2008 Aug 21
3
dovecot panic after upgrade 1.0.15 to 1.1.2
I recently upgraded dovecot from 1.0.15 to 1.1.2 and since then I am getting the following types of things in the logs: Aug 21 17:23:13 mail1 dovecot: imap-login: Login: user=<myuser>, method=PLAIN, rip=172.16.78.20, lip=172.16.78.22 Aug 21 17:24:01 mail1 dovecot: Panic: IMAP(myuser): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed:
2020 Nov 11
1
run firefox via an ssh tunnel
I can ssh -X myuser at theremote-mac but I cannot run /usr/bin/firefox. I can run "open -a Firefox" on the mac but then it just opens firefox on the mac Thoughts? On 11/11/20 3:45 PM, R C wrote: > I do it all the time. > > > make sure you forward X11,? on the? ssh server side,? and login with? > ssh -X me at myhost.whatever > > start firefox with: > >
2004 Jun 11
4
Bug#253861: logcheck: Please add support for imapproxy
Package: logcheck Version: 1.2.22a Severity: wishlist There is no support for imapproxy, and it would be a great help if it was added. Following are two sample lines from the syslog: Jun 11 09:36:55 MyHost in.imapproxyd[30845]: LOGOUT: '"MyUser"' from server sd [13] Jun 11 09:37:02 MyHost in.imapproxyd[30846]: LOGIN: '"MyUser"' (xxx.xxx.xxx.xx:yyyyy) on
2015 Nov 03
0
R-SIG-Debian Digest, Vol 123, Issue 1
Michael, rjags has updated. Thank you. BTW, I don't really know why I addressed the email to Dirk... Sebastien. Le 03/11/2015 12:00, r-sig-debian-request at r-project.org a ?crit : > Send R-SIG-Debian mailing list submissions to > r-sig-debian at r-project.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://stat.ethz.ch/mailman/listinfo/r-sig-debian
2015 Nov 02
3
R-packages for Ubuntu 15.10 wily
Dear Dirk, I just upgraded to Ubuntu 15.10. It seems that the r-packages are not upgrading although deb files exist on the cran repository. For instance, r-cran-rjags is back to 3-15-1 On the repository, I saw that the 'Sources' and 'Packages' files in wily folder show vivid version of packages although dated to yesterday : https://cran.univ-paris1.fr/bin/linux/ubuntu/wily/Sources
2009 Aug 21
0
R installation problem with shared libraries (PR#13900)
Full_Name: Uwe F. Mayer Version: 2.9.1 OS: SunOS myhost 5.10 Generic_120012-14 i86pc i386 i86pc Solaris Submission from: (NULL) (216.113.168.130) Configuration problem with the creation of shared libraries: Compilation only succeeds if SHLIB_LDFLAGS="-shared" is added to the configure command line. This is likely due to a wellknown gcc-4 feature, in that gcc requires -shared and not
2015 Oct 31
3
use pssh to restart a service
> > What does the sudo log say? This is all the secure logs say about the ssh session: [root at logs:~] #tail -f /var/log/secure Oct 31 19:15:20 logs sshd[24407]: Accepted publickey for bluethundr from 47.18.111.100 port 47469 ssh2: RSA ae:62:1f:de:54:89:af:2c:10:16:0e:fd:8d:7e:81:06 Oct 31 19:15:21 logs sshd[24407]: pam_unix(sshd:session): session opened for user bluethundr by (uid=0)
2006 Oct 27
0
RMySQL and stored procedures
Hi, I use RMySQL to connect to MySQL server where I have a couple of stored procedures. I know that the function for the stored procedures "is not yet implemented", but I was trying to get around the problem connecting like that: drv <- dbDriver("MySQL") con <- dbConnect(drv,user=MyUser, password=MyPasswd, dbname=MyDBName, host=MyHost, client.flag="196608"
2018 Aug 21
5
selinux question
I have a web application which uses sudo to invoke python scripts as the user under which the application runs (NO root access).? Is there any reason why sudo would would require sys_ptrace access for this?? I only get this violation intermittenly, and not with every call to sudo.? Here's the violation: Summary: SELinux is preventing sudo (httpd_t) "sys_ptrace" to <Unknown>
2009 Mar 01
8
puppet and LDAP users
I am trying to get puppet to manage my LDAP users but I don''t appear to be having much success. What I have in puppet.conf is this [puppetmasterd] ldapserver=ldap.myorg.company.com ldapbase=dc=myorg,dc=org ldapuser=cn=admin,dc=myorg,dc=org ldappassword=mysecret ldapparentattr=dc=myorg,dc=org I added the ldapparentattr in desperation and doubt if
2012 Jul 20
1
mdbox with separate index location results in many emptydirectories
Hallo, I use dovecot 2.1.7 with mdbox format and I specified a separate location for mailbox index files with mail_location = mdbox:/dovecot/storage%h:INDEX=/dovecot/index%h With this setting I get for every mailbox a directory under both filesystems /dovecot/index and /dovecot/storage, e.g. for the inbox it looks like that: # ls -lR /dovecot/index/home/hrz/myuser/mailboxes/INBOX