> Daniel (Sun 07.0500-11:49):
> 2)
> If I have installed qmail, then I telnet to mail.domain.com 25/110 is work well, but
>I can't get the mail from that server, what's wrong? (In this case I have
>installed/copied procmail and fetchmail from pkgtool)
> Should I re-configure/re-installed qmail again?
the logical operation is like this: incoming mail gets collected at your
isp (mail.domain.com?). you activate fetchmail on your machine, which logs
into your isp's pop3 port (110) using the password you set up with your isp
for this and gets your mail. whenever a message is transferred, fetchmail
connects locally to your smtp-daemon (port 25, host 127.0.0.1) to have it
delivered. you can configure fetchmail to pop mail for official-user-1@
isp.domain and route it to [EMAIL PROTECTED] this is part of my
~/.fetchmailrc:
# .fetchmailrc
set logfile /var/log/fetchmail
# poll interval
set daemon 77177
# defaults for every poll
defaults
fetchall forcecr
antispam 571, 550, 501
# example: poll your isp's pop3 server
poll pop3.isp.domain protocol POP3 timeout 200
user official-id pass password is local-id here
i had to specify the "forcecr" option, which was not neccessary when
fetchmail delivered via sendmail.
procmail is a sophisticated local delivery agent. you should not use it as
long as your setup doesn't work. when it works, it should get activated by
entries in local users .qmail files using "|procmail ..." lines (one
possibility of several). but for this to work the mail folders have to be in
mbox format, which is configurable in qmail but maildir is preferred for
several reasons. you should leave procmail out of the way until things work.
outgoing mail has nothing to do with this setup. it connects to port 25 of
your isp (outgoing means non-local here, and the basic setup is for a
leafnode with dynamic ip-routes). since many isp's do not relay mail and
want to spam-control their customers, they offer to act as "smart-host" for
outbound smtp. you can make sure of this by making
qmail/control/smtproutes look like ":smtp.isp.domain", just this one line
which should route outbound smtp to the smtp (not the pop3!) server of your
isp. many isp's have pop- and smtp-servers for their customers on the same
machine, but you might have to use different id's in the "poll" line in
.fetchmailrc and in qmail/control/smtproutes, like i have to.
fetchmail is started by "fetchmail -v". the logentries will contain the
time then, which helps to sort out the results of different tries while
debugging. after that fetchmail will poll every so often. the dialog with
the local smtp-deliverer is contained in the logfile.
you don't have to use the local smtp-connection. you might for instance
directly call procmail from within fetchmail using the "mda" option. then
the entire incoming-mail-chain/queue of qmail is out of the play. this
means that you don't have to start "tcpserver 0 smtp qmail-smtpd &" or have
(alternatively) "smtp stream tcp nowait root tcp-env qmail-smtpd"
configured in /etc/inetd.conf, =unless= you intend to relay mail.
for now, lets pretend your machine is the only and main mail handling
machine at home, so i can cut this answer short here...
--
[EMAIL PROTECTED]
