Mail Utility 1.0.000 Revised and Enhanced

[tarantir]

Hello all,

Back in October 2010 I introduced a couple of modules I developed for Managing Virtual Postfix/Dovecot implementations (Mailbox, Alias, Domains) and Amavis Policies and Message Quarantine. The attached Mail_Utility_eGroupware_Module.pdf details the features and also contains screen-shots of the interfaces.

Over the holiday I consolidated and re-wrote a portion of the applications as well as added new features such as White/Black Listing and Quarantined Notifications using EGroupware async.

Mail Utility (mailutil) is an EGroupware application/module which provides an interface for managing virtual Postfix/Dovecot/Amavis implementations that utilize a MySQL back-end.

This module is intended to enhance EGroupware by integrating it with virtual Postfix/Dovecot/Amavis implementations that utilize a MySQL back-end vs. an LDAP back-end. Ideally the Message Quarantine, Amavis Policies, and Message White/Black Listing features (see the dependency matrix below) could be used in conjunction with EGroupware implementations which are integrated with LDAP.

The new submission can be found in eGroupWare 3’rd party applications
(http://www.egroupware.org/egroupware/index.php?menuaction=tracker.tracker_ui.edit&tr_id=2747)

Mail_Utility_eGroupware_Module.pdf (938 KB)

It is still a work in development so I will update the submission a periodic intervals.

I hope you find the application useful.
Randy T

[camro]

thanks, it is the tool what i’m looking for …
my mind: ldap is not really the solution, which has future …
the auth itself can be done easier via sql - and for security reason, the admin only must know how the GRANT ccommand is working …
well, now i’m trying this tool, because the only 1 part what i miss in EGWis, the mail admin …
also mailutil have spamassasin, etc…

for me the first is:
1.) aliases
2.) quota
3.) forwarding
mail -> auth -> i will do via: direct check against egw_accounts (account_lid / account_pwd / account_status)
mail -> aliases -> i will do it via: check against egw_mailutil_alias (address / goto / domain / active)
mail -> quota -> i will do it via: check against egw_mailutil_mailbox (username / domain / quota / active)
(maildir: i will use the default, otherwise to dangerous)
but ? FORWARDING A COPY TO// ONLY FORWARDING TO ? how should i handle the forwarding email accounts + option for “only forwarding” or “forward a copy to”?
is there anything planned ? extra table extra gui ?

the only idea what i have is, via sieve server, and let do this every account by himself, but then, if i want change this, i mustlogin to this account …hmm
so, the forwarding is missing for me… or i’m blind ?

[tarantir]

My apologies for the delayed response.

You did not miss anything. Regarding forwards, I am using the standard sieve implementation with Dovecot integrated with eGroupware. The forward/vacation functionality in the sieve integration is very good and I saw no need to improve upon it.

If using sieve you are correct, if you an managing a user specific forward typically I believe you would maintain per user. I believe you can setup global sieve rules. I may be mistaken, but to your point that is something you would have to maintain outside of EGW.

Good luck I would be interested to hear your findings.

Randy T