Hello, everyone.
Well... I have read all of the appropriate man pages about procmail,
and I have even searched through the procmail list archives for
answers/solutions to my problem. In other words, I have "RTFM" :)...
Despite all of this effort, it seems that I have not been able to
create a procmail recipe (in .procmailrc) that will bounce messages
sent from certain perpetrators, with an error message, as per an
exitcode setting, e.g. 67 or 77.
I got some clues from some recent postings to this list, regarding the
.forward file (and its syntax). Currently, my .forward file says:
"|IFS=' ' ;exec /usr/local/bin/procmail #debraw"
Previously, my .forward file read like this:
"|IFS=' ' && exec /usr/local/bin/procmail -f- || exit 75 #debraw"
The procmail recipe that I am testing, for this purpose, is:
:0
* ^From.*juno.com
{
EXITCODE=67
:0
/dev/null
}
I do not want to permanently "deep-six" email from Juno. I have a Juno
account, along with this one. All I want to do is see if the recipe
works completely, i.e. assigning exitcode, sending a bounce-type
message (according to exitcode value) to Juno, and directing any email from
Juno to /dev/null.
I tested this setup several times yesterday, and earlier today, by
sending test messages from my Juno account to my WWA address. During
the last attempts, my log file said (in these excerpts):
procmail: Match on "^From.*juno.com"
procmail: Assigning "EXITCODE=67"
procmail: Assigning "LASTFOLDER=/dev/null"
procmail: Opening "/dev/null"
From juno.com!debra42 Thu Feb 20 02:13:38 1997
Subject: test
Folder: /dev/null 647
procmail: Notified comsat: "debraw(_at_)0:/dev/null"
...
procmail: Match on "^From.*juno.com"
procmail: Assigning "EXITCODE=67"
procmail: Assigning "LASTFOLDER=/dev/null"
procmail: Opening "/dev/null"
From juno.com!debra42 Thu Feb 20 03:00:25 1997
Subject: Test msg. for exitcode 67.
Folder: /dev/null 677
procmail: Notified comsat: "debraw(_at_)0:/dev/null"
...
procmail: Match on "^From.*juno.com"
procmail: Assigning "EXITCODE=67"
procmail: Assigning "LASTFOLDER=/dev/null"
procmail: Opening "/dev/null"
From juno.com!debra42 Thu Feb 20 06:44:09 1997
Subject: Test msg.
Folder: /dev/null 659
procmail: Notified comsat: "debraw(_at_)0:/dev/null"
So... At least, I could see that procmail was sending such emails to
/dev/null. But, I saw no indication that an error message was sent to
Juno, during this test period, by reviewing my log file. Also, when I
logged into my Juno account during this time, I never got any bounced
email messages back via email.
All I want to know is (1) where am I going wrong here, and (2) what can
I do to solve this problem. I would like to use exitcodes in procmail
to send particular messages to email abusers. And, as I understand it,
the inclusion of certain exitcodes in a procmail recipe, i.e. 67 and/or
77, are supposed to do the trick.
Can anyone assist me?
Thanks, in advance, for any helpful responses.
Debra Walker
--
Debra Walker debraw(_at_)wwa(_dot_)com
Chicago, IL debra42(_at_)juno(_dot_)com