Since there doesn't seem to be any changes I'll ask another question:
DAEMONEXPORT short daemon (void *job, M_INTERFACE *mi, char *address)
{
void *blank;
mi->logstring (20100, LOG_NORMAL, "TEST DAEMON: Daemon function called");
blank = mi->ji_create_job(JT_GENERAL, "u.d@o.com", NULL);
mi->ji_add_element(blank, "Joshua.Arner@ATIMetals.com");
mi->ji_add_data(blank, "Subject:This is it");
mi->ji_close_job(blank);
mi->ji_close_job(job);
return 0;
}
When
I run this as part of the code for daemon1.dll in the DDK the message
triggers the daemon and create the message just fine. However, the
triggering message is marked with a retry flag and repeats the entire
process on the next poll cycle. Am I doing something wrong or is there a
way to reset this flag?
My only solution is to try to copy the message and have the daemon return 1 to delete the message, I'd rather not do that.
<p>Since there doesn't seem to be any changes I'll ask another question:</p><p>DAEMONEXPORT short daemon (void *job, M_INTERFACE *mi, char *address)</p><p>{
&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; void *blank;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; mi-&gt;logstring (20100, LOG_NORMAL, "TEST DAEMON: Daemon function called");
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; blank = mi-&gt;ji_create_job(JT_GENERAL, "u.d@o.com", NULL);
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; mi-&gt;ji_add_element(blank, "Joshua.Arner@ATIMetals.com");
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; mi-&gt;ji_add_data(blank, "Subject:This is it");
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; mi-&gt;ji_close_job(blank);
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mi-&gt;ji_close_job(job);
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return 0;</p><p>
}</p><p>&nbsp;</p><p>When
I run this as part of the code for daemon1.dll in the DDK the message
triggers the daemon and create the message just fine.&nbsp; However, the
triggering message is marked with a retry flag and repeats the entire
process on the next poll cycle.&nbsp; Am I doing something wrong or is there a
way to reset this flag?</p><p>&nbsp;</p><p>My only solution is to try to copy the message and have the daemon return 1 to delete the message, I'd rather not do that.
</p>