List Info

Thread: Inheritance of quarantine-digest minutes settings




Inheritance of quarantine-digest minutes settings
user name
2006-05-09 01:10:45

Hello all, here is the situation.

I set the default user with a minute setting as to how often a digest should be received.
I set the default domain with the same setting.

I then create a new domain. The new domain by default has the same setting for minutes for quarantine digest time as the default domain. Example: Every 60 minutes, or whatever.

I then create a new user. For testing, this is all set low. I verify that there are spam emails in quarantine that exceed the settings that should trigger a digest. However, no digest is issued for the user I created, unless I then change the 0 for minutes to something else.

I am curious as to how to make the new users created default to having the same number of minutes on the digest settings as the default user.

Or is this not possible?

Thanks,

Steven Sorrells



Inheritance of quarantine-digest minutes settings
user name
2006-05-09 18:36:48
Steven Sorrells wrote:

> I set the default user with a minute setting as to how
often a digest
> should be received.
> I set the default domain with the same setting.
> 
> I then create a new domain. The new domain by default
has the same
> setting for minutes for quarantine digest time as the
default domain.
> Example: Every 60 minutes, or whatever.
> 
> I then create a new user. For testing, this is all set
low. I verify
> that there are spam emails in quarantine that exceed
the settings that
> should trigger a digest. However, no digest is issued
for the user I
> created, unless I then change the 0 for minutes to
something else.
> 
> I am curious as to how to make the new users created
default to having
> the same number of minutes on the digest settings as
the default user.
> 
> Or is this not possible?

This situation occurs because the digest interval setting is
a
"per-user" setting, rather than a
"per-address" setting.  The
per-address settings are stored in the policy table, and
those follow
the normal inheritance chain (system->domain->user),
but per-user
settings do not.  Per-user settings are assigned their
defaults solely
by the database (using the 'DEFAULT' clause defined in the
SQL schema).

The point you raise is valid, however; it may be desirable
to have
per-user settings follow the cascading inheritance model
that
per-address settings do--at least for the settings that can
be assigned
reasonable defaults (i.e. almost any column in the
maia_users table with
a 'DEFAULT' clause).  The 'spamtrap' column should
probably always
default to 'N' for safety reasons, but I don't see why
the other columns
with defaults shouldn't follow the inheritance model.

I've opened a ticket (#323
<htt
ps://secure.renaissoft.com/maia/ticket/323>) to
address this issue.

-- 
Robert LeBlanc <rjlrenaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamail
guard.com/>

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )