* This is the modus mailing list *
To those considering this I urge you to drop me a private mail.
As part of my work on Web Mail I plan on exposing some sections via Web
Services. This would therefore allow you to build custom pages for your
own systems that can tie back to the Modus Mail server.
The real reason for doing this is to allow a clustered solution for the
WL / BL stuff. At present a user hitting Web Admin on one server will
only have the WL / BL updates stored on that server and since we can't
share the MDB file across servers this would mean that only one server
can operate at a time. To cure this my plan is to create a series off
Web Services to allow users to update their WL / BL, and have the Web
Mail app call the web services on each server thereby replicating the
data. I'm still deciding on the exact format for sending into the Web
Service, in the sense off should this be done as a background process or
as a real-time process and keep the user occupied whilst it updates.
---
Erotic: Using a goose feather. Kinky: Using the whole goose.
(--------------------------------) {((((((
( Suneel Jhangiani ) /_ _ )
( Technical Director ) ( . . )
( Inter-Computer Technology Ltd. ) ( / )
(----------------------------------oOOo------------oOOo----)
( 40 James Street Tel: +44 (0) 20 7486 9601 )
( London W1U 1EU Fax: +44 (0) 7050 678 978 )
( United Kingdom Email: [EMAIL PROTECTED] )
( Website: http://www.inctech.com )
(----------------------------------------------------------)
-----Original Message-----
From: Lewis Watson [mailto:[EMAIL PROTECTED]
Sent: 07 November 2003 01:53
To: [EMAIL PROTECTED]
* This is the modus mailing list *
Hi Jim,
Thanks, I think I will probably do as you suggest and make the error
codes
user friendly myself. As soon as I can move some work out of the way I
am
going to add a php interface to interact with the extended DB, which
will
then get plugged into our account management site. I look forward to
removing some stuff out of the webmail system and dropping it into the
custom php system, which sounds like what you are going to be doing in
ASP.
Thanks,
Lewis
----- Original Message -----
From: "Jim Barstow" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 06, 2003 7:25 PM
Subject: [Modus] Error Message
> * This is the modus mailing list *
>
> I actually wrote several new error messages that I deciphered through
> trial and error.
>
> If you examine the asproot\login.asp file, you will see a section that
> looks like:
> ---snip---
> Case &H80040032
> Error = GetLabel("ErrorIMAP4NotSupported")
> Case &H800406BA OR &H800406BF
> Error = GetLabel("ErrorServerNotAvailable")
> Case Else
> Error = GetErrorLabel()
> ---snip---
>
> I simply added some new cases before the "Case Else" like
> ---snip---
> Case &H8004828A ''<this is an example, not real
> Error = "Invalid Password. Check your CAPS lock
> and try again"
> ---snip---
>
> When the error matching the case is returned, it will provide the user
> with whatever you set it to. I believe the actual errors they use are
> done with some include file with a function called GetLabel which
calls
> to a dictionary file to be multi-lingual.. You could always add new
> dictionary items and add new items to the GetLabel function.
>
>
> Jim Barstow
> Sr. Network Engineer
> Diversified Solutions and Services, Inc.
> 22645 Canal Road, Suite B
> Orange Beach, AL 36561
> 251.980.8968
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Lewis Watson
> Sent: Thursday, November 06, 2003 5:25 PM
> To: [EMAIL PROTECTED]
> Subject: [Modus] Error Message
>
>
> * This is the modus mailing list *
>
> Is there anywhere we can actually decipher the seemingly useless hex
> codes? Better yet - it would be nice for there to actually be a
logical
> error description as opposed to something like this... An internal
error
> occurred. Please try again later and contact your ISP if the problem
> persists. Description : Login failed. Code : &H800300CA
>
> First - An internal error makes a customer think that they did not do
> anything that would have caused the issue. Secondly. Smart error codes
> such as - invalid password or invalid username would help greatly.
Login
> failed is already apparent so it doesn't do much to help and the
> internal error just further complicates the issue. Some customers
think
> that means the server is broken rather than they entered Password as
> opposed to password. Thanks. Lewis
>
>
> ----- Original Message -----
> From: "Jon Benson" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, November 06, 2003 5:10 PM
> Subject: [Modus] Error Message
>
>
> * This is the modus mailing list *
>
> If you do setup a message similar to this please use "provider" rather
> then ISP. :)
>
>
> Jon Benson
> Mail/DNS/Linux Administrator
> OzHosting.com
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Friday, 7 November 2003 1:18 AM
> > To: [EMAIL PROTECTED]
> > Subject: [Modus] Error Message
> >
> >
> > * This is the modus mailing list *
> >
> > When a simple password error occurs at login the following error
> > appears, in red:
> >
> > An internal error occurred. Please try again later and contact your
> > ISP if the problem persists. Description : Login failed.
> > Code : &H800300CA
> >
> > While the statement may be true in a computer mentality, it is a bit
> > strong from a user point of view. It isn't an "internal error" in
the
>
> > program, it is either a "meathead" error on the part of the
customer,
> > or a typo, or his account is suspended for non payment.
> >
> > He probably should contact his ISP, etc., but could there be a less
> > strong message for this "external error" like "Your e-mail name or
> > password was not accepted by the server. Please try again and
contact
> > your ISP if the problem persists."?
> >
> > Cary Fitch
> >
> >
> > **
> > To unsubscribe, send an Email to: [EMAIL PROTECTED] with the
> > word "UNSUBSCRIBE" in the body or subject line.
> >
>
> **
> To unsubscribe, send an Email to: [EMAIL PROTECTED]
> with the word "UNSUBSCRIBE" in the body or subject line.
>
>
>
> **
> To unsubscribe, send an Email to: [EMAIL PROTECTED]
> with the word "UNSUBSCRIBE" in the body or subject line.
>
>
> **
> To unsubscribe, send an Email to: [EMAIL PROTECTED]
> with the word "UNSUBSCRIBE" in the body or subject line.
>
**
To unsubscribe, send an Email to: [EMAIL PROTECTED]
with the word "UNSUBSCRIBE" in the body or subject line.
**
To unsubscribe, send an Email to: [EMAIL PROTECTED]
with the word "UNSUBSCRIBE" in the body or subject line.
