[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] HELP, please - Email is broken (Part 2)
- Subject: [cobalt-users] HELP, please - Email is broken (Part 2)
- From: Charlie Summers <charlie@xxxxxxxxxx>
- Date: Fri Jul 20 23:35:01 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Folks;
Recap; mail is being delivered incorrectly to mailboxes in
/var/spool/mail/<mailbox> instead of following the sym link to
/home/spool/mail/<mailbox>.
Now that I've had a few hours' sleep, I believe I have tracked down the
problem, and yes, kids, I caused it by wiping off some of the "Cobalt Secret
Slime" from the system.
See, yesterday I started installing SmartList, which is based on procmail.
To do so, I updated procmail to the latest stable 3.15.2. Since procmail is
doing the delivering, and procmail is doing the renaming of the BOGUS mail
boxes, it is the 3.15.2 version of procmail that is causing my problem.
And in an all-too-frequent display of stupidity, I managed to forget to
back up the original /usr/bin/procmail, instaad replacing it with the make
install on the new version.
To prove my suspicions, I'd _really_ appreciate it if someone with a RaQ3
(I dunno if there's a serious software difference between the 3 and 3i, but
mine's a 3) could offer to send their /usr/bin/procmail binary. (To avoid
overloading a mailbox I have to access manually, please don't all of you send
a copy of the binary, though, huh? ;)
Or, if anyone understands the contents of the various updates, and knows
which update up to or including "Cobalt OS Release 5.0" (I'm a little unclear
about this right now...my provider, when setting up the machine, installed
"RaQ3-en-Update-OS Release 4.0" then twenty-two 4.0.x security updates, then
"Cobalt OS Release 5.0," according to the GUI's "Install Software" page)
contains the procmail binary for the RaQ3, let me know and I'll see if I can
extract the single file from the package. (Gee, another skill to learn.)
But as a _long term_ solution, does anyone here have any idea what
settings Cobalt used when compiling procmail? Or did they rewrite the
internals? (Yes, I'm going to be posting this question to the procmail
mailing list as well.)
Charlie (who still can't receive mail, but feels better that he
at least has a line on the problem)