[quote user="aligregory"]
Hi thanks for your post.
I have removed my .dll Daemon and .ini file from the Mercury directory now and both Mercury and Pegasus are working as they should. By that I mean that the pop3 client receives a mail in from google mail and then routes it to a local user called 'ali' which can then be viewed in Pegasus.
I thought it would be helpful to you if I provide a bit of back ground of what I am trying to achieve. When a new message is received I want my Daemon to inspect it's content, only take out what I need (i.e the To:, From: Subject: and main body fields) and then forward it on to an SMS server that I have set up. For the moment though to write it to a text file will be adequate.
However, as soon as I put my Daemon stuff back into the Daemon directory I experience the following problems:
1.) Mail no longer manages to be delievered to my local user
2,) Due to the message being un-deliverable I get a load of automated 'postmaster' messages generated which also end up being processed by my Daemon process.
Do you think it is best that I send you what code I have already written so you can try and tell why it is interfering with the normal functionality of Mercury being able to deliver messages to local users?
Thanks,
Ali
[/quote]
Can't help you with the daemon at all, however since there are many people writing daemons that manipulate both the QCF and QDF files when received I suspect that you are somehow messing up the QDF file so the QCF file can't deliver it.
[quote user="aligregory"]<p>Hi thanks for your post.</p>
<p>&nbsp;I have removed my .dll Daemon and .ini file from the Mercury directory now and both Mercury and Pegasus are working as they should. By that I mean that the pop3 client receives a mail in from google mail and then&nbsp; routes it to a local user called 'ali' which can then be viewed in Pegasus.</p>
<p>&nbsp;I thought it would be helpful to you if I provide a bit of back ground of what I am trying to achieve. When a new message is received I want my Daemon to inspect it's content, only take out what I need (i.e the To:, From: Subject: and main body fields) and then forward it on to an SMS server that I have set up. For the moment though to write it to a text file will be adequate.</p>
<p>However,&nbsp;as soon as I put my Daemon stuff back into the Daemon directory&nbsp;I experience the following problems:</p>
<p>1.) Mail no longer manages to be delievered to my local user</p>
<p>2,) Due to the message being un-deliverable I get a load of automated 'postmaster' messages generated which also end up being processed by my Daemon process.</p>
<p>&nbsp;Do you think it is best that I send you what code I have already written so you can try and tell why it is interfering with the normal functionality of Mercury being able to deliver messages to local users?</p>
<p>&nbsp;Thanks,</p>
<p>Ali</p><p>[/quote]</p><p>&nbsp;</p><p>Can't help you with the daemon at all, however since there are many people writing daemons that manipulate&nbsp; both the QCF and QDF files when received I suspect that you are somehow messing up the QDF file so the QCF file can't deliver it.</p><p>&nbsp;</p>