This is the new update section. I will put news and info regarding changes to
the structure/framework, etc here. If you want to find out what this is, just
scroll to the next horizontal line!
Februar 2002 - build platform is now RedHat 7.2. This is reflected below. Source RPMs will be provided, so it will be possible to roll your own :-). The most compley aspect of this will be the construction of a non-root user rpm environment for the courier IMAP stuff. This is VERY well explained at the courier site.
Februar 2002 - I am working on merging all the configuration files to be
under one location. This improves the distributed nature of the system, since
that location can be on a shared FS, available to many hosts. I am also working
on the standard build of sendmail 8.12.2 to incorporate that system. This has
feedback on several aspects of the system.Standard builds are protected as much
as possible.
Februar 2002 - I am working on a patch for courier IMAP to support Netscape
Messenger, which is not completely compatible. I agree with the courier author
(Sam Varshavchik) that Netscape are really responsible to fix their bugs, but the
reality is that we have to support lots of users who unknowingly use this stuff,
and then call out helpdesks when it does not work. Hence my patch. Let me know
if you are interested.
This is only the beginning. If you want to see what this system can do for you, download this MS-Powerpoint (I know) presentation. Then mail me (jthg at users dot sourceforge dot net) with your interest. I will be bringing RPMs (built on RedHat 7.1) to this site soon. The modules are all distinct, and based on standard code bases (i.e. no patching/tweaking).
This also means that you can use which ever daemon you like, so long as it can fit the function. This functional dependancy is relatively simple: LDAP integration, and maildir format mail boxes.
So why do you need F-Mail? Well the idea is that you can stick to a recognised framework for your mail system that works! And this does work. Front to back it has been tested and IS running. What you will get here are the configuration files for the various modules, and help installing them.
This is different from most offerings because it provides a buffer zone between the users & their boxes, from BOTH directions (inbound MX/reception cluster, & IMAP4/POP3 proxy cluster). In other words, you can move boxes, change usernames, etc. The users never find out (if you plan it right ;-). In theory users can migrate up & down product trees, paying for functionality, buying new domain names or not. But they never lose mail, because the box is always the same! Of course this kind of product function is beyond the scope of the mail system itself!
Unless someone out there wants to help?
The primary modules are as follows:
The first question is 'Why F in F-Mail?'. Well the answer is simple. Read The _F_riendly Manual and you will see how truly admin friendly the system is! It was designed to make the job of migrating your users from one system to another incredibly simple, and to make the system more long lived!
I have found with large mail systems that day to day management is not normally an issue. It only becomes one, when something like ILOVEYOU happens. Then the system you inherited (because you would never have done it like that ;-) lacks disk space, lacks performance, and worst of all, it lacks flexibility. So take the PPT, and let me know what you think!!!
Checkout the project details. There are some configuration files for sendmail (including the m4 configurations used to create them. I encourage you to use m4, but the final .cf files are there in case you just want to play. Be warned, the CVS config messes with the ID lines & revision numbering within the files when you view them! Please, only do this if you are an experienced sendmail.cf hacker!
More soon!!!!!
This has been brought to you courtesy of the people who paid me to design it! Sunrise Telecommunications AG.