On Mon, March 23, 2009 12:55 am, Karl Pearson wrote:
>
> On Sun, March 22, 2009 10:38 pm, Alan in Toronto wrote:
>> On Sat, March 21, 2009 1:03 am, Karl Pearson wrote:
>>>
>>> On Fri, March 20, 2009 10:28 pm, Alan in Toronto wrote:
>>>>
>>>>
>>>> On Sat, March 21, 2009 12:17 am, Paul Lesniewski wrote:
>>>>> On Fri, Mar 20, 2009 at 8:24 PM, Alan in Toronto
>>>>> <Alantoronto@xxxxxxxxxxxxxxx> wrote:
>>>>>>
>>>>>>
>>>>>> On Fri, March 20, 2009 11:01 pm, Paul Lesniewski wrote:
>>>>>>> On Fri, Mar 20, 2009 at 4:28 PM, Alan in Toronto
>>>>>>> <Alantoronto@xxxxxxxxxxxxxxx> wrote:
>>> << stuff deleted >>
>>>>>>>> Again, as with the original Courier config, this seems to work.
>>>>>>>> But, is this
>>>>>>>> optimal
>>>>>>>> or correct? Could someone in the know please give me some info.
>>>>>>>> about the proper
>>>>>>>> config values for a Dovecot server?
>>>>>>>
>>>>>>> config/conf.pl --> D --> "dovecot"
>>>>>>>
>>>>>>> Or look at the settings in doc/presets.txt
>>>>>>
>>>>>> Thanks Paul. I'm configuring using the Admin plugin. I looked at
>>>>>> doc/presets.txt.
>>>>>> With those Dovecot settings, I get that error:
>>>>>>
>>>>>> ERROR: Could not complete request.
>>>>>> Query: CREATE "Trash"
>>>>>> Reason Given: Unknown namespace.
>>>>>>
>>>>>> The key value seems to be "Default Folder Prefix"
>>>>>> (default_folder_prefix). If it
>>>>>> is
>>>>>> set to <none> (empty string) as specified for Dovecot in
>>>>>> doc/presets.txt, I get
>>>>>> that
>>>>>> error. But if I change it to what I used for Courier, INBOX., then
>>>>>> everything
>>>>>> seems
>>>>>> to work. This is what I have now:
>>>>>>
>>>>>> �IMAP Server Type: Dovecot
>>>>>> �IMAP Folder Delimiter: detect
>>>>>> �Default Folder Prefix: INBOX.
>>>>>>
>>>>>> I don't understand why doc/presets.txt Dovecot settings give me
>>>>>> that
>>>>>> error, so
>>>>>> even
>>>>>> though things appear to work with different settings I don't know
>>>>>> if
>>>>>> they are
>>>>>> optimal.
>>>>>
>>>>> It is possible that Dovecot has changed its standard configuration
>>>>> since the presets were developed (someone with some familiarity with
>>>>> Dovecot could chime in),
>>>>
>>>>> but given that we don't get reports about
>>>>> this problem, it seems it might be a custom or one-off configuration
>>>>> issue on your system.
>>>>
>>>> Perhaps it's like the documentation for UW-IMAP a few years ago. The
>>>> documented
>>>> config really seemed to be wrong, so based on trial and error testing
>>>> and detailed
>>>> documentation, I documented a config that worked well on several UW
>>>> servers.
>>>> Afterward, several people copied that config and replicated it to
>>>> other
>>>> sites
>>>> recommending it as the ideal config for SM on UW-IMAP.
>>>>
>>>>> The default folder prefix value isn't something
>>>>> that is going to be "non-optimal" when set some other way - it's not
>>>>> a
>>>>> performance setting. If INBOX. works for you, and ALL folder
>>>>> operations work as expected, then that's what you should use.
>>>>
>>>> Okay, that's good to know. Sort of an "if it seems to work, it's
>>>> working"
>>>> philosophy. I can work with that. :)
>>>>
>>>> Thanks Paul. P.S. Saw Richard Underhill's quintet recently in a tiny
>>>> club with me
>>>> just two armlengths from Richard. He was awesome!
>>>
>>> I have used UW-IMAP and now use Dovecot because it's just plain fast.
>>
>>
>>> I'd check /etc/dovecot.conf to see if there's any special settings,
>>> like
>>> what the namespace is set to, specifically mail_location = which if
>>> defaulted, is $HOME/mail and which is why SM thinks you should have
>>> that
>>> set to "".
>>
>> Thanks. I'm using PuTTY to SSH to root to find that. I've a neophyte at
>> using PuTTY
>> though, so I can't even find how to use a "find" command to search
>> within a text
>> file. I found /etc/dovecot.conf as you said, and used pico to view it.
>> Here is a
>> block with entries referring to mail_location.
>>
>> # REMEMBER: If you add any namespaces, the default namespace must be
>> added
>> # explicitly, ie. mail_location does nothing unless you have a namespace
>> # without a location setting. Default namespace is simply done by having
>> a
>> # namespace with empty prefix.
>> namespace private {
>> # Hierarchy separator to use. You should use the same separator for
>> all
>> # namespaces or some clients get confused. '/' is usually a good one.
>> # The default however depends on the underlying mail storage format.
>> #separator =
>>
>> # Prefix required to access this namespace. This needs to be
>> different for
>> # all namespaces. For example "Public/".
>> prefix = INBOX.
>
> That's the setting right there. As Paul said, it's a good thing to leave
> it alone, since it's working. Unless you are very confident that
> 'fixing' it won't break anything else.
Ah, I thought so (due to your earlier pointing me in that direction.) So, in a
normal/standard vanilla Dovecot that value would be empty?
cPanel releases used to include Courier as default. Now they use Dovecot (although I
could switch to Courier by selecting it on one of the control panel web interface
pages which would then do some backend change to config.) Perhaps they kept the old
prefix value to avoid breaking users' use of things like SquirrelMail. Or, perhaps
the developers just forgot to change it, which also happens in cPanel upgrades.
> To find text in a file, use grep, i.e:
>
> grep INBOX /etc/dovecot.conf
>
> or, to find a given word or phrase within a group of files, you could do:
>
> FNDSTR="prefix = INBOX"
> grep $FNDSTR *
>
> Linux uses the same 'wildcards' as DOS did (32/64 bit MS OSes).
>
> You can also use a find command to parse through directories recursively:
>
> find . -exec grep $FNDSTR {} \; -print
>
> which will do the grep against every file in the current directory (.)
> and recurse through all the subdirectories underneath.
>
> </lesson>
LOL. Thanks for the lesson. I appreciate it. I'm a newbie to SSH, so your lesson
will be saved along with other commands that I have learned. I've found a few pages
with some commands, but nothing comprehensive. A little comes back from old lizard
memory from when I used to work on Solaris years ago.
Thanks very much!
>>
>> # Physical location of the mailbox. This is in same format as
>> # mail_location, which is also the default for it.
>> #location =
>>
>> # There can be only one INBOX, and this setting defines which
>> namespace
>> # has it.
>> inbox = yes
>>
>> # If namespace is hidden, it's not advertised to clients via
>> NAMESPACE
>> # extension. You'll most likely also want to set list=no. This is
>> mostly
>> # useful when converting from another server with different
>> namespaces which
>> # you want to deprecate but still keep working. For example you can
>> create
>> # hidden namespaces with prefixes "~/mail/", "~%u/mail/" and "mail/".
>> #hidden = yes
>>
>> # Show the mailboxes under this namespace with LIST command. This
>> makes the
>> # namespace visible for clients that don't support NAMESPACE
>> extension.
>> #list = yes
>>
>> # Namespace handles its own subscriptions. If set to "no", the parent
>> # namespace handles them (empty prefix should always have this as
>> "yes")
>> #subscriptions = yes
>> #subscriptions = yes
>>
>> Does all that tell you anything? What else should I look for?
>>
>>
>>> It might have been changed to match your old server. If it
>>> was, leave it alone as you found it to work.
>>
>> Yeah, as long as it's working that's a good start. :)
>>> I'm kind of a 'purist'
>>> (whatever that means) and preferred to change from SM settings of
>>> mail/
>>> as the setting and liked the "" setting for Dovecot because that meant
>>> when I helped others setup their IMAP email in SM or whatever, I could
>>> just leave that setting alone and it would work 'out of the box.' For
>>> going forward, I find that the less things have to be 'tweaked' to
>>> make
>>> them back-compatible, the happier I am as an admin.
>>
>> As a rule, I agree with you. I prefer more "vanilla" installations, so
>> things are as
>> expected and other stuff could be added on easily because the base setup
>> is as
>> expected.
>>
>> Thanks for your help, and thanks Paul for your help.
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
