On Sun, May 21, 2000 at 08:37:21PM -0300, Richard Spencer wrote:
> When I began using Linux I started with
> Red Hat 6.0 and used KDE's KMail for a MUA.
>
> At that time I was checking 2 email accounts
> for mail, which was easy to implement, but I wasn't
> thrilled about the lack of configurability, and
> wanted a text-based MUA.
>
> 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,
> 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
Make sure fetchmail is working by invoking a test with fetchmail -v.
This will show where it's being placed and if it's working. From what I
can tell you have Mutt configured where to read your email but its not
the actual mechanism that is deciding where to put your incoming email.
Are you using procmail?
> When I ran fetchmail, I was happy to see that
> messages were being read, and not deleted.
> So happy in fact, that I went ahead and changed
> both 'keep' entries to 'nokeep'
>
> I noted that my mail for the first account was
> ending up in /var/spool/mail/$USER and was
> confident that all of the mail would end up there.
>
> I thought I'd have to change my .muttrc line:
>
> set spoolfile='/home/$USER/Mail/inbox'
> to set spoolfile='/var/spool/mail/$USER'
Mutt only looks where you tell it but does not deliver to this location.
This is a function of sendmail in your situation.
Fetchmail will use your MDA to determine where to put your email. Here
is an excerpt from the fetchmail man page.
____
As each message is retrieved fetchmail normally delivers
it via SMTP to port 25 on the machine it is running on
(localhost), just as though it were being passed in over a
normal TCP/IP link. The mail will then be delivered
locally via your system's MDA (Mail Delivery Agent, usu-
ally sendmail(8) but your system may use a different one
such as smail, mmdf, exim, or qmail). All the delivery-
control mechanisms (such as .forward files) normally
available through your system MDA and local delivery
agents will therefore work.
___
I think you may need to change a sendmail setting to change your default
mail box. Otherwise you could use procmail to filter into a different
mailbox too.
Your sprint mail is probably in /var/spool/mail/$USER.
Corey
>
> but anyhow was satisfied that the mail ended up
> SOMEWHERE.
>
> But I was wrong; the mail for the second account
> didn't end up in /var/spool/mail/$USER
>
> I put the following in .muttrc so that I could
> read my incoming mail, but after changing to
> another directory, couldn't easily change back
> (which I could easily do when /home/$USER/Mail/inbox
> held inbound mail.)
>
> Can anyone tell me:
> 1) where the mail from sprintmail might be?
I had procmail configured incorrectly before and my email turned into
vapor. Never to be found.
> 2) which files to check for clues?
> 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@'.
>
> 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
>
> thanks!
>
---end quoted text---
--
Best Regards,
Corey
