Difference between SMTPSend and Worker

Mike Matthews - Omnis omnis at lineal.co.uk
Tue Apr 12 17:44:07 UTC 2022

Nothing is wrong with it, I use it.  By using the Worker, it does give back control to the user quicker than having to wait for the SMTP command to complete.

Mike Matthews

Lineal Software Solutions
Commercial House, The Strand<x-apple-data-detectors://1/1> Barnstaple, Devon, EX31 1EU<x-apple-data-detectors://1/1>

omnis at lineal.co.uk<mailto:mike.matthews at lineal.co.uk>



On 12 Apr 2022, at 18:33, Das Goravani <goravanis at gmail.com<mailto:goravanis at gmail.com>> wrote:

Dear $all,

I know that Omnis recommends using the SMTP OW3 worker object over the SMTPSend command, but I don’t know WHY that is.

WHY do they recommend that way?

Is there something wrong with the SMTP Send command?

I have used SMTPSend in a repeat loop sending around 800 emails in a row, with no problems. It works.

I realize that with the worker you can do a mailshot, that’s nice. I found that I have things to do to each email in-between send commands, so a mail shot wouldn’t work for me based on my past needs anyways. I don’t need it to run in the background, foreground is fine. If these things are true then is there a need for me to use the worker?  I am going to implement the worker in my IMAP Client app, for sure, but I just want to understand what is "wrong" with the SMTPSend command if anything.


Das Goravani
Manage your list subscriptions at https://lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com

More information about the omnisdev-en mailing list