Roman Gelfand:
> Please, see below... The whole turnaround was roughly a second. What
> I meant by "Sending mail into Postfix" is chilkat application takes 13
> seconds to send it.
>
> Sep 12 10:38:49 mail1 postfix/smtpd[30657]: connect from
> unknown[192.168.0.147]
...
> Sep 12 10:38:50 mail1 postfix/smtp[30325]: 0208544124:
> to=<dkfsdklfd...@marketplace.amazon.com>,
> relay=retail-smtp-in.amazon.com[176.32.98.133]:25, delay=0.26,
> delays=0/0/0.1/0.15, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as
> 52D9D9EC1AE)
> Sep 12 10:38:50 mail1 postfix/qmgr[3632]: 0208544124: removed
A this point it would be worthwhile for you to look at the chilkat
side of things. I am not familar with chilkat, but I would expect
that it can produce logging that shows where it is spending its
time.
As long as you aren't overloading Postfix, i.e. you don't have
logging like this:
Oct 3 20:39:27 spike postfix/master[28905]: warning: service "smtp"
(25) has reached its process limit "30": new clients may experience
noticeable delays
Then there is nothing that could be fixed on the Postfix side.
Wietse
