Community Discussions and Support
Automated mail being created with MIME Error

Hi Paul,

 The problem I have is this is for a university project and so I really need to be looking to do it as a Daemon that I've written myself in order to gain academic credit.

 Since Thomas' last post regarding the QDF and QCF files I performed the following experiment:

 1.) I took my .dll and .ini file out and sent a message. I performed as it should and was successfully received by the local user and could be viewed in Pegasus. The content of the QCF files was:

 ST: R 000000000000 00 000001 000000 000000
FR:
DF: MG000002.QDF
FL: 0         
OS: 080423161112
BA: ali
ES: R 080423161112
RI: 000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
DI: --------.---
EA:

2.) After this I added my .dll and .ini file back in and restarted Mercury. I sent the same message but it was not successfully delievered to the local user. The content of the QDF file was identical (except for time stamps obviously) but the QCF file was different to the run previous:

ST: R 000000000000 05 000001 000000 000000
FR:
DF: MG000001.QDF
FL: 0         
OS: 080423160045
BA: ali
ES: R 080423160045
RI: 000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
DI: --------.---
EA:

Do any differences in the QCF files indicate why there would be an error in delivering to local users?

 

 

<P>Hi Paul,</P> <P> The problem I have is this is for a university project and so I really need to be looking to do it as a Daemon that I've written myself in order to gain academic credit.</P> <P> Since Thomas' last post regarding the QDF and QCF files I performed the following experiment:</P> <P> 1.) I took my .dll and .ini file out and sent a message. I performed as it should and was successfully received by the local user and could be viewed in Pegasus. The content of the QCF files was:</P> <P> ST: R 000000000000 00 000001 000000 000000 FR: DF: MG000002.QDF FL: 0          OS: 080423161112 BA: ali ES: R 080423161112 RI: 000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000 DI: --------.--- EA: </P> <P>2.) After this I added my .dll and .ini file back in and restarted Mercury. I sent the same message but it was not successfully delievered to the local user. The content of the QDF file was identical (except for time stamps obviously) but the QCF file was different to the run previous:</P> <P>ST: R 000000000000 05 000001 000000 000000 FR: DF: MG000001.QDF FL: 0          OS: 080423160045 BA: ali ES: R 080423160045 RI: 000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000 DI: --------.--- EA: </P> <P>Do any differences in the QCF files indicate why there would be an error in delivering to local users?</P> <P mce_keep="true"> </P> <P mce_keep="true"> </P>

Hi,

When receiving messages in to Mercury I'm getting the following message being automatically created:

To: Electronic Postmaster <postmaster@localhost>
From: Electronic Postmaster <postmaster@localhost>
Date: Mon, 14 Apr 2008 17:27:03 +0100
Subject: Postmaster Notify: Delivery Failure.
MIME-Version: 1.0
Content-type: multipart/mixed; boundary=19478.7701043

This message is in MIME format. If you are seeing this text,
then your mailer does not understand this format properly.

--19478.7701043
Content-type: Text/Plain; charset=US-ASCII
Content-Disposition: Inline
Content-Description: Reason for delivery failure.

The attached message has failed delivery and has been referred
to you as postmaster. The following error report or reports
were given to explain the problem:

   *** Electronic Postmaster <postmaster@localhost>

--19478.7701043
Content-type: Message/RFC822

 Any ideas?

Thanks,

Alastair

 

&lt;P&gt;Hi,&lt;/P&gt; &lt;P&gt;When receiving messages in to Mercury I&#039;m getting the following message being automatically created:&lt;/P&gt; &lt;P&gt;To: Electronic Postmaster &amp;lt;&lt;A href=&quot;mailto:postmaster@localhost&quot;&gt;postmaster@localhost&lt;/A&gt;&amp;gt; From: Electronic Postmaster &amp;lt;&lt;A href=&quot;mailto:postmaster@localhost&quot;&gt;postmaster@localhost&lt;/A&gt;&amp;gt; Date: Mon, 14 Apr 2008 17:27:03 +0100 Subject: Postmaster Notify: Delivery Failure. MIME-Version: 1.0 Content-type: multipart/mixed; boundary=19478.7701043&lt;/P&gt; &lt;P&gt;This message is in MIME format. If you are seeing this text, then your mailer does not understand this format properly.&lt;/P&gt; &lt;P&gt;--19478.7701043 Content-type: Text/Plain; charset=US-ASCII Content-Disposition: Inline Content-Description: Reason for delivery failure.&lt;/P&gt; &lt;P&gt;The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem:&lt;/P&gt; &lt;P&gt;&amp;nbsp;&amp;nbsp; *** Electronic Postmaster &amp;lt;&lt;A href=&quot;mailto:postmaster@localhost&quot;&gt;postmaster@localhost&lt;/A&gt;&amp;gt;&lt;/P&gt; &lt;P&gt;--19478.7701043 Content-type: Message/RFC822&lt;/P&gt; &lt;P&gt;&amp;nbsp;Any ideas?&lt;/P&gt; &lt;P&gt;Thanks,&lt;/P&gt; &lt;P&gt;Alastair&lt;/P&gt; &lt;P mce_keep=&quot;true&quot;&gt;&amp;nbsp;&lt;/P&gt;

