Community Discussions and Support
Sending emails stopped working

See if you can follow a submitted message in console windows (or log files) as it is received by MercuryS and picked up by Mercury core, there might be some useful information there.

See if you can follow a submitted message in console windows (or log files) as it is received by MercuryS and picked up by Mercury core, there might be some useful information there.

Hi there,

 have a wierd problem after upgrading to latest Mercury. That is, something went off track before (Mercury just flashed the window and vanished when started). Deceided to try upgrade to 4.80 and that seemed to do the trick.

BUT:

when logging in as IMAP users sending emails do not work. The mails end up as MSnnn.qcf/qdf files in queue directory and gets stuck there.

Other MSnnn.qcf/qdf files are processed without any problems.

We are not using SSL of any kind at the moment.

I have also noted that we no longer have entries in IMAP Current User log window. This is also a change.

Have looked at the settings and find nothing I can question.

The issue is with at least one outlook user, one Pegasus IMAP access user, one iPAD user and several smartphone users.

I also noted that one qdf-file that went through OK had no \n (end-of-line) markers, while the ones stuck has \n for every line.

Any clue to what has happened are welcome ....

Kai Atle

<p>Hi there,</p><p> have a wierd problem after upgrading to latest Mercury. That is, something went off track before (Mercury just flashed the window and vanished when started). Deceided to try upgrade to 4.80 and that seemed to do the trick.</p><p>BUT:</p><p>when logging in as IMAP users sending emails do not work. The mails end up as MSnnn.qcf/qdf files in queue directory and gets stuck there.</p><p>Other MSnnn.qcf/qdf files are processed without any problems.</p><p>We are not using SSL of any kind at the moment.</p><p>I have also noted that we no longer have entries in IMAP Current User log window. This is also a change.</p><p>Have looked at the settings and find nothing I can question.</p><p>The issue is with at least one outlook user, one Pegasus IMAP access user, one iPAD user and several smartphone users.</p><p>I also noted that one qdf-file that went through OK had no \n (end-of-line) markers, while the ones stuck has \n for every line.</p><p>Any clue to what has happened are welcome .... </p><p>Kai Atle </p>

Further information ...

It looks like the MercuryE is not picking up the emails. Other qcf/qdf pairs generated by other clients are grabbed by MercE from the queue and processed correctly.

Kai Atle

<p>Further information ...</p><p>It looks like the MercuryE is not picking up the emails. Other qcf/qdf pairs generated by other clients are grabbed by MercE from the queue and processed correctly.</p><p>Kai Atle </p>

As a start, check MercuryS log and core log to see what happens when the client submits a message to Mercury. Additionally, verify that the mercury.ini settings file isn't damaged. (If needed, compare it to backups saved as MERCURY.BAK and MERCURY.BK2.)

 

<p>As a start, check MercuryS log and core log to see what happens when the client submits a message to Mercury. Additionally, verify that the mercury.ini settings file isn't damaged. (If needed, compare it to backups saved as MERCURY.BAK and MERCURY.BK2.)</p><p> </p>

[quote user="Rolf Lindby"]

As a start, check MercuryS log and core log to see what happens when the client submits a message to Mercury. Additionally, verify that the mercury.ini settings file isn't damaged. (If needed, compare it to backups saved as MERCURY.BAK and MERCURY.BK2.)

 [/quote]

 I cannot see any difference, malformed content or anything extraordinary in mercury.ini.  The strange thing is the qcf/qdf files are in the queue directory. Other files are entering the queue and gets processed by MercE on its poll cycle but not the ones from the IMAP users. The same happens when I access the server with the IMAP setup I have always used on Pegasus Mail. I cannot dechipher the content of the qcf-file, but the only difference I can see is that the working files I have been able to catch do not have \n (hard lineshift) while the ones stuck have all had the \n (\n just used as symbol for line shift)

Kai Atle

[quote user="Rolf Lindby"]<p>As a start, check MercuryS log and core log to see what happens when the client submits a message to Mercury. Additionally, verify that the mercury.ini settings file isn't damaged. (If needed, compare it to backups saved as MERCURY.BAK and MERCURY.BK2.)</p><p> [/quote]</p><p> I cannot see any difference, malformed content or anything extraordinary in mercury.ini.  The strange thing is the qcf/qdf files are in the queue directory. Other files are entering the queue and gets processed by MercE on its poll cycle but not the ones from the IMAP users. The same happens when I access the server with the IMAP setup I have always used on Pegasus Mail. I cannot dechipher the content of the qcf-file, but the only difference I can see is that the working files I have been able to catch do not have \n (hard lineshift) while the ones stuck have all had the \n (\n just used as symbol for line shift)</p><p>Kai Atle </p>
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