Re: What happened to normalizeuid?

2017-01-20 Thread Sebastian Hagedorn via Info-cyrus
--On 20. Januar 2017 um 07:34:20 -0600 Nic Bernstein wrote: The "normalize" patch included by Debian isn't that far off from what the option "usercase_tolower" already offers: username_tolower (*on*|off) Convert usernames to all lowercase before

Re: What happened to normalizeuid?

2017-01-20 Thread Sebastian Hagedorn via Info-cyrus
--On 20. Januar 2017 um 08:04:25 +1100 Bron Gondwana via Info-cyrus <info-cyrus@lists.andrew.cmu.edu> wrote: On Fri, 20 Jan 2017, at 03:31, Sebastian Hagedorn via Info-cyrus wrote: --On 19. Januar 2017 um 17:18:06 +0100 Simon Matter <simon.mat...@invoca.ch> wrote: > We

Re: What happened to normalizeuid?

2017-01-19 Thread Sebastian Hagedorn via Info-cyrus
--On 19. Januar 2017 um 17:18:06 +0100 Simon Matter wrote: We and others had this as a patch in our RPMs but I think it has never been part of vanilla cyrus-imapd. Oops. Should I open an issue for a feature request? I'm surprised that's not something many sites want

What happened to normalizeuid?

2017-01-19 Thread Sebastian Hagedorn via Info-cyrus
Hi, I considered opening a Github issue, but the question seems too trivial for that. I'm playing around with cyrus-imapd-3.0.0-rc1. When I ran "cyr_info conf-lint" on the conf files from our 2.4.x production server, I got a few items I knew how to deal with, but also this: normalizeuid:

Cyrus and scale-out

2016-06-10 Thread Sebastian Hagedorn via Info-cyrus
Hi, our systems guys keep telling us that we are doing things in an old-fashioned way and should get with the program. We are currently using a single Cyrus server with roughly 13 TB of storage provided by a SAN. We used to have a Red Hat High Availability cluster, but we traded that in for

Re: imapd in race condition?

2016-04-15 Thread Sebastian Hagedorn via Info-cyrus
--On 15. April 2016 um 12:19:17 +0200 Marco via Info-cyrus wrote: I see these two processes that own all cpu resources: 28875 cyrus 20 0 278m 30m 9.8m R 98.1 0.2 73:20.74 imapd: ucxx1.xxi.it [10.10.10.53] xx^x...@xx.it xx.it!user.hd_xx.EVASE_C 24535

Re: IPv6

2016-04-11 Thread Sebastian Hagedorn via Info-cyrus
Thanks, I'm fine with that wording. --On 6. April 2016 um 12:33:08 +1000 ellie timoney wrote: Oh yeah, of course. I've added the following to man/master.8 for future releases: Services added or modified to listen on a privileged port may not be able to bind the port,

Re: IPv6

2016-04-05 Thread Sebastian Hagedorn via Info-cyrus
Hi Ellie, --On 5. April 2016 um 14:33:46 +1000 ellie timoney wrote: > Sebastian, is there anything you tried that *didn't* work, and if so, > what happened? The only thing I tried that didn't work was to add a IPv6 listener and to HUP the master process. The manpage

Re: Request: Please sign this list's messages via DKIM or SPF

2016-04-04 Thread Sebastian Hagedorn via Info-cyrus
Personally, I think that's a phenomenally stupid approach. As long as you can't show me an RFC that says you MUST or even SHOULD use SPF or DKIM, you're breaking SMTP. Due to the exponential increase of spam, we generally have to reject all messages which are not secured by SPF or DKIM, and

Re: IPv6

2016-03-29 Thread Sebastian Hagedorn via Info-cyrus
Hi Ellie, --On 29. März 2016 um 12:30:34 +1100 ellie timoney wrote: Ellie, can you please fix the listen statement to accept correctly bracketed ipv6 and backport to at least 2.5 and 2.4, shouldn't be many changes in that code. I don't think there's anything to fix

Re: IPv6

2016-03-23 Thread Sebastian Hagedorn via Info-cyrus
--On 24. März 2016 um 01:32:57 +0900 Hajimu UMEMOTO wrote: Though it is not mentioned in the manpage, the address:port notation without bracket is also accepted. You can find the following comment for parse_inet_listen() in master/master.c: * Parse the "listen"

Re: IPv6

2016-03-23 Thread Sebastian Hagedorn via Info-cyrus
--On 23. März 2016 um 15:41:25 +0100 lst_hoe02--- via Info-cyrus wrote: we've been using IPv6 for a few years now, but so far we haven't used it with Cyrus. Now we want to, and I have a few questions: Is it correct that if we use host names in the listen