Are you saying that mail is not being delivered to the users?  If the mail is being properly delivered I would suspect that you have either an autoforward and/or a filter that is pointing to a bad address.

 

&lt;p&gt;Are you saying that mail is not being delivered to the users?&amp;nbsp; If the mail is being properly delivered I would suspect that you have either an autoforward and/or a filter that is pointing to a bad address.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

Hi Thomas,

 I do not wish for the messages to actually be delivered to any users but just sit in the queue. I was originally wanting the message to go to a local user but the daemon I have written seems to interfere and not allow this to happen. Instead now, I'd prefer if the message would sit in the queue and my daemon will manipulate the message from there. However, in order for me to use it, it must be in a clean MIME format and not contain all the postmaster error content.

Thanks!

&lt;P&gt;Hi Thomas,&lt;/P&gt; &lt;P&gt;&amp;nbsp;I do not wish for the messages to actually be delivered to any users but just sit in the queue. I was originally wanting the message to go to a local user but the daemon I have written seems to interfere and not allow this to happen. Instead now, I&#039;d prefer if the message would sit in the queue and my daemon will manipulate the message from there. However, in order for me to use it, it must be in a clean MIME format and not contain all the postmaster error content.&lt;/P&gt; &lt;P&gt;Thanks!&lt;/P&gt;

You need to remove your daemon and get Mercury working properly first.

There is no way to help you if your daemon is interfering with message processing. 

&lt;p&gt;You need to remove your daemon and get Mercury working properly first.&lt;/p&gt;&lt;p&gt;There is no way to help you if your daemon is interfering with message processing.&amp;nbsp;&lt;/p&gt;

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

&lt;P&gt;Hi thanks for your post.&lt;/P&gt; &lt;P&gt;&amp;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&amp;nbsp; routes it to a local user called &#039;ali&#039; which can then be viewed in Pegasus.&lt;/P&gt; &lt;P&gt;&amp;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&#039;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.&lt;/P&gt; &lt;P&gt;However,&amp;nbsp;as soon as I put my Daemon stuff back into the Daemon directory&amp;nbsp;I experience the following problems:&lt;/P&gt; &lt;P&gt;1.) Mail no longer manages to be delievered to my local user&lt;/P&gt; &lt;P&gt;2,) Due to the message being un-deliverable I get a load of automated &#039;postmaster&#039; messages generated which also end up being processed by my Daemon process.&lt;/P&gt; &lt;P&gt;&amp;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?&lt;/P&gt; &lt;P&gt;&amp;nbsp;Thanks,&lt;/P&gt; &lt;P&gt;Ali&lt;/P&gt;

[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=&quot;aligregory&quot;]&lt;p&gt;Hi thanks for your post.&lt;/p&gt; &lt;p&gt;&amp;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&amp;nbsp; routes it to a local user called &#039;ali&#039; which can then be viewed in Pegasus.&lt;/p&gt; &lt;p&gt;&amp;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&#039;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.&lt;/p&gt; &lt;p&gt;However,&amp;nbsp;as soon as I put my Daemon stuff back into the Daemon directory&amp;nbsp;I experience the following problems:&lt;/p&gt; &lt;p&gt;1.) Mail no longer manages to be delievered to my local user&lt;/p&gt; &lt;p&gt;2,) Due to the message being un-deliverable I get a load of automated &#039;postmaster&#039; messages generated which also end up being processed by my Daemon process.&lt;/p&gt; &lt;p&gt;&amp;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?&lt;/p&gt; &lt;p&gt;&amp;nbsp;Thanks,&lt;/p&gt; &lt;p&gt;Ali&lt;/p&gt;&lt;p&gt;[/quote]&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Can&#039;t help you with the daemon at all, however since there are many people writing daemons that manipulate&amp;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&#039;t deliver it.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

[quote user="aligregory"]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[/quote]

You may be able to do all this as a policy - which would be a lot easier to debug.

&lt;P&gt;[quote user=&quot;aligregory&quot;]When a new message is received I want my Daemon to inspect it&#039;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[/quote]&lt;/P&gt; &lt;P&gt;You may be able to do all this as a policy - which would be a lot easier to debug.&lt;/P&gt;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft