At this time, correct The problems are the same as the '*nix' version
I have not ported the last snapshoot in win32 (in work) If anyone want the w32 binaries, i can sent them for test (i have to = finish the doc interfacing ecartis to xmail but setup easy) Francis -----Message d'origine----- De : David Byte [mailto:[EMAIL PROTECTED] Envoy=E9 : lundi 24 mars 2003 19:56 A : [EMAIL PROTECTED] Objet : [xmail] Re: XMail-WAI.NET features discussion Francis, How well is ecartis running on Win32 for you? I am looking for a good = list manager for my Win32 platform.. David Byte Owner, Byte Computer Services [EMAIL PROTECTED] ICQ# 50227527 918-230-2771 ----- Original Message ----- From: "CLEMENT Francis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 11:49 AM Subject: [xmail] Re: XMail-WAI.NET features discussion > > Hello Michal > > Coming back to xmail and using you WAI interface i will be happy to = =3D > help in > next WAI.NET > > For the SLIM replacement i have the solution : ecartis = (www.ecartis.org =3D > gpl, > written in C so fast ...) > I work on the win32 version that is currently running on my server = (not =3D > yet > fully commited to the main cvs project) > > Were can I find current work / discussion / dev mailing list/ on =3D > WAI.NET > project ? (sourceforge ...) > > Francis > > > > -----Message d'origine----- > De : Michal Altair Valasek [mailto:[EMAIL PROTECTED] > Envoy=3DE9 : mardi 11 mars 2003 20:05 > A : [EMAIL PROTECTED] > Objet : [xmail] XMail-WAI.NET features discussion > > > > Hello, > > as I announced before, I discontinued XMail-WAI and I'm planning new > version, which would be built on the .NET technology (mainly = ASP.NET). > > Currently, there is finished XMail-CTRL, universal module for =3D3D > communication > with XMail using it's CTRL protocol. > > I am sending you list of planned features, for discussion. Also, I am > accepting offers for help with implementation of features. The = project =3D > =3D3D > would > be distributed in Visual Studio .NET, used language would be VB.NET, = =3D > =3D3D > license > used would be GNU GPL. > > The main features of XMail-WAI would be in the .NET version too, with > exception of webmail (I'll discuss that later). Generally, it would = =3D3D > allow > distribution of privileges on server/domain/user levels. New features = =3D > =3D3D > would > include: > > - Possibility to limit account creation per domain, either by maximum = =3D > =3D3D > number > or by assigning the total amount of disk space. > - Better cooperation (with the new filtering system), which would = allow > things like autoresponders etc. to work. > - Speed optimization. Current version is too slow, due to = ctrlclnt.exe. =3D > =3D3D > It > can be better if rewritten to Shawn's eyeXMail. > > The features which would not be in the .NET version (although some of = =3D > =3D3D > them > are in the current version): > > - SLIM collaboration. I see that SLIM (my list manager) is ugly. Do = you =3D > =3D3D > know > about some list manager, which would run on Windows platform and = would, =3D > =3D3D > work > well with xmail, be free, preferably open-source, and not require > third-party software, such as Perl or Cygwin? If yes, I'll use it and = =3D > =3D3D > write > it's support to XMail-WAI.NET. If no, I'll consider writing of =3D > SLIM.NET, > which is long-term task. > - Multi-language interface. I wrote about this recently - writing > multi-language interface is a lot harder that the single-language = one. > Moreover, there is problem with further development, to maintain the > language data files. Therefore, the XMail-WAI.NET would be in English = =3D > =3D3D > only. > As it would use UNICODE, there should not be problem with non-ASCII > characters (but I cannot guarantee languages like chinese to work). > - Webmail. To write webmail is not a simple task and I don't have = time =3D > =3D3D > to do > it well. So, there would be no webmail in the first stage. > - Frozen messages management. Since XMail has option to simply = discard > undeliverable messages, I started to use it and don't bother with =3D > frozen > messages anymore. > - The strange things like pop3link etc. I am not using it, never was, = =3D > =3D3D > never > will, don't know how it's working. > > What I need: > - Your suggestions, what the XMail-WAI.NET should do. > - Your help with programming, mainly on the abstraction layer (see = =3D3D > lower), > but everything. > > Currently, the XMail-CTRL is working on the CTRL layer, so it returns = =3D > =3D3D > values > withount any abstraction as array of string. I want to write = something =3D > =3D3D > with > current codename XAL (XMail Abstraction Layer, compare with HAL - = =3D3D > Hardware > Abstraction Layer), which would convert Xmails CTRL output to .NET = =3D3D > native > formats, like datasets properly typed for databinding, etc. It's = =3D3D > relatively > simple work, but the main problem for me, because I don't have enough = =3D > =3D3D > time > :-( > > -- Michal A. Valasek > Altair Software Production > > *** New project: http://weblog.rider.cz *** > __________________________________________________________ > Censorship can't eliminate evil; it can only kill freedom. > E-mail: [EMAIL PROTECTED] * ICQ: 6160893 * GSM: +420-603-828493 > For list of all my web projects visit http://[EMAIL PROTECTED] > > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] > - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
