Sorry, I've no clue why your dm= configuration isn't working. You've munged the entries in your posted .ini file, but assuming the user and the domain are valid, then it should work.
[quote]Are you sure, that it is a queue problem? The connecting process between the mail client and MercuryS takes a long time. But once the client is connected to the MercuryS, the mail is immediately sent by MercuryE.
In the connection history, MercuryS lists the connection to the e-mail client at 23:55:44. After 36 seconds, the Mercury Core gets the mail and creates an outgoing job. Eight seconds later MercuryE reports that the e-mail was sent successfully. But then, I have to wait some further seconds, until the connection history from MercuryS is displayed. The entry, which I "quoted" above, appears together with the following message: "60 sec. elapsed, connection closed Wed Feb 02 23:56:44 2011". Is this normal? Whats wrong in my configuration?[/quote]
Am I sure? No, Its just a guess. Your earlier post said there was a delay before MercuryE sent the mail, but once it connected all was fine. Thus my thought that there was a pause before it polled the queue.
Based upon the times you've posted here, though, I'm not really seeing any delays in the Mercury processing. The MercuryS connection seems to be held open for an excessive amount of time, but that would be your email client doing that rather than Mercury. Am I misunderstanding the question? Because I'm not really seeing the issue ...
<p>Sorry, I've no clue why your dm= configuration isn't working.&nbsp; You've munged the entries in your posted .ini file, but assuming the user and the domain are valid, then it should work.
</p>
<p>
[quote]Are you sure, that it is a queue problem? The connecting process between the mail client and MercuryS takes a long time. But once the client is connected to the MercuryS, the mail is immediately sent by MercuryE.
In the connection history, MercuryS lists the connection to the e-mail client at 23:55:44. After 36 seconds, the Mercury Core gets the mail and creates an outgoing job. Eight seconds later MercuryE reports that the e-mail was sent successfully.&nbsp;But then, I have to wait some further seconds, until the connection history from MercuryS is displayed.&nbsp;The entry, which I "quoted" above, appears together with the following message: "60 sec. elapsed, connection closed Wed Feb 02 23:56:44 2011".&nbsp;Is this normal? Whats wrong in my configuration?[/quote]</p>
<p>Am I sure?&nbsp; No, Its just a guess.&nbsp; Your earlier post said there was a delay before MercuryE sent the mail, but once it connected all was fine.&nbsp; Thus my thought that there was a pause before it polled the queue.</p>
<p>Based upon the times you've posted here, though, I'm not really seeing any delays in the Mercury processing.&nbsp; The MercuryS connection seems to be held open for an excessive amount of time, but that would be your email client doing that rather than Mercury. Am I misunderstanding the question?&nbsp; Because I'm not really seeing the issue ...
</p>