IPv6

2016-03-23 Thread Sebastian Hagedorn via Info-cyrus
Hi, we've been using IPv6 for a few years now, but so far we haven't used it with Cyrus. Now we want to, and I have a few questions: Is it correct that if we use host names in the listen statement and add a record to the DNS that Cyrus will automatically listen to both the IPv4 and the

Re: Sendmail + Virtual Domains + aliases

2016-02-25 Thread Sebastian Hagedorn via Info-cyrus
--On 25. Februar 2016 um 11:04:59 +0100 Andrea Venturoli wrote: If I add that, then cyrusv2 from mailertable will not be used for oneofmydomains.com. Why use mailertable? We use this: I've followed the instructions on this page: >

Re: Sendmail + Virtual Domains + aliases

2016-02-25 Thread Sebastian Hagedorn via Info-cyrus
I was a bit brief yesterday. I have to say that I configured our sendmail more than 10 years ago and have only made minor changes since than. I don't remember the settings as well as I did back then ... --On 24. Februar 2016 um 18:15:26 +0100 Andrea Venturoli wrote: On

Re: determine whan the mailbox was last accessed

2016-01-12 Thread Sebastian Hagedorn via Info-cyrus
--On 12. Januar 2016 um 13:31:58 +0500 "Eugene M. Zheganin via Info-cyrus" wrote: So, main question is - what permission does the fud need on the mailbox to be able to provide info about it ? The right you need is 0 (zero) for user anonymous. --

Re: unable to delete corrupted mail box on cyrus v2.3.16

2016-01-11 Thread Sebastian Hagedorn via Info-cyrus
--On 11. Januar 2016 um 15:51:39 +0100 Sophie Loewenthal via Info-cyrus wrote: I have a broken mailbox that I would like to delete. This is Cyrus v2.3.16 on CentOS 6. I tried reconstructing the mailbox from scratch ( Because I suspect this was manually

Re: Sieve vacation script?

2015-12-26 Thread Sebastian Hagedorn via Info-cyrus
Hi, I've been struggling with figuring out how to set up a sieve vacation reply script. The documentation on this is pretty sparse, and the stuff I do find doesn't work. For example, [cyrus@www ~]$ sieveshell --user=resea...@episcopalarchives.org --authname=cyrus localhost connecting to

Re: Trouble with Outlook 2013, especially with the upgrade from 12/8

2015-12-16 Thread Sebastian Hagedorn via Info-cyrus
--On 11. Dezember 2015 um 16:52:07 +0200 Leena Heino via Info-cyrus wrote: We might have had similar problems with Outlook 2013: - Outlook would sometimes fail to create folders or recognize folders it had created earlier - Messages would get deleted or

Re: Trouble with Outlook 2013, especially with the upgrade from 12/8

2015-12-14 Thread Sebastian Hagedorn via Info-cyrus
--On 11. Dezember 2015 um 16:52:07 +0200 Leena Heino via Info-cyrus wrote: On Fri, 11 Dec 2015, André Schild via Info-cyrus wrote: Outlook and IMAP is just pain, it's not intended to work, otherwise who would buy the exchange server? 1) We see this rather

Trouble with Outlook 2013, especially with the upgrade from 12/8

2015-12-11 Thread Sebastian Hagedorn via Info-cyrus
Hi, we've always had more problems with users of Outlook than other clients, but in recent days they have become much graver. A number of users have lost mail in a way that we couldn't recover, even though we are using expunge_mode: delayed. There seems to be some correlation to this upgrade

Re: Trouble with Outlook 2013, especially with the upgrade from 12/8

2015-12-11 Thread Sebastian Hagedorn via Info-cyrus
users: locally stored folders that are created on the server, but deleted locally after the upgrade from 12/8. --On 11. Dezember 2015 um 17:04:49 +0100 Sebastian Hagedorn via Info-cyrus <info-cyrus@lists.andrew.cmu.edu> wrote: I have a follow-up question after talking to a user on the

Re: Trouble with Outlook 2013, especially with the upgrade from 12/8

2015-12-11 Thread Sebastian Hagedorn via Info-cyrus
--On 11. Dezember 2015 um 14:18:32 +0100 Sebastian Hagedorn via Info-cyrus <info-cyrus@lists.andrew.cmu.edu> wrote: we've always had more problems with users of Outlook than other clients, but in recent days they have become much graver. A number of users have lost mail in a way t