Mine started working correctly right away.. I am not happy guy.. LOL...
Now let me see.. what is the next task.. oh yea... an option to allow users
through the web to read / write / reply / view email.. ok...
where oh where can I find some free good code.. oh where oh where can it be
located?

I am sick.. or it is 5:00am in the morning.. gosh.. I need to find a life
here on this earth..
smile..

Later

Ed

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Shawn Anderson" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, October 02, 2001 8:02 PM
Subject: Re: [ANNONCE] eyeXMail v0.1.6 Released


> Thank you very much for updating your com object.  The update was
painless,
> and seems to improve reliability greatly!
>
>
> ----- Original Message -----
> From: "Shawn Anderson" <[EMAIL PROTECTED]>
> To: "'Shawn Anderson'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
> Sent: Thursday, September 27, 2001 7:32 PM
> Subject: RE: [ANNONCE] eyeXMail v0.1.6 Released
>
>
> > You are all probably wonder where you can get this new version :)
> >
> > http://xmail.eye-catcher.com
> >
> > Or
> > http://xmail.eye-catcher.com/products/eyeXMail/
> >
> > Shawn
> >
> > -----Original Message-----
> > From: Shawn Anderson [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, September 27, 2001 10:27 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [ANNONCE] eyeXMail v0.1.6 Released
> >
> >
> > Here is a much needed update to the eyeXMail COM object. It features the
> > following:
> >
> > - Rewrote the Socket library
> > - Fixed a but in receiving HTML encoded email via the POP3 component
> > - Added a TimeOut Property to the CtrlClnt object to specify how long a
> > wait should occur on new data
> >
> > Now, keep in mind that this is still in the early stages.
> >
> > Shawn
> >
> > -----Original Message-----
> > From: Shawn Anderson [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, September 27, 2001 7:37 PM
> > To: [EMAIL PROTECTED]
> > Subject: PROBLEM WITH EYEXMAIL
> >
> >
> > Ok guys, I get the message :)
> >
> > I will have a new version of eyeXMail up by tomorrow. I didn't realize
> > it was this bad or that this many people were using it, otherwise I
> > would have had a newer version out sooner. Most of the underlying
> > problems are with the socket library I went with, so right now I am
> > switching it out for one that _Digitalpeer recommended.
> >
> > Shawn
> >
> > -----Original Message-----
> > From: Edinilson J. Santos [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, September 27, 2001 7:29 PM
> > To: Orion Productions; [EMAIL PROTECTED]
> > Subject: Re: WAI version 1.0.0 - PROBLEM WITH EYEXMAIL
> >
> >
> > eyeXMail has a problem mainly when you are trying to list users. For
> > some others things it works relatively well.
> >
> > Because of this, we are using the following to list users (ASP):
> >
> > domain = "domain.com"
> > Set Executor = Server.CreateObject("ASPExec.Execute")
> > Executor.Application = "D:\mailroot\bin\ctrlclnt.exe"
> > Executor.Parameters = "-s XMAIL-IP -n 6017 -u USER -p PASSWORD userlist
> > " & domain strResult = Executor.ExecuteDosApp Set Executor = Nothing
> >
> > emails = split(vbCRLF & strResult, vbCRLF)
> > xemails = UBound(emails)-1
> > emailsnow = 0
> >
> > for j=1 to xemails
> >  partes = split(chr(9) & emails(j),chr(9))
> >  if partes(4) = """U""" Then
> >   emails(j) = replace(partes(2),chr(34),"") & "#" &
> > replace(partes(3),chr(34),"")
> >   emailsnow = emailsnow + 1
> >  else
> >   emails(j) = ""
> >  end if
> > next
> > if emailsnow <= 0 Then
> >   response.write "No emails"
> > Else
> >  for j=1 to xemails
> >   if emails(j) <> "" Then
> >    pos = Instr(emails(j),"#")
> >    email = left(emails(j),pos-1)
> >    passw  = mid(emails(j),pos+1)
> >
> >    'put your code here
> > end if
> > next
> >
> >
> > ps: download aspexecute here:
> > http://www.serverobjects.com/comp/Aspexec.zip
> >
> > Edinilson
> > ---------------------------------------------------------
> > ATINET-Afiliado UOL de Atibaia
> > Rua Francisco R. Santos, 54 sala 3
> > ATIBAIA/SP Cep: 12940-250
> > Tel Voz: (0xx11) 4412-0876
> > http://www.atinet.com.br
> >
> >
> > ----- Original Message -----
> > From: "Orion Productions" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, September 27, 2001 7:43 PM
> > Subject: Re: WAI version 1.0.0 - PROBLEM WITH EYEXMAIL
> >
> >
> > The problem is caused by the eyeXMail component, which seems to be quite
> > buggy. This is such a pity, because we need it so much for ASP / COM /
> > .NET development.
> >
> > Does anyone have an alternative for eyeXMail ?
> > The VB code for the XMail administrator works flawlessly, so if that
> > code could be adapted and incorporated into a COM component, we would at
> > last be able to write a decent web interface!
> >
> > I was already working on a very nice and complete web-based management
> > system for XMail, but I'm not motivated anymore to finish it because the
> > eyeXMail component doesn't behave as expected. :-( One of the things
> > that is very annoying, is that the result it returns is indeed
> > unpredictable: one time it works, the next time it doesn't or doesn't
> > return the complete set of data.
> >
> > So...  VB / COM / .NET developers.... WAKE UP! :-)  I'm the first
> > willing to spend my time in developing the ultimate web-based interface
> > for the great mailserver that XMail is, but first we need a solid
> > foundation to build on!
> >
> > I really hope that this e-mail will motivate people to tackle this
> > serious problem.
> >
> >
> > ----- Original Message -----
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, September 27, 2001 7:33 PM
> > Subject: Re: WAI version 1.0.0
> >
> >
> > > Yes - we too get this same error on multiple installs.  The WAI is
> > terrific,
> > > but there do seems to be some timing issues.  Normally, thru retrying,
> >
> > > you can eventually get it to work.
> > >
> > > It seems that often the function is accomplished, but the WAI doesn't
> > > find out about it.
> > >
> > > ----- Original Message -----
> > > From: "Webmaster" <[EMAIL PROTECTED]>
> > > To: "Davide Libenzi" <[EMAIL PROTECTED]>; "David Bitton"
> > > <[EMAIL PROTECTED]>
> > > Cc: <[EMAIL PROTECTED]>
> > > Sent: Thursday, September 27, 2001 3:31 AM
> > > Subject: WAI version 1.0.0
> > >
> > >
> > > > When running the web administration Xmail app.  this is the error I
> > > > am getting now. I am just creating new users and new domains.  The
> > > > program worked GREAT
> > up
> > > > until around 20 objects added into the system.. and now this error.
> >
> > > > I
> > > even
> > > > deleted all users and all domains... and added 1 domain and 1 user
> > > > and
> > > that
> > > > worked ok with no errors.. I tested and tested it with under 20
> > > > objects added to Xmail and it worked great.. then after a couple
> > > > days.. I
> > started
> > > > adding more objects (domains and users) and wam it started erroring
> > > > out again.. It is like it is running off a buffer that has so much
> > > > space and everything over that buffer errors out... Can someone
> > > > please help with a solution? What can I do to get this fixed? Thanks
> >
> > > > in advance...
> > > >
> > > > This app is from:
> > >
> > > ----------------------------------------------------------------------
> > > ----
> > > --
> > > > ----
> > > > WAI version 1.0.0
> > > > (c) Michal A. Valasek - Altair Software Production, 2001 This is the
> >
> > > > free software distributed under the terms of GNU General
> > > Public
> > > > License.
> > > > For more information about GNU and GPL, visit the Free Software
> > Fundation
> > > > web site
> > >
> > > ----------------------------------------------------------------------
> > > ----
> > > --
> > > > ----
> > > >
> > > > Microsoft VBScript runtime error '800a0009'
> > > >
> > > > Subscript out of range: '[number: 0]'
> > > >
> > > > /xmadmin/system/main.asp, line 238
> > > >
> > > >
> > >
> > >
> >
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.281 / Virus Database: 149 - Release Date: 18/09/2001
> >
> >
> >
> >
>
>

Reply via email to