Jeffrey,
We are using Maia in almost the EXACT same configuration you
are
planning. We are using CentOS 5 and running a MS Exchange
server
internally. We also provide our Maia filtering for some of
our customers
who run their own Exchange servers at their offices, and for
smaller
email hosting that we do on other linux servers. The
additional servers
that we host email for however, are irrelevant as far as the
setup and
differences between what you are planning, and what we are
doing. It's
really the same setup.
As for the distribution groups, those get separated at the
Exchange
server level. So Maia just sees them as 1 email address. If
you need to
give your users Maia access for managing the distribution
group email
address(es), then you can just add a Maia account for the
email
distribution list. Immediately upon creating this account,
and email
will be sent to your distribution list with the login
information.
You'll probably want to lock down the password in Maia for
the
distribution list, so that the members of the list don't
lock eachother
out of that Maia account.
FYI, each user will also have their own Maia account. So
they'll need to
log into Maia with the email address that the sender was
using when
sending to them (either their own email address or the
distribution
list).
On second thought, there may be another way to do this. Maia
allows you
to assign more than one email address to a maia user
account. However, I
don't know whether more than 1 Maia user can share the same
email
address as a secondary address. I don't know how Maia would
handle that
on the database side. Maybe somebody else in the list can
tell you.
Concerning user Authentication:
You could use just about any authentication method you want
in your
situation (assuming that the only inside server you are
using Maia for
is your company's exchange server). I would probably just
use Maia's
internal user database. However, POP, IMAP & LDAP would
work if you make
these accessible from your Exchange server (or other DC w/
LDAP), but I
am left in question again regarding whether you can share a
secondary
email address among multiple Maia users. If not, then users
needing to
manage the Maia account for the Exchange distribution list
would need to
log into Maia using a user account specific for that email
distribution
list. Authenticating against your POP or IMAP server (or
other server)
is pretty cool, except that distribution groups don't have
passwords in
Active Directory. So you'd need to create a separate account
in AD that
is a "real" user account with a password. Then
within Maia you could
assign the distribution group's email address to that new AD
user.
I would probably just use Maia's internal user database, and
just have a
separate Maia user account for each distribution group. Then
only the
users in that distribution group would be given the
password. I don't
think there are really any privacy issues there, since
everybody in the
distribution list sees every email sent to it, then allowing
them to
manage those same messages in Maia, probably is not a big
deal. The
biggest problem may just be that they have differing
opinions on what is
SPAM & what is not. Or on a user accidentally deleting a
message from
Maia's SPAM quarantine, rather than rescuing it. This would
prevent
everyone in the distribution list from ever receiving that
message
(which is probably NOT cool).
If you have a very large user base, and people who would
have problems
with the possibility of dealing with more than one
username/password,
then you may want to implement my above suggestion for using
either pop,
imap or ldap authentication. Other people in the mailing
list may have
more ideas too, but my suggestions should definitely work. I
actually
haven't used Maia w/ LDAP auth, but I have with the others.
Let me know if you need more info on using Maia w/ MS
Exchange.
As for CentOS 5, to tell the truth, to me it was a PAIN
getting it all
setup. I did use RPMForge's repository, which made things
much easier,
but I still think that the Maia community should come up
with an easier
installation method. I was googling all over the place to
resolve some
of the dependencies. And sometimes maia's check-config
script would tell
me that I needed the "db" package, and I wouldn't
know whether it was
the php module or the perl module. The db package may not
have been the
one that I had this problem with, but there were at least 2
dependencies
that I had a hard time figuring out, due to not having
specific enough
information.
I think that probably the easiest way to install Maia on
CentOS 5 is to
setup rpmforge as a yum repository on your machine. Then do
yum install
amavisd-new. This will automatically determine all of the
amavisd-new's
dependencies, and let you give the confirmation to install
them. After
that is installed, make a backup copy of
/etc/init.d/amavisd, then do
yum remove amavisd-new. That way you get all of the packages
that
amavisd-new needs installed, then remove only amavisd-new.
Then when you
start to setup maia on your system, you should have a lot
less
dependencies to work out. As for the copy of
/etc/init.d/amavisd, the
original should get removed when you remove amavisd-new. But
you can
just put your backup back in there and open it up and change
anything
that may not be specific to your maia installation. This
makes it easy
to start maia as a deamon at system boot (runlevel control),
as well as
control it using the "service" command.
FYI, I am currently having a problem with maia not removing
"Unconfirmed
SPAM" from that list after I confirm it. People on the
list have felt
that it is a database issue. I have yet to sort it out, but
think that I
probably will get it within the next 2 weeks (fitting it in
between
other things). I don't really think it could be related to
CentOS 5, but
at this point I don't really know. I have tried a couple
suggestions
given by other users of this mailing list, and so far it
hasn't worked.
You may want to find out whether other people on the list
are using
CentOS 5 problem free.
Regards,
--
Doug Mortensen
Impala Networks
Network Consultant
-----Original Message-----
From: maia-users-bounces renaissoft.com
[mailto:maia-users-bouncesrenaissoft.com] On Behalf
Of
maia-users-requestrenaissoft.com
Sent: Thursday, July 05, 2007 1:00 PM
To: maia-usersrenaissoft.com
Subject: Maia-users Digest, Vol 46, Issue 8
Send Maia-users mailing list submissions to
maia-usersrenaissoft.com
To subscribe or unsubscribe via the World Wide Web, visit
http://www.renaissoft.com/mailman/listinfo/maia-users
or, via email, send a message with subject or body 'help'
to
maia-users-requestrenaissoft.com
You can reach the person managing the list at
maia-users-ownerrenaissoft.com
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of Maia-users digest..."
Today's Topics:
1. Re: Using Maia for SMTP frontend to Exchange
(Michiel van den Berg)
2. Re: I cannot login as admin (David Morton)
------------------------------------------------------------
----------
Message: 1
Date: Thu, 5 Jul 2007 15:38:58 +0200
From: "Michiel van den Berg" <mvdbergmooy.nl>
Subject: Re: [Maia-users] Using Maia for SMTP frontend to
Exchange
To: "Jeffry Bilder" <electro93gmail.com>, "Maia"
<maia-usersrenaissoft.com>
Message-ID: <C4E6566E755921468A51F552F9502BFA8DEF6FSR0102.mooy.local>
Content-Type: text/plain; charset="us-ascii"
Maia only sees email addresses. To maia a distribution Group
is 'just
another' email address. So it will be a seperate user in
maia unless you
link it to another account.
________________________________
Van: maia-users-bouncesrenaissoft.com
[mailto:maia-users-bouncesrenaissoft.com] Namens
Jeffry Bilder
Verzonden: donderdag 5 juli 2007 15:36
Aan: Maia
Onderwerp: [Maia-users] Using Maia for SMTP frontend to
Exchange
I am planning on creating a Maia Mailguard server to act as
an SMTP
frontend to our environment. I was wondering how Maia
Mailgaurd handles
email coming into a distribution group. It it my
understanding that
Maia setups up an account per email it receives, but with a
distribution
group, it obviously is sent to multiple people. Is there a
way to have
this filtered at the user level for the group, rather than
filtering on
the group?
Also, does anyone have any installation guide using Centos.
I am
following the one for FC5, but would certainly like to know
the repos
needed to install some of the packages that live outside
rpmforge and
the default CentOS repositories.
Thank you!
- JB
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www.renaissoft.com/pipermail/maia
-users/attachments/20070705/ef3b
a3da/attachment-0001.html
------------------------------
Message: 2
Date: Thu, 5 Jul 2007 08:56:17 -0500
From: David Morton <mortondadgrmm.net>
Subject: Re: [Maia-users] I cannot login as admin
To: DUKE <mail2dukegmail.com>
Cc: maia-usersrenaissoft.com
Message-ID: <79DD68AE-4D48-49A6-939B-F6F14AE8C928dgrmm.net>
Content-Type: text/plain; charset=UTF-8; delsp=yes;
format=flowed
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jul 5, 2007, at 8:13 AM, DUKE wrote:
> >> Many thanks for your help. Now it starts, but
I cannot find "the
> key"
> >> which is mentioned in the docs, as the
super-admin menu. Where
> is it or
> >> why is it not here ?
>
> At first you have to build a keyfile:
>
> /var/spool/amavis/maia/scripts/generate-key.pl
> /var/
> spool/amavis/blowfish.key
>
> After that you must set the path to your keyfile in
maia.conf:
>
> ? Set $key_file line to read
>
$key_file="/var/spool/amavis/blowfish.key";
>
> At least you must spezifie the keyfile in your
admin-panel under
> systemconfiguration:
>
> /var/spool/amavis/blowfish.key
>
Or better yet, remove the key file and make sure both
entries are
empty. If you don't need the encryption, I wouldn't use
it. It
only prevents accidental reading of email by someone
directly in the
database... unless you have a way to make sure only the
webserver can
read the key for only the Maia application... Anyone that
can
access the key file can access the email. And even then,
the
superadmin can always turn on the option to read user's
email...
The encryption feature is there for specific client that
requested
for a specific situation; I really don't find very useful
and it
wastes CPU time.
OTOH, it would certainly be good to put Maia on an SSL host.
That
is accomplished outside of Maia, same as any other web
server
application.
David Morton
Maia Mailguard http://www.maiamailguard
.com
mortondadgrmm.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGjPiEUy30ODPkzl0RAuQjAKDCcdTWcrEuvw11pr6/rTWxeNGMywCe
Plxl
dNILvu4guD13BK2BxEk88Yg=
=F35k
-----END PGP SIGNATURE-----
------------------------------
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
End of Maia-users Digest, Vol 46, Issue 8
*****************************************
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
|
