Here are some features that would be useful:

dbmail_users

Other than what is already available in the table, the following could be added for more functionality.

  • last_logout

Useful to check if the user is still online (i.e. if last login is greater than last logout, then the user must be online).

  • creation_date

Is it really necessary to explain why this would be useful :-)

  • expiry_date

There may be cases when you wish to grant a user a fixed window of usage, such as when the user is a student, or someone as a guest for a fixed duration.

  • enabled

Shows whether or not the user account is enabled. If not enabled then the user will not be able to login.

Why is all this necessary? In almost all settings, Administrators need more usable information, and we should let them have some of that here :-)

dbmail-auto_replies

Other than what is already available in the table, the following could be added for more functionality.

Adding these fields (and functionality) would be most helpful so that users could customize their auto replies to their customers/friends etc.

  • description

This is a short desription, or a name for this auto-reply entry.

  • enabled

A boolean field, True by default. To indicate whether or not this is active. This saves the user from having to re-enter the same stuff again when needed.

  • sender_address

So that, this message is sent only if the sender matches. If blank, it applies to all. Some sort of wildcard capability might be useful here to handle domains etc.

  • weekday_number

The weekday_number field represent weekday numbers for which the auto reply is active. If zero, it means this field is ignored by DBMail.

  • start_time
  • end_time

The start_time and end_time fields represent times between which the auto reply is active. If zero, it means this field is ignored by DBMail.

  • start_date
  • end_date

The start_date and end_date fields represent dates between which the auto reply is active. If zero, it means this field is ignored by DBMail.

  • reply_body

When reply_body is blank it means that no auto reply should be generated –this is helpful in the case of mail lists.

Why is all this necessary?

Users working part time (i.e. available for certain days of the week or times of day), or people going on holiday or business trips can better handle the correspondence addressed to them. This, in return, will not only help them avoid a few embarrassing situations, but also may help them get out of some legal liabilities too.

dbmail-auto_notifications

Other than what is already available in the table, the following could be added for more functionality.

Ideally, there should be one entry for each sender and notification address pair (even for those containing wildcards) in order to make it uncomplicated for the users.

  • description

This is a short desription, or a name for this auto-notification entry.

  • enabled

A boolean field, True by default. To indicate whether or not this is active. This saves the user from having to reenter the same stuff again when needed.

  • sender_address

This notification will be activated if a message comes from a particular sender. This is most useful in the case if the sender is an important one –your beloved one or a high account customer which may or may not mean the same :-) Ideally it should support domains so that the user could handle a whole cutomerbase (a company etc.).

  • weekday_number

These fields represent weekday numbers for which the auto notification is active. If zero, it means this field is ignored by DBMail.

  • start_time
  • end_time

These fields represent times between which the auto notification is active. If zero, it means this field is ignored by DBMail.

  • start_date
  • end_date

These fields represent dates between which the auto notification is active. If zero, it means this field is ignored by DBMail.

Why is all this necessary?

Having different workdays for notifications enables the user to send a notification to different accounts depending on the weekday. This is useful when there are different people working part time part of the week, or the user has personal accounts that he/she may be using during holidays etc.

A General Note for dates, times and weekday numbers

While it is obviously possible that a user may enter values into weekday_number, start_time, end_time, start_date, end_date fields that may make that particular constrains impossible to execute, we are not (at this stage) concerned with whether the combination is possible or not. Later, much much later, after this functionality added into DBMail and it has matured well enough, further code can be added to tell the user if his/her constarints are meaningful or not. Or we can go a little further and show the user a graphical screen displaying what action will be taken and when. Pipe dream :-)

 
auto_reply.txt · Last modified: 2011/07/06 13:15 by paul
 
DBMail is developed by Paul J Stevens together with developers world-wide