On Sun, May 21, 2000 at 08:37:21PM -0300, Richard Spencer wrote:
> I then decided to switch to Mutt, and with some
> effort, configured my .muttrc to my satisfaction.
> I used this config file to name my smtp server, 

Huh?  SMTP is for sending mail, and Mutt does not support it.

> and settled for checking only mail in my primary 
> account.
> 
> But today I tried to use Mutt to check the other
> account as well. Here's what I did:
> 
>       created a .fetchmailrc like this...
> 
> poll pop3.uol.com.br proto pop3
>   user [EMAIL PROTECTED] pass secret1
>   fetchall keep
> poll pop.a001.sprintmail.com proto pop3
>   user [EMAIL PROTECTED] pass secret2
>   fetchall keep
> smtphost smtp.uol.com.br
  ^^^

AFAICU this line tells fetchmail to forward all messages received from
pop.a001.sprintmail.com account to smtp.uol.com.br instead of delivering
them locally.  I'm not quite sure how this option works -- I've never
used it.

> But I was wrong; the mail for the second account
> didn't end up in /var/spool/mail/$USER

> Can anyone tell me:
> 1) where the mail from sprintmail might be?
> 2) which files to check for clues?

man fetchmail

> 3) a good way to tell Mutt to read my inbox
>    in /var/spool/mail first? (I already tried
>    making my /home/$USER/Mail/inbox a symlink
>    to /var/spool/mail/$USER, and that seemed
>    not to work as well; the inbox was labeled
>    in a  peculiar fashion--it became 'inbox@'.

That `@' is only shown to inform you that `inbox' is a symlink.  It is
not actually a part of the name.

> I can tell you I'm running Red Hat 6.0 on a Pentium
> Laptop, and haven't taken any steps to configure
> sendmail, although it always runs as a process.
> 
> 430 ?  S  0:00 sendmail: accepting connections on port 25

Perhaps you'll want to specify a smart host if your computer do not have
a registered domain name.  Otherwise many servers will reject SMTP
connections from you.  But maybe using a simpler MTA is a better choice.

Marius Gedminas
-- 
An NT server can be run by an idiot, and usually is.

Reply via email to