[quote user="Vincent Fatica"]
P.S., In the forum's message composer, how do you get your code to appear in a box?
[/quote]
That was just an indent actually. :)
/Rolf
After the submission of a message to a list with one member, my DAEMON() is called. It does this
CHAR filename[MAX_PATH];
mi->ji_access_job_data(job, filename, MAX_PATH);
and writes filename to a log file, I get the likes of this (single string):
D:\MERCURY\QUEUE\MG000001.QDFD:\MERCURY\QUEUE\MG000002.QDF
What do I make of this, handle it? I want to remove a header from the outgoing message (which ultimately winds up being in MG000003.QDF). (I'm using Mercury v4.62.)
Thanks.
[quote user="Vincent Fatica"]
After the submission of a message to a list with one member, my DAEMON() is called. It does this
CHAR filename[MAX_PATH];
mi->ji_access_job_data(job, filename, MAX_PATH);
and writes filename to a log file, I get the likes of this (single string):
D:\MERCURY\QUEUE\MG000001.QDFD:\MERCURY\QUEUE\MG000002.QDF
What do I make of this, handle it? I want to remove a header from the outgoing message (which ultimately winds up being in MG000003.QDF). (I'm using Mercury v4.62.)
Thanks.
[/quote]
Sorry, I didn't have newlines in my debug logging function, so that's actually 2 calls to DAEMON(). I still don't know what to make of it. Why is my DAEMON() being called twice?
Thanks.
You should be able to see the corresponding message ids in the Mercury core log file, which might give some hint. Are there any other deamons loaded?
/Rolf
No, there are no other daemons loaded.
I'm trying to get rid of the "Sender:" header that's put into messages to lists. And I'm trying to do it "by the book". Code like this (below) just results in an endless loop of files being created in the queue (with alternating names) and my daemon being called over and over.
CHAR *rid[2] = {"Sender", NULL};
CHAR filename[MAX_PATH];
mi->ji_open_job(job);
mi->ji_access_job_data(job, filename, MAX_PATH);
mi->edit_message_headers(filename, &rid[1], rid);
mi->ji_unaccess_job_data(job);
mi->ji_close_job(job);
return 0;
Am I doing something wrong? Has David taken steps so the "Sender:" header cannot be removed?
I mainly write in Pascal and haven't made any global daemon that modifies raw message data, but I did a small test which worked OK in my system (slightly simplified code with just the main ingredients):
if mi.ji_access_job_data(job, Filename, 256) = 1 then
begin
mi.logstring(10, LOG_DEBUG, 'Message extracted');
if mi.edit_message_headers(Filename, AddHeaders, DelHeaders) = 1 then
mi.logstring(10, LOG_DEBUG, 'Headers have been modified.')
else mi.logstring(10, LOG_DEBUG, 'Error modifying headers.');
mi.ji_unaccess_job_data(job);
end
else
mi.logstring(10, LOG_DEBUG, 'Failed to extract message');
Result := 0;
/Rolf
[quote user="Rolf Lindby"]
I mainly write in Pascal and haven't made any global daemon that modifies raw message data, but I did a small test which worked OK in my system (slightly simplified code with just the main ingredients):
That's basically the same as the one I had posted except that I did no logging and did call ji_open/close_job. So I mimmicked yours (C code below). It worked! I don't know what the problem was with using ji_open/close_job. Thanks.if mi.ji_access_job_data(job, Filename, 256) = 1 then
begin
mi.logstring(10, LOG_DEBUG, 'Message extracted');
if mi.edit_message_headers(Filename, AddHeaders, DelHeaders) = 1 then
mi.logstring(10, LOG_DEBUG, 'Headers have been modified.')
else mi.logstring(10, LOG_DEBUG, 'Error modifying headers.');
mi.ji_unaccess_job_data(job);
end
else
mi.logstring(10, LOG_DEBUG, 'Failed to extract message');
Result := 0;[/quote]
CHAR *rid[2] = {"Sender", NULL};P.S., In the forum's message composer, how do you get your code to appear in a box?
CHAR filename[MAX_PATH];
if ( mi->ji_access_job_data(job, filename, MAX_PATH) )
{
mi->logstring(10, LOG_DEBUG, filename);
if ( mi->edit_message_headers(filename, &rid[1], rid) )
mi->logstring(10, LOG_DEBUG, "Headers modified");
else
mi->logstring(10, LOG_DEBUG, "Error modifying headers");
mi->ji_unaccess_job_data(job);
}
else
mi->logstring(10, LOG_DEBUG, "Failed to access job data");
return 0;
