On Sun, 27 May 2001, Derek Martin wrote:
> What do you mean you can't get it to run?

  He's using nullclient, will cause *everything*, even local mail, to be
forwarded on to his ISP.  He may have other things wrong, too, but that's a
killer, I'm sure.  :-)

> You're missing the local mailer, which may be why sendmail won't start.  
> It's required.

  Both the Sendmail documentation and my own experience lead me to believe the
local mailer is included automatically by modern Sendmail distributions.  
(I'm not 100% sure, since I always use procmail for local delivery.)

> I also would leave out accept_unresolvable_domains unless you really need
> it.

  On a transient dial-up system fetching mail from an ISP, I think this
feature is appropriate.  The DNS lookups take time, and if they barf,
fetchmail barfs.  Anti-spam is best handled at the ISP -- remember, the
destination MX has already accepted the mail and done delivery once it reaches
the ISP mailbox.  Supplement that with a procmail recipe that delivers to
/dev/null or takes more pro-active action, if you so wish.

> Why is mail parsed into multiple folders in the mail spool?

  As a guess, because the OP was used to running everything as "root".  :-)

> As far as I can tell, ou really have no need to run the [Sendmail] daemon
> at all, so I wouldn't.

  Fetchmail really wants a local SMTP listener.  You can convince it
otherwise, but it isn't happy about it.  :-)  Running the daemon is okay, so
long as you firewall port 25 off from the Internet.

  For that matter, you should firewall your general system off from the
Internet *anyway*.  I think we've beaten that horse to death by now.  :-)

>   FEATURE(always_add_domain)dnl

  I would think this would be an undesired feature, as it could cause mail
that is well and truly local to try and route via the ISP, no?

-- 
Ben Scott <[EMAIL PROTECTED]>
| The opinions expressed in this message are those of the author and do not |
| necessarily represent the views or policy of any other person, entity or  |
| organization.  All information is provided without warranty of any kind.  |


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to