Meaning of Discarding messages from sync_client?

Could anyone explain the meaning of lines like: Mar 26 00:49:50 util6 sync_client[31645]: Discarding: 3082 () I have literally millions of these in my maillog (occasionally with flags between the parentheses and rarely other text in place of the zeroes) and am wondering

Re: Meaning of Discarding messages from sync_client?

WC == Wesley Craig w...@umich.edu writes: WC This is the client trying to re-sync the protocol with the WC server. There should be a line preceding the Discarding: messages WC with containing the word invalid or illegal, which is the actual WC problem. Indeed: Mar 25 23:17:36 util6

Not possible to replicate from 2.3.7 to 2.3.16?

I'm trying to move my mail services to both new hardware and a new Cyrus version. This involves a change in architecture from i386 to x86_64. I was going for what looked like the simplest method: set the new server as a replica, let everything replicate, then quickly shut things down, configure

Re: Not possible to replicate from 2.3.7 to 2.3.16?

[Forgot to send this to the list; sorry. BG == Bron Gondwana br...@fastmail.fm writes: BG No, sorry. I figured as much; I backed off to 2.3.7 on the new machine so that I could get a good replica. BG Replication across versions is trick at the best of times, and BG you're talking about

Re: Not possible to replicate from 2.3.7 to 2.3.16?

BG == Bron Gondwana br...@fastmail.fm writes: BG The advantage of reconstructing (if you choose that BG path instead, heaps more IO use though) is that you'll get real SHA1 BG GUIDs rather than padded GUIDs. Not a huge deal - though I'll BG probably force the SHA1 calculation in the 2.4

FYI: if startup is too fast, IDLE fails

Thought I'd mention an odd problem with idled which I've worked around so that it gets into the list archive. Running 2.3.16, the master starts idled without error. However, all of the services initially started by master would fail to contact idled and give the following error: imap[23494]:

Re: Berkeley DB: private copy?

Just so you know, the policies of most Linux distributions forbid this kind of bundling, so unless it's easily disabled (and preferably defaults to using system libraries) the distributions will just have to patch it back out again. For example, here's the Fedora policy:

Long term offline mail retention

I manage email (and practically everything else) for a medium sized university department. Recently I've been informed that we're adopting a three-year retention policy for email. We're allowed to keep things for longer than that, so I'm not looking at forced expiration (which is all I found

Re: Deleting unused or dormant mail accounts.

BG == Bron Gondwana br...@fastmail.fm writes: BG yes, it should work with 2.4. Good news. Since folks may not know much about this, here's some detail. I've been using this little Perl script to talk to the fud server for so long that I've no recollection of where it came from. It's only 53

Code for manipulating all messages matching some criteria?

Recently our campus was hit with a particularly bad targeted trojan attach and the IT overlords sent out a demand that we (a small department with several hundred mailboxes on our own server) go through all user mailboxes and actually delete the offending messages. At least using the admin

Ban some users from accessing IMAP

I have a pretty simple cyrus setup; I have a long-running 2.3.16 install on RHEL5 (one day I'll update), with authentication handled by cyrus-sasl 2.1.22 and everything authenticating to a kerberos server. What I would like to do is ban some valid users from accessing IMAP. We've had a rash of

Re: Ban some users from accessing IMAP

DM == Dave McMurtrie dav...@andrew.cmu.edu writes: DM The good news is that user_deny.db does exactly what you want. It DM allows you to deny any specific service to a valid user, even if DM they can successfully authenticate to your Cyrus server. Oh, that's what that does. I see one mention

Re: Communicating kerberos password expiration

Thanks for your response! DW == Dan White dwh...@olp.net writes: DW I haven't found it common for IMAP clients to display Quota alerts, DW but I haven't extensively tested. Squirrel mail, and perhaps Horde, DW will display Quota Alerts, so it's possible that it would display DW any alert

Re: Communicating kerberos password expiration

DW == Dan White dwh...@olp.net writes: DW There is an annotation (/comment) which you can set per mailbox, DW which should result in an alert being displayed: Checking that again, I'm not sure that's the case. There's a misformatting in the FAQ entry which squishes the text for /motd into the

Communicating kerberos password expiration

I know this isn't entirely a Cyrus question, but I figure some folks here would have some idea of my issue. Basically, we use Kerberos authentication with Cyrus. The passwords in Kerberos expire. With shell and (Linux) desktop logins and such, the system alerts users and if necessary forces

Re: Cyrus IMAP 3.0.0-beta1 released

SM == Simon Matter simon.mat...@invoca.ch writes: SM As I'm currently working on a 2.5.x release of our Invoca RPMs I'm SM wondering if it would make sense to just go with 3.0 beta? The work SM on 2.5.x will still take some more time because it's a big change SM with the new build system, new

Re: berkdb in configure.ac

EA == Eray Aslan er...@a21an.org writes: EA The berkdb macros in cmulocal/berkdb.m4 tries to find the installed EA berkeley include files and libraries but they are just too painful EA and error prone. I had reports of imapd crashes because of EA include/lib mismatches. Fedora has carried a

Re: Can't find icu-uc to build IMAP 3.0.0

> "RLM" == Rosenbaum, Larry M writes: RLM> I am trying to build Cyrus-IMAP 3.0.0 on RHEL6. That's pretty old these days EL6 has a version of libicu that doesn't include any of the icu-* pkgconfig files. It does contain libicuuc, though. You just need to tell the

Re: Update from cyrus-imapd 2.5 to 3.0

> "JLT" == Jason L Tibbitts writes: JLT> Maybe it would be better if you could provide more explicit JLT> information in some way. Like, a directory listing or something. To update the list, the issue was that the admins: line contained a regular user ID. When that user

Re: any working cyrus-imapd-3.0.2?

> "SL" == Stephan Lauffer writes: SL> ...ok found working fedora 26 packages... Yes, I have updated packages in Fedora 26, but if you have any specific questions about how I've built things please let me know. The spec file is relatively well commented:

Re: Update from cyrus-imapd 2.5 to 3.0

> "DH" == David Hill writes: DH> Also, if a folder is created, it is created in DH> /var/spool/imap/[first_letter_of_folder]/Junk instead of DH> /var/spool/imap/d/user/dhill/Junk ... In your bug you indicated that things were being stored under /var/spool/[first letter]/

Re: Fedora26. Cyrus- 3.0.3. cyr_virusscan None Configured.

> "AS" == Anton Shilov via Info-cyrus > writes: AS> I think it is missconfig because ClamAV isn't part of cyrus-imap AS> packet. The Fedora package is not configured to use clmav. This is because clamav in Fedora still uses the old openssl libraries

Re: update to 3.0.3 even more problematic than 3.0.2

> "BG" == Bron Gondwana writes: BG> https://github.com/cyrusimap/cyrus-imapd/issues/2132 BG> We're pretty sure we've found the cause. Do you plan to cut a 3.0.4 release or should I plan on pushing this patch into my distro packages? - J< Cyrus Home Page:

Re: Backup methods

Cyrus does have an integrated backup system (see https://cyrusimap.org/imap/reference/admin/backups.html) which I'm not sure has been mentioned in this thread. But you still have to have enough space to keep the compressed backups on disk in order to move them to tape or whatever archival storage

Re: Backup methods

> "A" == Anatoli writes: A> What about mysqldump > dump.sql, then mysql < dump.sql? Also a wrong A> way and didn't have to be implemented? No, that's exactly my point. Thanks for making it for me! The analog to the way you indicated that you would like it to work would

Re: Backup methods

> "A" == Anatoli writes: A> What you mention is highly related to the replication backup A> we were talking about in the previous mails. Well, sort of. It is a method that is actually focused around doing backups. It happens to make use of the replication protocol

Re: System I/O error (in reply to end of DATA command) for LMTP delivery

If you suspect selinux, please do 'ausearch -m avc -ts today' and see what you get. You may also wish to do 'setenforce 0' and try again, just to make sure. I can provide some basic help with selinux if that's needed. - J< Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info:

Re: System I/O error (in reply to end of DATA command) for LMTP delivery

> "SI" == Stephen Ingram writes: SI> I did turn it off just to see what happened, but it was not SI> the problem. Nice though, because I learned how to relabel a volume SI> to get back in the good graces of SELinux. Well, just using setenforce doesn't disable selinux; it just disables

Re: Solaris Compiling 3.0.5 with libical3.0

> "JD" == Jean-Christophe Delaye writes: JD> Is Libical 3.0.0 supported with 3.0.5 ? Any idea ? It is not, but you can apply https://github.com/cyrusimap/cyrus-imapd/commit/1966c22fc4249a1157a4d4c1224138ce78653514 At least that's what I do in Fedora. -

Re: Failure making cyrus-imapd-3.0.5 on CentOS 7

> "DJW" == David J Weller-Fahy writes: DJW> Greetings again, I've made it a bit further in my attempt to DJW> install cyrus-imapd, but am getting failures when executing `make`. DJW> The failure is shown below. You should look at what the Fedora specfile does

Re: segfaults with cyrus-imapd 3.0.9 on latest arch linux

> "AP" == Andreas Piesk writes: AP> Hello list, i'm trying to get cyrus-imapd 3.0.9 (testet 3.0.8 too) AP> running on latest arch linux. Here's the configure summary: AP> External dependencies: ldap: no openssl: yes zlib: yes pcre: yes AP> #6 0x7fc4aa385050 re_acquire_state_context

Re: Cyrus IMAP in the next Debian

> "PV" == Paul van der Vlis writes: PV> Somebody has packaged Cyrus version 3.08, but there are problems PV> with some of the Cassandane tests. It may be useful to see how Fedora handles Cassandane as part of its build process. I did a lot of work to get things functioning and get patches

Re: [cyrus 3.0] 20 delayed mailbox deleted limit?

> "BG" == Bron Gondwana via Info-cyrus > writes: BG> How would you suggest we protect against exploiting delayed delete BG> to fill the server without going over quota? Well, I don't even run quotas. But I do keep deleted messages around for 12 weeks,

Re: [cyrus 3.0] 20 delayed mailbox deleted limit?

> "BG" == Bron Gondwana writes: BG> Just to be really clear what this is. It's per mailbox name - if BG> you create and delete the SAME mailbox more 20 times, it only keeps BG> the most recent 20 of that mailbox. Hmm. That's much less problematic, but it still allows

Re: LDAP backed aliases

> "TG" == Tony Galecki via Info-cyrus > writes: TG> I’ve done a quick search and haven’t come across anything yet. Is TG> there a way to manage or pull alias information via LDAP? It could TG> be that my google fu is weaker than yours. Well, I have my

Re: imap impersonate

> "PG" == Patrick Goetz via Info-cyrus > writes: PG> Why would you need to do this as opposed to, say, just setting up PG> multiple personalities on your MUA? I used impersonation to initially import mailboxes into Cyrus way back when I switched from

Re: watching and processing a Spam folder for each user

> "PB" == Patrick Boutilier via Info-cyrus > writes: PB> Only problem with that is users always seem to report some stuff as PB> spam when it clearly isn't. :-) True, but at least it's only a statistical thing. You could easily extract the From:

Re: watching and processing a Spam folder for each user

> "BJM" == Brian J Murrell via Info-cyrus > writes: BJM> So leaving out the latter part (the per-user database and handling, BJM> etc.) I wonder what, if anything exists to monitor the Spam (and BJM> NotSpam) folders for all users. I have a system which

Re: how to deal with mail retention/archival.

> "GR(" == Giuseppe Ravasio (LU) via Info-cyrus > writes: GR(> I saw that someone proposed to make a sort of abuse of delayed GR(> expunge, but I think that in order to comply with regulatory GR(> retention should be better considering some specific

Re: Did calculating the quota change from 2.3 to 2.5?

> "BG" == Bron Gondwana via Info-cyrus > writes: BG> If you use imapsync, it doesn't know about that, and will upload the BG> same message twice. 2.5 doesn't have the smarts to recognise that BG> it's the same message. Fun random question: Does anything

Re: fetching spam from users junk folder

> "MS" == Marcus Schopen via Info-cyrus > writes: MS> Hi, I'm looking for an easy way to fetch spams, which were moved MS> into a special junk subfolder by users in their accounts. I'd like MS> to move those messages from there to my account, so I can

Re: "Resource temporarily unavailable", systemd and your FAQ Webpage

> "NB" == Nic Bernstein via Info-cyrus > writes: NB> I'm curious which Linux distribution NB> you're using? For the record, Fedora's systemd has task accounting enabled (and I've added some information to the unit file about it). I'm not sure about