Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>These are bounce messages. Something is sending messages through your mail server, but the recipient is not accepting it, so your system generates a bounce message. Those bounce messages are being refused also, so they get "frozen" by the exim MTA. You need to figure out where the messages came from originally and stop the flow of those unauthorized messages.</p> <p><code>exigrep 1UorWC-0002Nz-Mz /var/log/exim/main.log</code> (or whatever your path is)</p> <p>That will find the bounce message in the mail logs. I picked a frozen message in my mail queue as an example (1UosOk-0000ej-KG):</p> <pre><code># exigrep 1UosOk-0000ej-KG /var/log/exim/main.log +++ 1UosOk-0000ej-KG has not completed +++ 2013-06-18 09:40:22 1UosOk-0000ej-KG &lt;= &lt;&gt; R=1UosOf-0000bX-BV U=www P=local S=894 2013-06-18 09:40:24 1UosOk-0000ej-KG ** origsender@example.biz P=&lt;&gt; R=dnslookup_forwarder T=remote_smtp_forwarder: SMTP error from remote mail server after RCPT TO:&lt;origsender@example.biz&gt;: host mail.example.biz [80.76.197.72]: 554 5.7.1 &lt;origsender@example.biz&gt;: Relay access denied 2013-06-18 09:40:24 1UosOk-0000ej-KG Frozen (delivery error message) </code></pre> <p>The first line says that the bounce message <strong>1UosOk-0000ej-KG</strong> was created in response to message <strong>1UosOf-0000bX-B</strong> (that is what the R= phrase in the &lt;= line means). Now search for <em>THAT</em> message id to find out where this message actually came from. In my case, it wasn't a bounce message, it was a customer's autoresponder:</p> <pre><code># exigrep 1UosOf-0000bX-BV /var/log/exim/main.log 2013-06-18 09:40:18 1UosOf-0000bX-BV H=example.biz [62.189.29.157] Warning: SPF PASS (pass) to m.ivenue.com: domain of example.biz designates 62.189.29.157 as permitted sender 2013-06-18 09:40:22 1UosOf-0000bX-BV &lt;= origsender@example.biz H=example.biz [62.189.29.157] P=esmtp S=17624 2013-06-18 09:40:22 1UosOf-0000bX-BV =&gt; /netapp3/mail/maildirs/b/o/y/boyexample.com/sarah/Maildir/ (sarah@boyexample.com) &lt;sarah@boyexample.com&gt; P=&lt;origsender@example.biz&gt; R=virtual_user T=address_directory 2013-06-18 09:40:22 1UosOf-0000bX-BV =&gt; sarah &lt;sarah@boyexample.com&gt; P=&lt;origsender@example.biz&gt; R=autoresponder_always T=autoresponder_always_t 2013-06-18 09:40:22 1UosOf-0000bX-BV Completed </code></pre> <p>Once you find out what process is being used to send those messages through your system, you can take steps to prevent them, assuming they are not valid messages to begin with. What steps you take will very much depend on what you find.</p> <p>Usually you will not want to try to resend these frozen messages. However, if the messages were frozen due to some temporary network or configuration error, and you want to make exim resend them, then you need to generate a list of frozen messages and tell Exim to deliver them. The easiest way is with the exiqgrep program:</p> <pre><code>exiqgrep -z -i | xargs -n 1 exim -M </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload