exim filters and/or procmail
Lee Bradshaw
I noticed that fetchmail was downloading, but then I didn't have any new
messages in my folders. I couldn't find anything useful in the log files and I
couldn't find the messages anywhere, so it looks like they went to /dev/null.
I'm now switching to exim.
Does anyone have an example of exim filters which split list mail into
different files?
Does anyone know how to get procmail working with exim?
Here is one of my attempted .forward files:
"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #lee"
And here are the results from /var/log/exim/mainlog:
1998-10-26 23:12:40 0zY0Uq-0000CK-00 <= debian-us...@lists.debian.org H=freefall [192.168.1.7] P=esmtp S=3410 id="-l7NY.A.JiG.icUN2"@murphy
1998-10-26 23:12:40 0zY0Uq-0000CK-00 ** |IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #lee <lee@freefall> D=userforward T=address_pipe: "IFS='" command not found for address_pipe transport
1998-10-26 23:12:40 0zY0Uq-0000CN-00 <= <> R=0zY0Uq-0000CK-00 U=mail P=local S=4246
1998-10-26 23:12:41 0zY0Uq-0000CK-00 Error message sent to debian-us...@lists.debian.org
1998-10-26 23:12:41 0zY0Uq-0000CK-00 Completed
1998-10-26 23:12:42 0zY0Uq-0000CN-00 => debian-us...@lists.debian.org R=smarthost T=remote_smtp H=mail.mindspring.com [207.69.200.195]
1998-10-26 23:12:42 0zY0Uq-0000CN-00 Completed
Please cc: replies. Before I removed my .forward exim generated quite a few
errors to debian-user-request. I'm afraid I may be kicked off the list.
--
Lee Bradshaw l...@sectionIV.com (preferred)
Alantro Communications l...@alantro.com
--
Unsubscribe? mail -s unsubscribe debian-us...@lists.debian.org < /dev/null
George Bonser
> Does anyone have an example of exim filters which split list mail into
> different files?
See the exim filter specification at www.exim.org
>
>
> Does anyone know how to get procmail working with exim?
no need, exim filter rules are more powerful than procmal.
BTW your mail is probably in smail's input queue. Try running smail -v -q
and see if your mail gets delivered. Smail is broken in the current
setup if you upgrade from a previous version and keep your config file. It
will end up queueing the mail rather than delivering it. Running the
following command as root helps:
smail -q5m
This is an example of smail's behavior changing between versions. If you
have an extensive custom config file and do not want it overwritten by the
package maintainer, you get a surprise in every version. Something
breaks.
>
> Here is one of my attempted .forward files:
>
> "|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #lee"
>
> And here are the results from /var/log/exim/mainlog:
>
> 1998-10-26 23:12:40 0zY0Uq-0000CK-00 <= debian-us...@lists.debian.org H=freefall [192.168.1.7] P=esmtp S=3410 id="-l7NY.A.JiG.icUN2"@murphy
> 1998-10-26 23:12:40 0zY0Uq-0000CK-00 ** |IFS=' ' && exec /usr/bin/procmail -f
- || exit 75 #lee <lee@freefall> D=userforward T=address_pipe:
"IFS='" command not found for address_pipe transport
Try
| "IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #lee"
instead of putting the quote before the pipe.
>
>
> Please cc: replies. Before I removed my .forward exim generated quite a few
> errors to debian-user-request. I'm afraid I may be kicked off the list.
>
> --
> Lee Bradshaw l...@sectionIV.com (preferred)
> Alantro Communications l...@alantro.com
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-us...@lists.debian.org < /dev/null
>
>
>
George Bonser
The Linux "We're never going out of business" sale at an FTP site near you!
ser...@purdue.edu
|
| Does anyone have an example of exim filters which split list mail into
| different files?
Here are some chunks of my .forward file that deal with the debian-*
lists traffic.
# Exim filter
if error_message then finish endif
if $h_X-Mailing-List: contains debian-user or
$h_X-Mailing-List: contains debian-changes
then
save /home/servis/Mail/debian
endif
if $h_X-Mailing-List: contains debian-devel
then
save /home/servis/Mail/debian-devel
endif
|
|
| Does anyone know how to get procmail working with exim?
|
If you can use the exim filter rules you don't need procmail.
--
Brian
---------------------------------------------------------------------
"Never criticize anybody until you have walked a mile in their shoes,
because by that time you will be a mile away and have their shoes."
- unknown
Mechanical Engineering ser...@purdue.edu
Purdue University http://www.ecn.purdue.edu/~servis
---------------------------------------------------------------------
Lee Bradshaw
> fetchmail: SMTP> MAIL FROM:<@pop.mindspring.com> SIZE=2249
> fetchmail: SMTP< 501 <@pop.mindspring.com> : colon expected after route
Sorry to follow up my own post, but I got the answer from the exim list.
Install a new version of fetchmail. I installed the slink version and the
problem was solved.
--
Lee Bradshaw l...@sectionIV.com (preferred)
Alantro Communications l...@alantro.com