On Sat, May 26, 2001 at 04:02:46PM -0400, Ed Robitaille wrote:
> When I first started using Linux on my home box 4+ year ago, I ran
> everyhting worked and I ran as root !!
It may have worked, but running as root is just a bad, bad idea.
> I decided to do the right thing, I stored all my config and rc scripts
> et c. I downloaded the ximian gnome 1.4. I reformatted and re-loaded
> my drive. I'm using SuSe 6.4. I set my self up as a user. I use a dial
> up ISP.
> I had been using fetchmail --> procmail --
I'm assuming that you are still doing this... you don't make that clear.
But since mutt doesn't have a pop client, I'm guessing you have to be
doing that.
> I would like then use mutt as my mua ( correct buzzword ??)
> I used send mail as my mta. I am using ximaian evolution for for writing
> this e-mail I DO NOT recommend it .
> I have 2 problems
> 1. I cannot get sendmail to run. I am using config.mc:
What do you mean you can't get it to run? You've got logs below so
it must be running... Do you mean the daemon won't start?
> FEATURE(`nullclient',`mail.eagle1sr.com')
> FEATURE(`nocanonify')
> MAILER(smtp)
> MASQUERADE_AS(`eagle1st.com')
> FEATURE(`masquerade_envelope')
> define(`SMART_HOST',`mail.eagle1st.com')
> FEATURE(`accept_unresolvable_domains')
Lots of stuff wrong here... You're missing the local mailer, which
may be why sendmail won't start. It's required. You probably don't
want to bother with nullclient or nocanonify.
Assuming you cut and pasted, you've also got a type-o in the
nullclient macro. I also would leave out accept_unresolvable_domains
unless you really need it.
> When I send my mail I get the following in my e-mail log:
>
> May 26 15:41:15 localhost sendmail[1322]: f4QJfF701322: from=-N,
> size=676, class=0, nrcpts=5,
> msgid=<[EMAIL PROTECTED]>,
> relay=root@localhost
> May 26 15:41:17 localhost sendmail[1324]: f4QJfF701322: to=--,
> ctladdr=-N (0/0), delay=00:00:02, xdelay=00:00:02, mailer=relay,
> pri=150676, relay=mail.eagle1st.com. [216.204.29.3], dsn=5.1.1,
> stat=User unknown
You seem to somehow be getting some sort of command line options where
your envelope addresses should be. That's bizarre.
> 2. When I run fetchmail, my mail is parsed into the different folder
> s of my spool directory '/var/spool/mail/*folder'. The files are
> ed.users ( owner ) rw-rw-- . I cannot r/w to them
> when I run as a user 'ed'. ?????
Why is mail parsed into multiple folders in the mail spool?
Generally, you would have fetchmail pass the mail to sendmail, then
have sendmail pass it to procmail (you can skip sendmail if you know
how to configure fetchmail to do it) and then use procmail rules to
filter mail into folders in your home directory.
You don't have to do it that way, but I wouldn't put them in the mail
spool directory... you should probably be the owner of the directory
where you filter your mail. I have no guess as to why you can't read
or write the files, ithout seeing the output of this:
ls -la /var/spool/mail
It's very likely that you've got some sort of permission problem on
the spool directory, or who knows what else.
I'm really not getting a good sense of what you want to do, what
you're actually doing, and why you're doing it that way from reading
your message. I don't know how helpful this will be, given that I
don't have a clear understanding of what you're trying to do, but here
goes:
If you run sendmail as a daemon on the local host, people will be able
to connect to it from the internet. As far as I can tell, ou really
have no need to run the daemon at all, so I wouldn't.
You probably want your mail masqueraded to your ISP's domain, but bear
in mind that if you send mail as user "ed" that your return address
will be "[EMAIL PROTECTED]" whereas your e-mail address actually appears
to be erobitaille. You need to configure your MUA to change that (I'm
not sure if Mutt can do that) or change your username to erobitaille
on your local system.
The m4 file you will want to use will look something like this:
FEATURE(always_add_domain)dnl
FEATURE(use_cw_file)dnl
FEATURE(smrsh, `/usr/lib/sm.bin/smrsh')dnl
FEATURE(masquerade_envelope)dnl
FEATURE(access_db)dnl
define(`confME_TOO', True)dnl
MAILER(local)dnl
MAILER(smtp)dnl
MASQUERADE_AS(`eagle1st.com')dnl
define(`SMART_HOST',`mail.eagle1st.com')
This is modified heavily from my debian mail config, so you'll need to
make sure that the paths and whatnot are correct for your distro. For
example, the path for smrsh on Red Hat systems is this:
FEATURE(`smrsh',`/usr/sbin/smrsh')
If it doesn't automatically filter mail through procmail, you may also
need these:
FEATURE(local_procmail)
MAILER(procmail)
define(`PROCMAIL_MAILER_PATH',`/usr/bin/procmail')
BTW, even though I could get this working for myself, I still agree
with Ben. If I were in your position, I'd probably switch back to
Netscape or take a look at Kmail. It wasn't that bad when I looked at
it about 2 years ago, and it must have gotten better since then...
You can get sendmail to work, but it's sort of a pain ITA for the
environment you're describing if you don't know what you're
doing. [Plus, I'm basically very lazy.]
HTH.
P.S. to briefly address gaf's comment, I agree that you CAN get this
working with an m4 config file that's not too different from the stock
one. The problem is figuring out which options you need to
change/delete/add, and understanding what they do. This, for someone
unfamiliar with sendmail, can take hours, or even days of reading
docs... It's worth noting that even though you may only need to
change 4 lines in the m4 file, the resulting sendmail.cf file will
likely be VASTLY different, including different config options, and
entirely different mailer rulesets, which is suggestive of just how
complex the differences really are, despite appearances.
--
---------------------------------------------------
Derek Martin | Unix/Linux geek
[EMAIL PROTECTED] | GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu
**********************************************************
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
**********************************************************
