Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread DZ-Jay
So, rather than a new protocol, you have created a new e-mail server 
and client system which communicates in its own proprietary binary 
format?

dZ.

On Feb 6, 2008, at 18:50, David A. G. wrote:

 Dear friends,

 I have developed a complete and very improved e-mail protocol, highly 
 immune
 to the SPAM, with data encryption and compression, with sender ID
 validation, etc. BUT not compatible with the standard email (SMTP).

-- 
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread Fastream Technologies
I wonder why he chose a binary format instead of text as no popular/common
protocol is designed that way (i.e. HTTP, FTP, IMAP--all telnet based)!

Regards,

SZ


On 2/7/08, DZ-Jay [EMAIL PROTECTED] wrote:

 So, rather than a new protocol, you have created a new e-mail server
 and client system which communicates in its own proprietary binary
 format?

dZ.

 On Feb 6, 2008, at 18:50, David A. G. wrote:

  Dear friends,
 
  I have developed a complete and very improved e-mail protocol, highly
  immune
  to the SPAM, with data encryption and compression, with sender ID
  validation, etc. BUT not compatible with the standard email (SMTP).

 --
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html

 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread Dave Baxter
I suspect that's half the point.  Only like equipped users can
communicate.  Guess there could be a use in the financial or military
markets, or other intentionaly closed environments...   There again,
I'd also guess they have such systems implemented already?

Servers, nothing to stop you delivering directly, as many corporate
systems do already, ours included, so long as you know the IP or domain
address of course...   I suspect for the above type of users, regular
POP/SMTP/IMAP etc incompatability would not be a problem!

Have to say though, spam is primeraly user driven from personal
experience, from website form filling and so on.   And what happens when
a spammer gets hold of one of these secure mailer clients etc.

Wonder why PGP or Open GPG is not as popular as it could be?  There are
plugins that integrate OK with the likes of Outlook (ugh!)
Thunderbird, Pegasus etc...   Ah, of course, the powers that be, like to
watch what goes on   Silly me...

Cheers..   I'll crawl back under my rock, it's a bit too bright out
here...

Dave B.
 

 -Original Message-
 From: DZ-Jay [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 07, 2008 11:56 AM
 To: ICS support mailing
 Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)
 
 Hello:
   Also, if it is not compatible with SMTP, how does 
 anybody outside your own mail server network get it?  And if 
 it does communicate with external SMTP servers in order to 
 inter-operate with other networks (otherwise, what's the 
 point in sending yourself e-mail?) then it *is* susceptible 
 to SPAM and abuse.
 
   dZ.
 -- 
   DZ-Jay [TeamICS]
   http://www.overbyte.be/eng/overbyte/teamics.html
 
 
 
This mail has been scanned by Palmer Cook Computer Services Limited.  
www.palmercook.co.uk
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread Fastream Technologies
MP3 is not a protocol but a file format. You are right that TCP/UDP uses
binary headers but we are talking about a high level protocol, which if
popularized, will be coded by third party coders according to RFC and this I
believe will not be so trivial for the binary case! ICS has codes for
SMTP/POP/HTTP/FTP (all text) but not for TCP. Wasn't there a need for low
level stacks? Think again--we have all lived through syn-attacks and
ping-o-deaths. Keep in mind that Microsoft recoded the entire TCP/IP stack
in Windows 2008 Server just for this. But since it was something hard to do,
through the past decade, Microsoft was being waited to step forward.

ALso, for adoption, large enterprises want to test every protocol they
use--when they are new. Testing a binary protocol for them would also be
hard and this might hammer adoption globally. We have customers who study
and stress test for 29 days to understand how our caching and then decide to
buy at the end of the trial period!

Regards,

SZ


On 2/7/08, Hoby Smith [EMAIL PROTECTED] wrote:

 Actually, IMNSHO (In My Not So Humble Opinion), binary protocols make much
 smarter sense for binary machines.  Even with the discrepancies of the
 various flavors of binary formats (big vs little endian, etc), it is WAY
 MORE EFFICIENT for binary machines to use binary protocols than to
 interpret
 human readable formats (text, xml, etc) into binary formats so that they
 may
 be processed appropriately by processor and related software.  Only humans
 think in the context of textual formats; computers do not.  The overhead
 associated with textual translation is a horrible side effect of the web
 phenomenon.

 Actually, the statement no popular/common protocol is designed that way
 is
 horribly inaccurate.  True, the W3C has an inherent conflict of interest
 in
 driving the pervasive use of textual formats.  However, there are tens of
 thousands of binary formats that predate the stupid web stack and continue
 to emerge daily.  For example, consider TCP, which is a binary protocol
 and
 the actual core technology upon which this mail list and ICS is
 founded.  I
 would consider TCP to be popular and common.  It is only the layer 7
 centric, web focused protocols that are textual in nature.  Unfortunately,
 the web has set computing back about 20 years, the effects of which has
 only
 recently begun to be realized in all of its awful consequences (slow
 cumbersome interfaces, security issues galore, etc).

 Quite some time back, before clients of various types were ubiquitous, it
 was necessary for servers to understand human readable formats (ftp, etc).
 That need has long been outlived and the perspective that drives it is
 seriously antiquated.  With very few exceptions, the data needs of server
 systems are way too complex to be constrained by human readable formats.

 For example, are you going to type the binary values for a MIME image that
 you want to embed in an email?  Try doing that via a textual SMTP
 interface.
 The whole need of MIME was to overcome the stupid limitations of a textual
 email standard.  Let's see, how do I represent binary data in a textual
 format.  Yeah, that makes perfect sense.  In a web world, I guess it does.
 How about a word document?  Do you want a format that you have to type the
 font details manually, like HTML?  NO, you use a word processor that does
 all that for you and then stores it in format that the system understands.
 How about audio?  Do you want a media stream protocol that is human
 readable? Such a media protocol would be too slow be feasible.  MP3 is a
 BINARY solution that attempts to answer the audio data issues.  Everyone
 uses a piece of software that understands MP3.  I would consider MP3 to be
 common and popular, even though it is BINARY.

 For computing needs, the future reality is surely a return to strong
 binary
 representations that can be interpreted into forms that humans can
 understand as needed, or can be handled by clients as necessary.


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Fastream Technologies
 Sent: Thursday, February 07, 2008 5:43 AM
 To: ICS support mailing
 Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)

 I wonder why he chose a binary format instead of text as no popular/common
 protocol is designed that way (i.e. HTTP, FTP, IMAP--all telnet based)!

 Regards,

 SZ


 On 2/7/08, DZ-Jay [EMAIL PROTECTED] wrote:
 
  So, rather than a new protocol, you have created a new e-mail server
  and client system which communicates in its own proprietary binary
  format?
 
 dZ.
 
  On Feb 6, 2008, at 18:50, David A. G. wrote:
 
   Dear friends,
  
   I have developed a complete and very improved e-mail protocol, highly
   immune
   to the SPAM, with data encryption and compression, with sender ID
   validation, etc. BUT not compatible with the standard email (SMTP).
 
  --
 DZ-Jay [TeamICS]
 http

Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread Francois PIETTE
 ICS has codes for
 SMTP/POP/HTTP/FTP (all text) but not for TCP. 

I'm not sure about what you mean. 
ICS as TWSocket and TWSocketServer for TCP.

Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread Hoby Smith
Hello SZ...

Astute observation about formats vs. protocols.  However, I don't think
that David has done away with TCP/IP, the transport protocol used for
sending the email with.  In a sense, all layer 7 solutions can really be
considered a format in a TCP payload.  So, the distinction really blurs
there to some degree.

Regardless, the core issue is still relevant, namely that binary systems
think in a binary context. If a driving constraint is efficiency and
minimalist approaches, binary formats and protocols are mandated.
Regardless of how you slice it, binary makes better sense FROM THE SYSTEMS
perspective.  

As for the TCP hacking attacks you reference, they PALE in comparison to the
security flaws that are revealed and exploited on a daily basis that stem
from the inherent lack of security in the original web protocol designs.
Additionally, those TCP hacks provide no security related exposure, in the
sense of data compromise, but rather in systems resiliency.  Syn-attacks
will not get to your corporate data.  XSS attacks, on the other hand, can
provide a wonderful mechanism for compromising your systems in a number of
ways.  Additionally, SSL dependence is at the root of almost ALL BAD web
thinking.  However, everyone still thinks the Emperor looks great and
somehow it's just going to work itself out.  If the web protocols had
envisioned ANY CONCEPT of user and state, instead of the stupid session-less
paradigm it enforces, as well as in-transit security, there would be no need
for the web stack paradigm to exist in its currently flawed state.

Regarding testing new protocols, new standards emerge EVERY DAY.  In the
xml related world (given this is a format not a protocol), they emerge every
minute.  Considering that numerous security hacks attack FORMAT weaknesses
in the OS and related software (image files, etc), this issue still applies.
Scores of them pass through corporate enterprises without testing every day.
Additionally, anything constructed as a layer 7 solution is going to pass
through the internet architecture just fine, barring various packet
inspector rules, etc.  Again, I don't think David has invented a new TCP
stack, but rather just different info being passed through TCP.  

Regards...

Hoby

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Fastream Technologies
Sent: Thursday, February 07, 2008 10:35 AM
To: ICS support mailing
Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)

MP3 is not a protocol but a file format. You are right that TCP/UDP uses
binary headers but we are talking about a high level protocol, which if
popularized, will be coded by third party coders according to RFC and this I
believe will not be so trivial for the binary case! ICS has codes for
SMTP/POP/HTTP/FTP (all text) but not for TCP. Wasn't there a need for low
level stacks? Think again--we have all lived through syn-attacks and
ping-o-deaths. Keep in mind that Microsoft recoded the entire TCP/IP stack
in Windows 2008 Server just for this. But since it was something hard to do,
through the past decade, Microsoft was being waited to step forward.

ALso, for adoption, large enterprises want to test every protocol they
use--when they are new. Testing a binary protocol for them would also be
hard and this might hammer adoption globally. We have customers who study
and stress test for 29 days to understand how our caching and then decide to
buy at the end of the trial period!

Regards,

SZ


On 2/7/08, Hoby Smith [EMAIL PROTECTED] wrote:

 Actually, IMNSHO (In My Not So Humble Opinion), binary protocols make much
 smarter sense for binary machines.  Even with the discrepancies of the
 various flavors of binary formats (big vs little endian, etc), it is WAY
 MORE EFFICIENT for binary machines to use binary protocols than to
 interpret
 human readable formats (text, xml, etc) into binary formats so that they
 may
 be processed appropriately by processor and related software.  Only humans
 think in the context of textual formats; computers do not.  The overhead
 associated with textual translation is a horrible side effect of the web
 phenomenon.

 Actually, the statement no popular/common protocol is designed that way
 is
 horribly inaccurate.  True, the W3C has an inherent conflict of interest
 in
 driving the pervasive use of textual formats.  However, there are tens of
 thousands of binary formats that predate the stupid web stack and continue
 to emerge daily.  For example, consider TCP, which is a binary protocol
 and
 the actual core technology upon which this mail list and ICS is
 founded.  I
 would consider TCP to be popular and common.  It is only the layer 7
 centric, web focused protocols that are textual in nature.  Unfortunately,
 the web has set computing back about 20 years, the effects of which has
 only
 recently begun to be realized in all of its awful consequences (slow
 cumbersome interfaces, security issues galore, etc).

 Quite

Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread David A. G.
Answering to all...

DZ-Jay:
 So, rather than a new protocol, you have created a new e-mail server and 
 client system which communicates in its own proprietary binary format?
That is correct, but according the definition of protocol and thinking about 
my system runs directly over TCP/IP...

DZ-Jay:
 Also, if it is not compatible with SMTP, how does anybody outside your 
 own mail server network get it?
For the moment I have the only server, but this system works in the same way 
than the standard e-mail ... using Domains and MX-DNS queries.

Fastream Technologies:
 I wonder why he chose a binary format instead of text as no popular/common 
 protocol is designed that way.
The reason is simple, using a binary protocol ensures a minimum consumption 
of bytes through the net. And the most important reason, my protocol uses 
only 4 steps to send or receive an e-mail:
1- client: connection and authentication
2- server: response
3- client: work identification and e-mail transmision (in a single block!)
4- server: final response (CRC validation made!)
5- client: request to close connection
This kind of protocol ensures a very fast interaction client/server and 
enables a native data compressiĆ³n.

