From: "Michael Higgins" <mhiggins@banfieldgroup.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Sylpheed-Claws / Claws-Mail / Postfix -- the gentoo way
Date: Wed, 7 Feb 2007 13:23:14 -0800 [thread overview]
Message-ID: <005401c74afe$2dc089d0$6564a8c0@TBG.local> (raw)
In-Reply-To: <20070207185130.3616dfbb@krikkit.digimed.co.uk>
> -----Original Message-----
> From: Neil Bothwick [mailto:neil@digimed.co.uk]
> On Wed, 7 Feb 2007 09:40:59 -0800, Michael Higgins wrote:
>
> > Anyway, what I don't understand is the maildir, MH, mbox, qmail
> > delivery thing. I followed a wiki[1] which suggests I need to use
> > rcvstore command in a .forward file, etc. and to set up my delivery
> > using nmh if I'm a sylpheed user. This has worked for a
> while and is
> > working for me again.
> >
> > My question is, does anyone know if this is still needed?
> Somehow it
> > looks as if claws should handle its own delivery now, or be able to
> > use maildir?
>
> maildir is mail storage, not delivery. I use claws-mail with
> postfix and it's just a matter of setting the SMTP server to
> localhost, or wherever your postfix server lives.
Well, I use the "sendmail" option instead of smtp. Either one works for me.
>
> How do you collect mail? It's probably easiest to let postfix
> store incoming mail in a local maildir
I can't see how one makes that happen. FEX, mutt creates a maildir
'.maildir', but postfix config template lists 'Maildir/' as option. IDK what
the defaults are, nor what they should be. It _seemed_ like leaving
home_maildir [or whatever related option] unset in the config delivers to
~/.maildir. Like it's a gentoo-provided default, or something.
This is what I'm questioning... is there a gentoo-dev preference for not
using MH (or for using .maildir not Maildir specifically) that's going to
catch me up in the future. Now, I'm collecting it to the right place by
having to set up nmh and a .forward file in ~/.
> store and run a local
> IMAP/POP server - I use dovecot for this.
>
Well, this is a fix for the difficulty I had. I guess claws has options only
for pop or imap or local mbox. Not maildir, maybe that's what the extra
'-maildir' ebuild is supposed to remedy. (IDK. It didn't seem to make a
difference.) The instructions from the wiki for postfix regarding sylpheed
is to use nmh and ~/.forward.
I know MH is a storage thing, but the messages delivered to postfix have
magically 'just shown up' in the [MH] mail folder used by claws, I suppose
as a function of the files created by install-mh and .forward, as indicated
in the wiki.
I guess that's just the way to go as it works, or... running dovecot...
which would moot the problem I have now... and give me mail access via a
client not on my home machine.
So, has anyone found a shell mailreader that would use MH folders? I thought
I'd found a way in the past for mutt to do so, but it escapes me now. Maybe
this will teach me to backup /etc before the disk craps out next time. ;-)
Thanks for your reply.
Cheers,
--
Michael Higgins
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2007-02-07 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:40 [gentoo-user] Sylpheed-Claws / Claws-Mail / Postfix -- the gentoo way Michael Higgins
2007-02-07 18:51 ` Neil Bothwick
2007-02-07 21:23 ` Michael Higgins [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005401c74afe$2dc089d0$6564a8c0@TBG.local' \
--to=mhiggins@banfieldgroup.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox