Hi, I’m new to all this, and was looking for some help/advise with regards to
smtpclient.
Using the OverbyteIcsMailSnd as a demo app I can’t seem to send emails to gmail.
Here is the error log as provided in the demo app
Connecting to SMTP server...
220 mx.google.com ESMTP
Darren Doggett wrote:
530 5.7.0 Must issue a STARTTLS command first. 13sm630074ewy.13
530 5.7.0 Must issue a STARTTLS command first. 13sm630074ewy.13
Using my limted knowledge is the problem that the smtpclient
component is not sending the command
STARTLLS, if this is the case then can
I can't get the client working with it.
httpCli.TransferEncoding is a readonly property.
How can I set the transfer encoding to chunked and send seperate chunks ?
thx,
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
I can't get the client working with it.
httpCli.TransferEncoding is a readonly property.
How can I set the transfer encoding to chunked and send seperate chunks ?
From what I see there is no easy way to do it with the HttpCli, without
overriding some methods or/and add your own PostChunked
Paul wrote:
I can't get the client working with it.
httpCli.TransferEncoding is a readonly property.
It is server's TransferEncoding, that's why it's read only.
How can I set the transfer encoding to chunked and send seperate
chunks ?
THttpCli supports chunked encoding when it receives
So it's currently impossible with THttpCli :-(
I should at least be able to send substreams without ending the post
request, but haven't found a way to do this yet.
Paul
- Original Message -
From: Arno Garrels arno.garr...@gmx.de
To: ICS support mailing twsocket@elists.org
Sent:
So it's currently impossible with THttpCli :-(
No impossible but a little bit tricky probably.
Probably you'd better derive a new component and override what has to be.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet
Paul wrote:
So it's currently impossible with THttpCli :-(
Should not be difficult to add it to the component,
or a derived class. Are you sure the HTTP allows chunked
encoded POST requests and server commonly support it?
I should at least be able to send substreams without ending the post
- Original Message -
From: Arno Garrels arno.garr...@gmx.de
I wonder what you want to achieve?
speed.
If you managed to keep
one conection alive by sending an infinite data stream
it won't ensure that the other connection, your work
connection, won't be disconnected nevertheless.
Paul wrote:
- Original Message -
From: Arno Garrels arno.garr...@gmx.de
I wonder what you want to achieve?
speed.
If you managed to keep
one conection alive by sending an infinite data stream
it won't ensure that the other connection, your work
connection, won't be disconnected
If I got you right, you use ICS HTTP server and it disconnects
the connections, right? If you are on v7 I hope you noticed that
the HTTP server component got a new timeout feature that
disconnects clients even when they established
Keep-Alive connections? It's ON by default.
I use a modified
If you managed to keep one conection alive by sending an infinite data
stream
it won't ensure that the other connection, your work
connection, won't be disconnected nevertheless.
Should be possible if you write both server and client though.
Don't forget about proxies and firewalls. They
Don't forget about proxies and firewalls. They probably has also to
support it
It should be possible imho.
it's like sending a large file in pieces.
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Don't forget about proxies and firewalls. They probably has also to
support it
It should be possible imho.
it's like sending a large file in pieces.
Not exactly. Any device analysing the content has to decode chunks.
--
francois.pie...@overbyte.be
http://www.overbyte.be
--
To unsubscribe
Paul wrote:
With Http(s), you have to send a new request each time for each
message and there is a huge delay if multiple proxies are in between.
And you never know what those proxies do.
That makes me believe that HTTP isn't the right protocol for the job.
--
Arno Garrels
--
To unsubscribe
And you never know what those proxies do.
That makes me believe that HTTP isn't the right protocol for the job.
I wish I had another choise, but I'm not.
In the end, only https is allowed.
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Not exactly. Any device analysing the content has to decode chunks.
I still don't get it right then.
What is the problem with sending a large file and pause the transfer for a
few seconds in between ?
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
17 matches
Mail list logo