If you'll give it consideration I could rip AngleMail out of
phpGroupWare into a standalone webmail.
(I'd do it for the fame of the few people who know me ...)
www.anglemail.org
there is a demo of an older version at:
https://demo.axisgroupware.org:4430/login.php
check out the email part of the demo.
Paul Iadonisi (pri.rhl1(a)iadonisi.to) wrote:
>
>On Wed, Jul 23, 2003 at 03:35:41PM -0400, Bill Nottingham wrote:
>
>[snip]
>
>> We're actually considering for this upcoming release:
>>
>> - adding in cyrus-imap
>> - taking out uw-imap
>>
>> Opinions?
>
> My vote is definite thumbs up for cyrus-imap. Simon Matter's rpms have
>also been well put together (and have only been getting better) and would
>probably only require minor tweaks to fit into Red Hat Linux nicely.
> On a sort of related note, I'd like to see something better than
>squirrelmail (or an additional choice) for webmail. I know that comment
>might generate some flames, but my problem with it is that it claims to be
>modular, but I have a hard time calling something modular when most of
>the additional modules I've seen require modification of some other source
>files. Maybe it's bad module design, but I suspect that's not the case.
>I'd rather see something that treats modules the way, for example, drupal
>does (http://www.drupal.org/). Drop the right .module file in modules
>directory and add whatever other files you need to, and the function is
>added. No mucking around with core source files.
> I tried out squirrelmail mostly because I didn't want to learn sieve
>(I can be lazy at times :-)) and saw that it had a sieve module. But then
>I got frustrated because I could just apply the errata for squirrelmail and
>expect everything to work. Sieve is but *one* of the reasons I like
>cyrus-imapd. It would be nice to have a webmail program (that handled
>sieve or had extensions for it) that was a little easier to deal with
>from admin point of view.
> Alternatives? Not sure. Horde's IMP, possibly, but I don't know how
>well it meets my above criteria, and I know it's a whole suite of web apps,
>so it would have to be looked a more closely. Don't want TOO much cruft.
>
>--
>-Paul Iadonisi
> Senior System Administrator
> Red Hat Certified Engineer / Local Linux Lobbyist
> Ever see a penguin fly? -- Try Linux.
> GPL all the way: Sell services, don't lease secrets
>
>
>http://www.redhat.com/mailman/listinfo/rhl-devel-list
--
That's "angle" as in geometry.

Prior to this first beta, uw-imap was configured in alphas / rawhide with
plaintext authentication disabled when connecting over unsecured connections
(ie, pop / imap, but not pops / imaps).
In beta1, uw-imap and dovecot both accept plaintext auth via at least imap
(didn't try pop). Was it decided that the world's not ready to give up
plaintext yet after all? Or just an accidental reversion?
later,
chris

Hi,
When looking at a bug report in IPv6 initscripts:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=86210
I came across a very strange bug. When a command is run from
interactively, it works fine. When it's run via hotplug, it bugs under a
very specific scenario: sometimes when we're redirecting stderr to stdin.
The chain of commands is:
/sbin/ifup eth1
/etc/sysconfig/network-scripts/ifup-ipv6 eth1
ipv6_add_addr_on_device eth1 fec0::2/64
[in /etc/sysconfig/network-scripts/network-functions-ipv6]
ipv6_exec_ifconfig eth1 inet6 add fec0::2/64
LC_ALL=C /sbin/ifconfig eth1 inet6 add fec0::2/64 2>&1
The last fails, for some unknown reason with error code 1 and no output
when run non-interactively; the code fragment in full is:
---8<---
##### Wrapper for used binaries
## ifconfig
# $*: <arguments...>
# return code: result of execution
ipv6_exec_ifconfig() {
local options=$*
LC_ALL=C /sbin/ifconfig $options 2>&1
return $?
}
---8<---
One can work around the issue by removing "2>&1" (again, for whatever
reason?!?). However, we really shouldn't change that code in the source,
because some functions depend on that to eliminate error messages.
I did a prototype change, and modified the relevant
ipv6_add_addr_on_device:ipv6_exec_ifconfig function to use ipv6_exec_ip; a
similar problem appeared (so, it doesn't seem to be specific to the
application executed).
Any ideas/thoughts? This seems so weird I'd like some pointers what could
be wrong here..
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

http://www.fedora.us/wiki/QAChecklist
Some highlights from Fedora's packaging guidelines... for now the easier
points. I'm avoiding the Epoch discussion for now since I am short on
time.
1. Are the pre- and post(un)install scripts correct?
=================================================
If it installs files named **.so.* into %{_libdir}, is there a %post -p
/sbin/ldconfig and %postun -p /sbin/ldconfig?
If it has info files, is there a %post script that installs them, and a
%postun one which removes them (and only on erase, not upgrade)?
2. Finding Missing BuildRequires
================================
http://www.fedora.us/wiki/HOWTOFindMissingBuildRequires
Here is a brute force method of finding missing package BuildRequires.
This works a lot better if you have a local apt/yum repository, or cache
everything.
Any suggestions for a cleaner way of testing for missing BuildRequires?
Any suggestions for the "list of packages that should not be in
BuildRequires" because they occur too frequently and should be in a
standard build environment?
We should define a standard minimal build environment for RHLP. Fedora
currently does so implicitly with the dependencies of
fedora-rpmdevtools.
3. Finding Redundant BuildRequires
==================================
http://www.fedora.us/wiki/HOWTOUseRequires
How not to be overzealous in adding BuildRequires, and including
versioned dependencies when not needed. This document needs to be
clarified a bit but otherwise good.
4. RPM Macros
=============
http://www.fedora.us/wiki/RPMMacros
Whenever possible use directory macros rather than hard coded
directories. RHLP's docs should probably state the "why" too.
5. Strict Directory Ownership
=============================
Any directory created by the package should be owned with a %dir entry
within %files. rpm -vv shows unowned directories during installation,
and I believe Enrico wrote a tool to test many RPMS and look for unowned
directories.
Attacking Epoch when I have more time later this week...
Warren Togami
warren(a)togami.com

Several times I've had difficultys bringing up eth0 after an OS install
and found that setting "Plug and play OS" to "no" in the bios setup
would cause Kudzu to find the nic and everything worked. This helped
with 3 diffenent nics, including a 3c905c with rh9 and a sound card.
Is far as I can tell the bios was assigning an IRQ and/or IO address
after I made the change so that the device was ready for linux (kudzu)
to use. Does linux normally handle this or does the bios need to set
this way normally?
Scott Becker