public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Mutt and Gmail
Date: Tue, 28 Oct 2008 08:27:28 +0900	[thread overview]
Message-ID: <5644721A67DC451A8A1DA8A90455FF8C@bouncy> (raw)
In-Reply-To: <20081027154117.GA13533@lnx3.holmesgrown.com>

Let me tidy up a few small things here.
Exim4 does in deed support both tls and ssl for smarthosts and local smtp 
authentication.
You need to install
exim4-daemon-heavy
for the advanced authenticators, ldap and sql support.

You can configure your smarthost to authenticate with ssl and tls, might 
have to do it by hand by editing files in /etc/exim4.
I personally split the config into a whole pile of little files (option in 
dpkg-reconfigure exim4-config)

then you run
update-exim4.conf
when you edit the fragments.
monolythic is ok too but you end up editing a large file and it can be 
easier to make mistakes and harder to find what you want.

the heavy deamon also supports exiscan so you can set up stuff like spam 
assassin and clamav if that floats your boat.

If your current setup works for you probably no need to go through all this 
bother.
I'm just guarding against the statements that exim4 can't do ssl or tls; i'd 
hate those sorts of ideas to get stuck in the archives when they are in fact 
not the case.
apt-get install exim4-doc-html
is a good idea
or unzip the spec.txt file in /usr/share/doc/exim4

there's an intire manual there, something that few of us have the time to 
read in these busy days however it's nice to know it is there when you need 
it.
Regards, Kerry.

----- Original Message ----- 
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, October 28, 2008 12:41 AM
Subject: Re: Mutt and Gmail


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> I never got therror concerning a mak database for exim.  I looked in
> the README files under the /usr/share/doc/exim4 for my instructions.
> Sorry, but right now I forget what I used to configure it; I suppose
> it was dpkg-reconfigure.  Sorry, I'm new to Debian so am still
> bouncing off the walls a bit.  I was a slackware user for over ten
> years so am more used to editing strait files.  I didn't find the docs
> to be all that confusing though.  In fact, one of the options in the
> config script enables me to hide the local machine name from my
> outgoing addresses and smart host over to my main mail server for non
> gmail activities.
>
> As for configuring exim to have two different smart hosts depending on
> what from address was used, that goes way over my head and I doubt any
> debconf scripts cover that.  Plus AFAIK, exim doesn't handle ssl/tls
> encryption so that's why the need for either msmtp or mutt's internal
> smtp support.  Both of these latter items support gmail.  In fact, it
> is just recent that I ran into the situation that started this thread
> and that is mutt can't find any authenticators now when I use the
> internal smtp support but I can get them through msmtp OK.  Mutt's
> smtp support works great on my laptop which is still running under
> slackware 12.0.
>
> Chuck, I don't use fetchmail or getmail on this box.  I use Gmail's
> IMAP support directly in Mutt.  It works pretty good too.
>


      parent reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Steve Holmes
 ` Chuck Hallenbeck
   ` Steve Holmes
     ` Chuck Hallenbeck
       ` Alonzo
         ` Steve Holmes
           ` Christopher Moore
             ` Steve Holmes
               ` David Csercsics
           ` Kerry Hoath [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=5644721A67DC451A8A1DA8A90455FF8C@bouncy \
    --to=kerry@gotss.net \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).