David Rose wrote:
> Am I correct in thinking that the SMTP client component does not support
> natively sending mail using MX records ?
Yes. As you point out, it is an SMTP client component, and as such
connects to a specified SMTP server. Performing direct connections to
recipients' servers
Hi,
Try removing the if not (FTPClient1.Binary) then line. It could already be
binary in the component but the typeset command may not have been issued
before.
Regards,
SZ
- Original Message -
From: "David Rose" <[EMAIL PROTECTED]>
To:
Sent: Friday, December 16, 2005 12:26 AM
Subje
Is there something wrong with the code below. As far as I understand it should
be uploading in binary mode, but the
FTP conversation looks like it's in ASCII mode, though the (23MB) file does
seem to upload correctly.
If I try something like FTPexplorer then the FTP log does show "Opening BINARY
Hello!
>> FP> I have a development version for TWSocket which share the same
>> window handle
>> FP> for as many TWSocket as you like (for one as now to any large value
>> which
>> FP> fit your needs). Initially, I planned to make it available as a next
>> majour
>FP> release but I had no time to
> Am I correct in thinking that the SMTP client component does not support
> natively sending mail using MX records ?
> In other words if I want to send mail using MX records I'd have to do a
> DNS lookup on the recipients email address then connect to that server
> using the SMTP client component,
Am I correct in thinking that the SMTP client component does not support
natively sending mail using MX records ?
In other words if I want to send mail using MX records I'd have to do a
DNS lookup on the recipients email address then connect to that server
using the SMTP client component, send t
Just have a look at the source code ftpcli.pas. Search for "proxy" and you'll
find some background
informations about proxy support. There are several kind of proxies...
If you have a "transparent proxy", here are the steps (no programming needed !):
1) Instead of connection to a remote FTP se
> I looked and could only find it (no-cache)in the CreateVirtualDocument
> procedures. There is no "no_cache" in WebServ1.pas and I assume you
> refer to "no-cache".
Seems you have an outdated ICS. Download again from my website, preferably the
last ICS-beta which
is the version I really use in m
> I am evaluating ICS, specifically the component thttpcli and have the
> following problem: if I retrieve a web page with multibyte characters,
> I cannot seem to get the data in proper format. It seems like the
> Buffer that comes with HttpDocEnd() is a char *, not a WideString or
> something sim
I think that is a simple question, so common, but i dont know how to
do this, i try and see that exist a propertie just to inform the proxie
address, but how to make a authentication in a proxie? My proxie
requires authentication, how to do this with ftp client component?
Cenary
p
Hi,
I am evaluating ICS, specifically the component thttpcli and have the
following problem: if I retrieve a web page with multibyte characters,
I cannot seem to get the data in proper format. It seems like the
Buffer that comes with HttpDocEnd() is a char *, not a WideString or
something similar.
I looked and could only find it (no-cache)in the CreateVirtualDocument
procedures. There is no "no_cache" in WebServ1.pas and I assume you
refer to "no-cache". I understand it for the dynamic pages but I still
cannot how to do it for all other non-dynamic pages it delivers.
Thanx for you fast resp
Hello Francois,
This would be nice :-) I heard you talking about this one year before
and I was wondering when you planned to implement it officially.
FP> I have a development version for TWSocket which share the same window handle
FP> for as many TWSocket as you like (for one as now to any large
13 matches
Mail list logo