Darin McGee
 So you lock out 99.9% of the email - no wonder it blocks spam.
hehehe ... I added many features that ensures a real spam blocking, not 
only taking hand on the incompatibility, please read my webpage 
www.hidens.com.ar
I meaning that all known spamming methods are blocked or minimized (from 
address thefts to mail pumps), except a user sending a real e-mail to 
another one (obviously). Well you can just denounce that user to the 
webmaster...

Darin McGee
 That's what I love about standards, everybody has one :)
Yes, the only problem here is how to popularize it... hehehe

Thanks for your time to every body, you are invited to use it...

David Jorge Aguirre Grazio
www.djag.com.ar



- Original Message - 
From: Dave Baxter [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Thursday, 07 February, 2008 10:29 AM
Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)


I suspect that's half the point.  Only like equipped users can
 communicate.  Guess there could be a use in the financial or military
 markets, or other intentionaly closed environments...   There again,
 I'd also guess they have such systems implemented already?

 Servers, nothing to stop you delivering directly, as many corporate
 systems do already, ours included, so long as you know the IP or domain
 address of course...   I suspect for the above type of users, regular
 POP/SMTP/IMAP etc incompatability would not be a problem!

 Have to say though, spam is primeraly user driven from personal
 experience, from website form filling and so on.   And what happens when
 a spammer gets hold of one of these secure mailer clients etc.

 Wonder why PGP or Open GPG is not as popular as it could be?  There are
 plugins that integrate OK with the likes of Outlook (ugh!)
 Thunderbird, Pegasus etc...   Ah, of course, the powers that be, like to
 watch what goes on   Silly me...

 Cheers..   I'll crawl back under my rock, it's a bit too bright out
 here...

 Dave B.


 -Original Message-
 From: DZ-Jay [mailto:[EMAIL PROTECTED]
 Sent: Thursday, February 07, 2008 11:56 AM
 To: ICS support mailing
 Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)

 Hello:
 Also, if it is not compatible with SMTP, how does
 anybody outside your own mail server network get it?  And if
 it does communicate with external SMTP servers in order to
 inter-operate with other networks (otherwise, what's the
 point in sending yourself e-mail?) then it *is* susceptible
 to SPAM and abuse.

 dZ.
 -- 
 DZ-Jay [TeamICS]
 http://www.overbyte.be/eng/overbyte/teamics.html



 This mail has been scanned by Palmer Cook Computer Services Limited. 
 www.palmercook.co.uk
 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be
 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread Hoby Smith
Actually, IMNSHO (In My Not So Humble Opinion), binary protocols make much
smarter sense for binary machines.  Even with the discrepancies of the
various flavors of binary formats (big vs little endian, etc), it is WAY
MORE EFFICIENT for binary machines to use binary protocols than to interpret
human readable formats (text, xml, etc) into binary formats so that they may
be processed appropriately by processor and related software.  Only humans
think in the context of textual formats; computers do not.  The overhead
associated with textual translation is a horrible side effect of the web
phenomenon.

Actually, the statement no popular/common protocol is designed that way is
horribly inaccurate.  True, the W3C has an inherent conflict of interest in
driving the pervasive use of textual formats.  However, there are tens of
thousands of binary formats that predate the stupid web stack and continue
to emerge daily.  For example, consider TCP, which is a binary protocol and
the actual core technology upon which this mail list and ICS is founded.  I
would consider TCP to be popular and common.  It is only the layer 7
centric, web focused protocols that are textual in nature.  Unfortunately,
the web has set computing back about 20 years, the effects of which has only
recently begun to be realized in all of its awful consequences (slow
cumbersome interfaces, security issues galore, etc).

Quite some time back, before clients of various types were ubiquitous, it
was necessary for servers to understand human readable formats (ftp, etc).
That need has long been outlived and the perspective that drives it is
seriously antiquated.  With very few exceptions, the data needs of server
systems are way too complex to be constrained by human readable formats.  

