Yes, once a message is frozen, it usually remains there until you *do*
something. Exim freezes a message when it is stumped and often needs a
from you.
To deal with the frozen messages, if you have the eximon, that might
be easier for you. Myself, I don't like to mouse so I like the
command line.
exim -Mvb MESSAGE_ID
tells you what's in the body of the message, for example. You want to
read the documentation about "The Exim Command Line", especially the
options that start with -M to figure out what you want to do with the
frozen messages and how to do it.
So far, my frozen messages messages have all needed to be removed,
no other action yet for me:
exim -Mrm message_id
Most have been junk mail being sent to non-existent addresses on my
domain.
Adding:
receiver_verify = true
to the main configuration in my configure file stopped those.
---- QUESTIONS
However, I have two classes of frozen messages left and I'm wondering
if I can find a better way to deal with them.
The first is that a majordomo list owner's address stopped working and
mail that should go to him, i.e., his list's error messages, became
frozen instead. I wish it would be sent to majordomo-owner
automatically.
The other is a result of junk mail coming into my online petition
address. I simply can't figure out what is happening:
the -Mvh gives:
> 12m4dB-0008AF-00-H
> exim 402 400
> <>
> 957143053 0
> -ident exim
> -received_protocol local
> -body_linecount 45
> -frozen 957143057
> -localerror
> XX
> 1
> invest600@???
>
> 133P Received: from exim by rosa with local (Exim 3.13 #2)
> id 12m4dB-0008AF-00
> for invest600@???; Sun, 30 Apr 2000 18:04:13 -0700
> 042 X-Failed-Recipients: evote@???
> 058F From: Mail Delivery System <Mailer-Daemon@???>
> 024T To: invest600@???
> 059 Subject: Mail delivery failed: returning message to sender
> 037I Message-Id: <E12m4dB-0008AF-00@rosa>
> 038 Date: Sun, 30 Apr 2000 18:04:13 -0700
-Mvb gives:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. The following address(es) failed:
>
> evote@???:
> generated |/usr/local/majordomo/wrapper fence eVote_script2 resend -l petitionj -h deliberate.com petitionj-outgoing
>
> The following text was generated during the delivery attempt:
>
> ------ |/usr/local/majordomo/wrapper fence eVote_script2 resend -l petitionj -h deliberate.com petitionj-outgoing ------
>
> exim: neither action flags nor mail addresses given
>
> ------ This is a copy of the message, including all the headers. ------
>
> Return-path: <invest600@???>
> Received: from lisa.sersat.com.ar ([200.10.123.3])
> by rosa with esmtp (Exim 3.13 #2)
> id 12m4d8-0008A9-00
> for evote@???; Sun, 30 Apr 2000 18:04:12 -0700
> From: invest600@???
> To: health@???
> Subject: Investor
> MIME-Version: 1.0
> Content-Type: text/plain; charset=unknown-8bit
> DATE: 23 Feb 00 11:57:31 PM
> Message-ID: <eK4G749AXymnrsykgkAmz>
>
>
> NEW AGE CITIES, trading under the symbol NACT is alternative health communities that provides the most comprehensive online source of natural health related products and services, creating one of the most demographically targeted network of Web sites on the Internet.
>
>
>
> This Dot Com will generate profits immediately learn how;
> http://1075912011/newagecities1.html
>
> AOL users <a href="http://1075912011/newagecities1.html"> CLICK HERE</a>
>
>
>
> You were sent this message because your address is in our subscriber database.
> If you wish to be removed, please reply here; mailto:rem_nac1@email.com?subject=REMOVE
> and we will remove you from our subscriber list.
------
I'm clueless as to why exim didn't deliver to eVote@??? in
the first place. Then I guess its error message didn't find anywhere
to go and ended up in the frozen messages. Why didn't receiver_verify
simply refuse it in the first place?
If anyone has any ideas about how I can clean up these issues, that
would be great.
Marilyn Davis, Ph.D.
eVote - online polling software for email lists
http://www.deliberate.com
marilyn@???
+1 650 965-7121 (USA)
