Hello Angus,
You are true, I made a mistake talking about "multiple threads", I
meant multiple components in a single thread with a thread dedicated
to the smtp component's so it is separated from the main GUI thread so
the visual interface (if any) should be always responsive whenever the
s
> The application I'm working on is 9 years old, has many thousands
> of man hours spent on it, and whilst it would be nice to have a
> single TSmtpCli, in order to avoid a massive code rewrite it's much
> easier for me to have lots of TSnmpCli components, rather than one
> (you can't see it, b
This is a really useful thing for me to know, thanks for posting this.
> This is the correct way of handling. As per the RFC, error codes win
> the 400 range are "transient errors", meaning that they are temporary,
> and the sender should retry eventually; while codes in the 500 range
> a
Thanks for all the messages! Some useful things for me to know.
My question wasn't about email volume as such, but simply about having lots of
TSmtpCli components active at any one time, even if they are not doing anything.
The application I'm working on is 9 years old, has many thousands of ma
On Aug 17, 2009, at 04:45, Dod wrote:
I usually do it according to fail code 5.x.x or 4.x.x for 4.x.x I
retry later, for 5.x.x I pout them appart to check manually why they
have been rejected.
This is the correct way of handling. As per the RFC, error codes win
the 400 range are "tr
On Aug 16, 2009, at 14:43, Pete Williams wrote:
Previously my app used a single TSmtpCli and this all worked fine.
Now however I have to send mail on behalf of lots of accounts and
the number of TsmtpCli components in use simultaneously, used in a
multi threaded application, could be in exc
Hello Angus,
I usually do it according to fail code 5.x.x or 4.x.x for 4.x.x I
retry later, for 5.x.x I pout them appart to check manually why they
have been rejected.
regards.
>> Also if a MX refuse you because of some blacklist then remove
>> thoses mails from the queue and send you
> Also if a MX refuse you because of some blacklist then remove
> thoses mails from the queue and send you a mail alert so you can
> investigate why destination refused your mail.
It's important not to fail an email on a first refusal, due to the wide
usage of 'greylisting' where the SMTP ser
Pete Williams wrote:
> Hi
>
> I've used ICS components for a while now and had great results.
>
> I have something new to do and wanted some advice before starting a
> new project.
>
> Previously my app used a single TSmtpCli and this all worked fine.
> Now however I have to send mail on behalf
Hello Pete,
200 mails per hour is really not much, a single thread can do much
more.
But you may be slowed by the other side smtp server if it is slow or
timeout. So doing multi-thread is a good way to maintain a good
average speed.
You can create 20 threads with a common queue
Hi
I've used ICS components for a while now and had great results.
I have something new to do and wanted some advice before starting a new project.
Previously my app used a single TSmtpCli and this all worked fine. Now however
I have to send mail on behalf of lots of accounts and the number
11 matches
Mail list logo
