-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 It sounds like simple-smtp may be quite similar to msmtp. Do you use it for both your normal and gmail? I could probably do a similar thing here and completely remove exim but I think exim might be needed to support auto services like cron and other system utils that may generate e-mail such as debsecan. On Mon, Oct 27, 2008 at 04:24:44PM -0400, Christopher Moore wrote: > Hello, > Here I'm using getmail and simple-smtp to handle receiving and sending > mail. For gmail, I have mutt set up to use imap. It seems to be > working fine for me. I found an article on how to set it up. I have a > special config file for gmail which I call gmail-mutt. When I want to > use gmail I run mutt like this: > mutt -F gmail-mutt > > For a single user system, sendmail and exim4 are overkill even though > you can get them to work. > > Chris > On Mon, Oct 27, 2008 at 08:41:17AM -0700, Steve Holmes wrote: > > -----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. > > > > On Mon, Oct 27, 2008 at 09:47:15AM -0500, Alonzo wrote: > > > Hello chuck, > > > > > > I would like to use my AIM address for sending mail, however... i'm not > > > exactly sure how to configure exim4 using debconf. I'm confused with the > > > questions. so I've removed it for now until I have better documentation. > > > Also when I start up debian lenny, it complains about send mailno make > > > database that i have to build it by hand. Anyone know what that's about? > > > > > > Alonzo > > > ----- Original Message ----- From: "Chuck Hallenbeck" <chuckh at ftml.net> > > > To: "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca> > > > Sent: Monday, October 27, 2008 4:16 AM > > > Subject: Re: Mutt and Gmail > > > > > > > > >> Steve, > > >> > > >> I use mutt too, but have always let it hand the outgoing stuff off to > > >> exim4 for handling. Exim4 spools the outgoing items, so it you often > > >> send with attachments, you don't have to wait while your MUA completes > > >> the send. You also have /etc/email-addresses and /etc/aliases to help > > >> adjusting your return address and routing your arrivals. If you have > > >> not already done so, you might want to consider getmail to replace > > >> fetchmail, if you are using it. > > >> > > >> Chuck > > >> > > >> > > >> On Sun, Oct 26, 2008 at 08:26:46PM -0700, Steve Holmes wrote: > > >>> -----BEGIN PGP SIGNED MESSAGE----- > > >>> Hash: RIPEMD160 > > >>> > > >>> I looked at the exim logs and gmail was not mentioned anywhere; > > >>> besides, I have mutt configured to go to gmail directly. These later > > >>> versions of mutt allow for direct smtp with appropriate ssl/tls > > >>> encryption. I don't know, but I fell back to using msmtp for the > > >>> transport functions like I used to use and that works fine. I wonder > > >>> if it's got to do with the way mutt was configured/compiled for debian > > >>> or what. At least it works now even if I have to use an external > > >>> component to move the mail. Thanks for the idea though. > > >>> > > >>> On Fri, Oct 24, 2008 at 02:56:46PM -0400, Chuck Hallenbeck wrote: > > >>> > Steve, > > >>> > > > >>> > You are probably using exim4 to send your mail to a smart host. Look > > >>> > at: > > >>> > > > >>> > /etc/exim4/passwd.client > > >>> > > > >>> > Chuck > > >>> > > > >>> > > > >>> > On Fri, Oct 24, 2008 at 11:52:45AM -0700, Steve Holmes wrote: > > >>> > > -----BEGIN PGP SIGNED MESSAGE----- > > >>> > > Hash: RIPEMD160 > > >>> > > > > >>> > > I've had mutt set up to work with gmail for some time now and all and > > >>> > > all, it has worked quite well. But lately after installing Debian > > >>> > > some time after that I keep getting an error when trying to send mail > > >>> > > to the gmail smtp server. > > >>> > > > > >>> > > No authenticators available > > >>> > > > > >>> > > I've checked out all the ssl and tls related packages; I can read > > >>> > > mail > > >>> > > from gmail but I just can't seem to send anymore. Are there any > > >>> > > mutt/gmail users out there who might be able to shed a light on this > > >>> > > matter? > > >>> > > -----BEGIN PGP SIGNATURE----- > > >>> > > Version: GnuPG v1.4.9 (GNU/Linux) > > >>> > > > > >>> > > iEYEAREDAAYFAkkCGX0ACgkQWSjv55S0LfHLWQCgniV5rffW2PqVA1NvzAQbwwHu > > >>> > > WRgAnRNyyqFlzd8q9vo9PGAEgnkxyEEI > > >>> > > =/Ofr > > >>> > > -----END PGP SIGNATURE----- > > >>> > > _______________________________________________ > > >>> > > Speakup mailing list > > >>> > > Speakup at braille.uwo.ca > > >>> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >>> > > > >>> > -- > The Moon is Waning Crescent (17% of Full) > > >>> > > > >>> > My web site: http://hallenbeck.ftml.net -- my telephone: > > > >>> 1-518-334-9022. > > >>> > -------- > > >>> > It is wise to keep in mind that neither success nor failure is ever > > >>> > final. > > >>> > _______________________________________________ > > >>> > Speakup mailing list > > >>> > Speakup at braille.uwo.ca > > >>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >>> -----BEGIN PGP SIGNATURE----- > > >>> Version: GnuPG v1.4.9 (GNU/Linux) > > >>> > > >>> iEYEAREDAAYFAkkFNPYACgkQWSjv55S0LfFjQgCfQxf5UgbhE48x7JelF727bGdg > > >>> bOMAoI5XTasRoJ3rove9llTUKoiCxk7a > > >>> =etye > > >>> -----END PGP SIGNATURE----- > > >>> _______________________________________________ > > >>> Speakup mailing list > > >>> Speakup at braille.uwo.ca > > >>> http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >> > > >> -- > > >> The Moon is Waning Crescent (3% of Full) > > >> > > >> My web site: http://hallenbeck.ftml.net -- my telephone: 1-518-334-9022. > > >> -------- > > >> It is wise to keep in mind that neither success nor failure is ever final. > > >> _______________________________________________ > > >> Speakup mailing list > > >> Speakup at braille.uwo.ca > > >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >> > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup at braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.9 (GNU/Linux) > > > > iEYEAREDAAYFAkkF4R0ACgkQWSjv55S0LfEoPgCguwOPO6tpv828DBU3tzikcLaM > > PTMAnRcCIAawRUxE5NRRguyo/3scVbDT > > =ptHS > > -----END PGP SIGNATURE----- > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkkGQKwACgkQWSjv55S0LfG0MgCgk+tnWwPlt2dILxQ7IWVSB4Yi z28AnjdyNW91Nejwv2xWJnAiukT4E/aX =rv50 -----END PGP SIGNATURE-----
