> "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 uw-imapd. I guess it might also be
> "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
RHEL7 as its systemd/system.conf file
> "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 analyse
MS> them to adjust anti spam
> "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 blow up if you run hardlink on yo
> "MU" == Michael Ulitskiy via Info-cyrus
> writes:
MU> My question is: assuming cost is not an issue, would it be advisable
MU> to put an entire cyrus mail spool on SSD? I'm thinking about
MU> combinining multiple SSDs into RAID10 to further increase
MU> performance.
I don't see why n
> "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: headers and blacklist them, but that wou
> "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 sucks things out of everyone's "c
> "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 software.
True, but it seems odd (to
> "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 someone to force
somet
> "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, and even if I didn't, I do delete
> "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 aliases in LDAP and have for years,
11 matches
Mail list logo