For example, are you going to type the binary values for a MIME image that
you want to embed in an email?  Try doing that via a textual SMTP interface.
The whole need of MIME was to overcome the stupid limitations of a textual
email standard.  Let's see, how do I represent binary data in a textual
format.  Yeah, that makes perfect sense.  In a web world, I guess it does.
How about a word document?  Do you want a format that you have to type the
font details manually, like HTML?  NO, you use a word processor that does
all that for you and then stores it in format that the system understands.
How about audio?  Do you want a media stream protocol that is human
readable? Such a media protocol would be too slow be feasible.  MP3 is a
BINARY solution that attempts to answer the audio data issues.  Everyone
uses a piece of software that understands MP3.  I would consider MP3 to be
common and popular, even though it is BINARY.

For computing needs, the future reality is surely a return to strong binary
representations that can be interpreted into forms that humans can
understand as needed, or can be handled by clients as necessary.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Fastream Technologies
Sent: Thursday, February 07, 2008 5:43 AM
To: ICS support mailing
Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)

I wonder why he chose a binary format instead of text as no popular/common
protocol is designed that way (i.e. HTTP, FTP, IMAP--all telnet based)!

Regards,

SZ


On 2/7/08, DZ-Jay [EMAIL PROTECTED] wrote:

 So, rather than a new protocol, you have created a new e-mail server
 and client system which communicates in its own proprietary binary
 format?

dZ.

 On Feb 6, 2008, at 18:50, David A. G. wrote:

  Dear friends,
 
  I have developed a complete and very improved e-mail protocol, highly
  immune
  to the SPAM, with data encryption and compression, with sender ID
  validation, etc. BUT not compatible with the standard email (SMTP).

 --
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html

 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread Hoby Smith
Go David.   

As a disclaimer, I admit that I am seriously biased, since I am probably the
only nerd on the planet that thinks Tim Berners Lee should be shot for
giving us the stupid web trash we have now, or perhaps it is the large
corporate interests to blame that determined for their own personal gain
that the web was should be the ULTIMATE vehicle for software facilitation.
Either way, I plainly admit my anti-web bias.

Nonetheless, the ONLY solution for overcoming the massive amounts of
oversights in various areas (security, scalability, state management, etc)
in the current protocols (SMTP, FTP, HTTP, etc) is by RETHINKING and
REPLACING them with something that inherently thinks smarter. 

Kudos to David for thinking OUT of the box to ANY DEGREE.  Innovation should
be supported, not rebuffed for its lack of status quo complicity.

Ok, I am deflating my personal soap box now... You may return to your
regularly scheduled programming...  :)

Hoby

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of David A. G.
Sent: Thursday, February 07, 2008 10:13 AM
To: ICS support mailing
Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)

Answering to all...

DZ-Jay:
 So, rather than a new protocol, you have created a new e-mail server and

 client system which communicates in its own proprietary binary format?
That is correct, but according the definition of protocol and thinking about

my system runs directly over TCP/IP...

DZ-Jay:
 Also, if it is not compatible with SMTP, how does anybody outside your 
 own mail server network get it?
For the moment I have the only server, but this system works in the same way

than the standard e-mail ... using Domains and MX-DNS queries.

Fastream Technologies:
 I wonder why he chose a binary format instead of text as no popular/common

 protocol is designed that way.
The reason is simple, using a binary protocol ensures a minimum consumption

of bytes through the net. And the most important reason, my protocol uses 
only 4 steps to send or receive an e-mail:
1- client: connection and authentication
2- server: response
3- client: work identification and e-mail transmision (in a single block!)
4- server: final response (CRC validation made!)
5- client: request to close connection
This kind of protocol ensures a very fast interaction client/server and 
enables a native data compressiĆ³n.

Darin McGee
 So you lock out 99.9% of the email - no wonder it blocks spam.
hehehe ... I added many features that ensures a real spam blocking, not 
only taking hand on the incompatibility, please read my webpage 
www.hidens.com.ar
I meaning that all known spamming methods are blocked or minimized (from 
address thefts to mail pumps), except a user sending a real e-mail to 
another one (obviously). Well you can just denounce that user to the 
webmaster...

Darin McGee
 That's what I love about standards, everybody has one :)
Yes, the only problem here is how to popularize it... hehehe

Thanks for your time to every body, you are invited to use it...

David Jorge Aguirre Grazio
www.djag.com.ar



- Original Message - 
From: Dave Baxter [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Thursday, 07 February, 2008 10:29 AM
Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)


