Re: server not accessible - 3.6-beta3-1

[email protected]
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
Hi,

I was surprised too, but in a different way: I have the same values. I probably found the debian 9 standard in my archive, which was also a template for me:

.../src/debian/cyrus-imapd/cyrus-imapd_2.5.10-3.debian/debian/cyrus.conf -->

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...
SERVICES {
        # --- Normal cyrus spool, or Murder backends ---
        # add or remove based on preferences
        imap            cmd="imapd -U 30" listen="imap" prefork=0 maxchild=100
        #imaps          cmd="imapd -s -U 30" listen="imaps" prefork=0 maxchild=100
...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


so i used for my production with 3.0.x:

        imap            cmd="imapd -U 30" listen="imap" prefork=0 maxchild=100
        imaps           cmd="imapd -s -U 30" listen="imaps" prefork=0 maxchild=100

Hmm, I'll have to look again :-)

Thanks,
Martin

PS: Oops, wrongly sent an hour ago


> Simon Matter <[email protected]> hat am 15.11.2022 17:06 CET geschrieben:
> 
>  
> > Thank you Ivan,
> >
> > I just checked it and modified to 
> >
> >         imap            cmd="imapd -U 60" listen="imap" prefork=10
> > maxchild=500 proto=tcp4
> >         imaps           cmd="imapd -s -U 60" listen="imaps" prefork=10
> > maxchild=500 proto=tcp4
> >
> > We will see, soon.
> >
> > The old (default) was:
> >
> >         imap            cmd="imapd -U 30" listen="imap" prefork=0
> > maxchild=100
> >         imaps           cmd="imapd -s -U 30" listen="imaps" prefork=0
> > maxchild=100
> 
> What I'm wondering is where did your cyrus.conf file come from?

------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/Tc5a2b80110a27505-M4ca0475ad9675da7b346a06d
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.