I suspect that's half the point.  Only like equipped users can
 communicate.  Guess there could be a use in the financial or military
 markets, or other intentionaly closed environments...   There again,
 I'd also guess they have such systems implemented already?

 Servers, nothing to stop you delivering directly, as many corporate
 systems do already, ours included, so long as you know the IP or domain
 address of course...   I suspect for the above type of users, regular
 POP/SMTP/IMAP etc incompatability would not be a problem!

 Have to say though, spam is primeraly user driven from personal
 experience, from website form filling and so on.   And what happens when
 a spammer gets hold of one of these secure mailer clients etc.

 Wonder why PGP or Open GPG is not as popular as it could be?  There are
 plugins that integrate OK with the likes of Outlook (ugh!)
 Thunderbird, Pegasus etc...   Ah, of course, the powers that be, like to
 watch what goes on   Silly me...

 Cheers..   I'll crawl back under my rock, it's a bit too bright out
 here...

 Dave B.


 -Original Message-
 From: DZ-Jay [mailto:[EMAIL PROTECTED]
 Sent: Thursday, February 07, 2008 11:56 AM
 To: ICS support mailing
 Subject: Re: [twsocket] AN: New e-mail protocol (spam free and more!)

 Hello:
 Also, if it is not compatible with SMTP, how does
 anybody outside your own mail server network get it?  And if
 it does communicate with external SMTP servers in order to
 inter-operate with other networks (otherwise, what's the
 point in sending yourself e-mail?) then it *is* susceptible
 to SPAM and abuse.

 dZ.
 -- 
 DZ-Jay [TeamICS]
 http

Re: [twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-07 Thread Fastream Technologies
I mean the TCP stack itself. The bugs in first Trumpet and then MS Winsock
caused many problems throughout the years since Internet flourished. (AFAIK,
since 1993-4). All the coders chose to implement top-level protocols (like
you) and it was left to MS for doing the complex TCP job...

Regards,

SZ

On 2/7/08, Francois PIETTE [EMAIL PROTECTED] wrote:

  ICS has codes for
  SMTP/POP/HTTP/FTP (all text) but not for TCP.

 I'm not sure about what you mean.
 ICS as TWSocket and TWSocketServer for TCP.

 Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
 --
 [EMAIL PROTECTED]
 The author of the freeware multi-tier middleware MidWare
 The author of the freeware Internet Component Suite (ICS)
 http://www.overbyte.be

 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


[twsocket] AN: New e-mail protocol (spam free and more!)

2008-02-06 Thread David A. G.
Dear friends,

I have developed a complete and very improved e-mail protocol, highly immune 
to the SPAM, with data encryption and compression, with sender ID 
validation, etc. BUT not compatible with the standard email (SMTP).

Let me introduce you to High Density Mail Protocol (HDMP):

This very improved e-mail protocol takes advantage of the technology 
available in the 21' century and offers benefits far superior in contrast 
with the actual system based on technology and security standards now 
obsolete (SMTP was created in 1982).

Some features:

- Data compression (transfers up to 10 times faster than the actual e-mail 
system).
- Data encryption (protects the content using encryption methods, like AES, 
3DES, etc).
- Minimum handshaking, only 4 steps are needed to send or receive an 
e-mail.
- Immune to the SPAM (for more info visit our website).
- Persistent Digital Signature (PDS)(FREE). Can be used to identify an user 
and automatically decrypt protected e-mails.
- Full binary protocol (in contrast with the text based protocol used by 
SMTP).
- Multiple-Body capability. Automatic e-mail checking and notification. Etc.
- FREE SERVICE.

You can know all about the protocol features by going here: 
www.hidens.com.ar

Create your account (free) and download the e-mail client by going here: 
www.hidensmail.com.ar

Used ICS components:

HiDens Mail Server: WSocketServer
HiDens Mail Client: WSocketClient and HttpClient
HiDens User Account Manager: HttpServer
Protocol development time and testings: 2 years.
Final applications development time: 8 months.

I think this is an interesting alternative for many peoples (like me) and 
companies now very tired about the high volume of spam and poor security 
levels found using the standard e-mail...

thanks for your time,

David Jorge Aguirre Grazio
www.djag.com.ar

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be