Re: Procmail problem
Hi Anne, For me, it's sendmail that provides that - I found this out by using yum provides ala: yum provides /etc/smrsh chris On 2012-08-23, at 3:10 AM, Anne Wilson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 23/08/12 10:07, Andrey Y. Shevel wrote: >> >> Did you check the content of the directory /etc/smrsh ? >> > I don't have that directory - and I don't ever recall seeing one. > What package creates it? > > Anne >> Andrey >> >> >> >> On Wed, 22 Aug 2012, Anne Wilson wrote: >> >>> Date: Wed, 22 Aug 2012 12:33:09 +0100 From: Anne Wilson >>> To: Gerald Waugh >>> , SL Users >>> Subject: Re: Procmail problem >>> >> On 21/08/12 20:02, Gerald Waugh wrote: >>>>> >>>>> On 08/21/2012 01:50 PM, Anne Wilson wrote: >>>>>> For reasons not relevant to this list, I've been using >>>>>> GMail to read my mail for a while, so I hadn't noticed that >>>>>> my local mail server now has big problems. >>>>> >>>>>> I see mail arriving there in maillog, and my .forward file >>>>>> passes it to procmail - but procmail appears to be not >>>>>> doing its stuff - the messages aren't being delivered at >>>>>> all. >>>>> >>>>>> What could be wrong? >>>>> >>>>>> Anne >>>>> What is in your .procmailrc $HOME/.procmailrc >>>>> >> Thanks for answering. .procmailrc is a restored file that worked >> perfectly before - I'll give you the details if you still want to >> see it after reading this. >> >> Digging around in logs I found that there have been some problems >> with perl updates - and I assume that procmail is a perl app. It >> seems likely that I messed things up when setting repo priorities, >> so I set out to clean things up. >> >> First I removed the packages that wouldn't update, keeping a list >> so that I can restore them as soon as I have the problem sorted, >> and tweaked the priorities of rpmforge, since that seems to be the >> one that was missing out. At first I thought that had done it, as >> I got a clean list of updates about to perform. Unfortunately, I >> then got a transaction error - >> >> file /sbin/extlinux from install of syslinux-4.05-1.el6.rfx.x86_64 >> conflicts with file from package >> syslinux-extlinux-4.02-4.el6.x86_64 >> >> If I try to update the remaining packages as they stand at present >> I get >> >> Error: glibc-2.12-1.25.el6.i686 (sl) Requires: glibc-common = >> 2.12-1.25.el6 Installed: glibc-common-2.12.1.47.el6_2.5.x86_64 >> (@sl-security) glibc-common = 2.12.1.47.el6_2.5 Available: >> glibc-common-2.12-1.25.el6.x86_64 (sl) glibc-common = >> 2.12-1.25.el6 >> >> I thought of removing glibc, again, to instantly re-install, to >> ensure I got the right version, but that promises to remove >> hundreds of packages, so I abandoned that idea. >> >> By now I am completely out of my depth. Is it possible to repair >> this system, or would be simpler to just abandon it, and try a >> clean install, setting up everything afresh? I hate to be beaten, >> but a broken system is a liability. >> >> Anne >>> >> > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAlA2AZIACgkQj93fyh4cnBf96wCfZfZ+4Ds2K3RDiIsnMAMu8rMs > sR8AnRTndtUIJ0c4qoWsSlyofrEsCStk > =36CI > -END PGP SIGNATURE-
Re: Procmail problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/08/12 10:07, Andrey Y. Shevel wrote: > > Did you check the content of the directory /etc/smrsh ? > I don't have that directory - and I don't ever recall seeing one. What package creates it? Anne > Andrey > > > > On Wed, 22 Aug 2012, Anne Wilson wrote: > >> Date: Wed, 22 Aug 2012 12:33:09 +0100 From: Anne Wilson >> To: Gerald Waugh >> , SL Users >> Subject: Re: Procmail problem >> > On 21/08/12 20:02, Gerald Waugh wrote: >>>> >>>> On 08/21/2012 01:50 PM, Anne Wilson wrote: >>>>> For reasons not relevant to this list, I've been using >>>>> GMail to read my mail for a while, so I hadn't noticed that >>>>> my local mail server now has big problems. >>>> >>>>> I see mail arriving there in maillog, and my .forward file >>>>> passes it to procmail - but procmail appears to be not >>>>> doing its stuff - the messages aren't being delivered at >>>>> all. >>>> >>>>> What could be wrong? >>>> >>>>> Anne >>>> What is in your .procmailrc $HOME/.procmailrc >>>> > Thanks for answering. .procmailrc is a restored file that worked > perfectly before - I'll give you the details if you still want to > see it after reading this. > > Digging around in logs I found that there have been some problems > with perl updates - and I assume that procmail is a perl app. It > seems likely that I messed things up when setting repo priorities, > so I set out to clean things up. > > First I removed the packages that wouldn't update, keeping a list > so that I can restore them as soon as I have the problem sorted, > and tweaked the priorities of rpmforge, since that seems to be the > one that was missing out. At first I thought that had done it, as > I got a clean list of updates about to perform. Unfortunately, I > then got a transaction error - > > file /sbin/extlinux from install of syslinux-4.05-1.el6.rfx.x86_64 > conflicts with file from package > syslinux-extlinux-4.02-4.el6.x86_64 > > If I try to update the remaining packages as they stand at present > I get > > Error: glibc-2.12-1.25.el6.i686 (sl) Requires: glibc-common = > 2.12-1.25.el6 Installed: glibc-common-2.12.1.47.el6_2.5.x86_64 > (@sl-security) glibc-common = 2.12.1.47.el6_2.5 Available: > glibc-common-2.12-1.25.el6.x86_64 (sl) glibc-common = > 2.12-1.25.el6 > > I thought of removing glibc, again, to instantly re-install, to > ensure I got the right version, but that promises to remove > hundreds of packages, so I abandoned that idea. > > By now I am completely out of my depth. Is it possible to repair > this system, or would be simpler to just abandon it, and try a > clean install, setting up everything afresh? I hate to be beaten, > but a broken system is a liability. > > Anne >> > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA2AZIACgkQj93fyh4cnBf96wCfZfZ+4Ds2K3RDiIsnMAMu8rMs sR8AnRTndtUIJ0c4qoWsSlyofrEsCStk =36CI -END PGP SIGNATURE-
Re: Procmail problem
Did you check the content of the directory /etc/smrsh ? Andrey On Wed, 22 Aug 2012, Anne Wilson wrote: Date: Wed, 22 Aug 2012 12:33:09 +0100 From: Anne Wilson To: Gerald Waugh , SL Users Subject: Re: Procmail problem -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/08/12 20:02, Gerald Waugh wrote: On 08/21/2012 01:50 PM, Anne Wilson wrote: For reasons not relevant to this list, I've been using GMail to read my mail for a while, so I hadn't noticed that my local mail server now has big problems. I see mail arriving there in maillog, and my .forward file passes it to procmail - but procmail appears to be not doing its stuff - the messages aren't being delivered at all. What could be wrong? Anne What is in your .procmailrc $HOME/.procmailrc Thanks for answering. .procmailrc is a restored file that worked perfectly before - I'll give you the details if you still want to see it after reading this. Digging around in logs I found that there have been some problems with perl updates - and I assume that procmail is a perl app. It seems likely that I messed things up when setting repo priorities, so I set out to clean things up. First I removed the packages that wouldn't update, keeping a list so that I can restore them as soon as I have the problem sorted, and tweaked the priorities of rpmforge, since that seems to be the one that was missing out. At first I thought that had done it, as I got a clean list of updates about to perform. Unfortunately, I then got a transaction error - file /sbin/extlinux from install of syslinux-4.05-1.el6.rfx.x86_64 conflicts with file from package syslinux-extlinux-4.02-4.el6.x86_64 If I try to update the remaining packages as they stand at present I get Error: glibc-2.12-1.25.el6.i686 (sl) Requires: glibc-common = 2.12-1.25.el6 Installed: glibc-common-2.12.1.47.el6_2.5.x86_64 (@sl-security) glibc-common = 2.12.1.47.el6_2.5 Available: glibc-common-2.12-1.25.el6.x86_64 (sl) glibc-common = 2.12-1.25.el6 I thought of removing glibc, again, to instantly re-install, to ensure I got the right version, but that promises to remove hundreds of packages, so I abandoned that idea. By now I am completely out of my depth. Is it possible to repair this system, or would be simpler to just abandon it, and try a clean install, setting up everything afresh? I hate to be beaten, but a broken system is a liability. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA0w3MACgkQj93fyh4cnBcTLACgivsdNoODcfSkS1WvRvKi6kQ1 YlYAn0R5Dy/JE5nJKjxHxBNKtOJSJl+s =3oqy -END PGP SIGNATURE- -- NAME: Andrey Y. Shevel (Chevel) : EMAIL: andrey.she...@pnpi.spb.ru \ Computing Systems Department: http://hepd.pnpi.spb.ru/CSD | TEL : +7(81371)36040 | POST ADDRESS: Petersburg Nuclear Physics Inst. | FAX : +7(81371)36040 | 188300, Gatchina, Leningrad district, Russia. | __+7(81371)46256 /
Re: Procmail problem
On 2012/08/23 01:04, Anne Wilson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/08/12 22:40, jdow wrote:
On 2012/08/22 11:08, Anne Wilson wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 22/08/12 18:17, Konstantin Olchanski wrote:
On Wed, Aug 22, 2012 at 12:33:09PM +0100, Anne Wilson wrote:
... procmail appears to be not doing its stuff
What could be wrong?
Why just had a spike of cartalk style questions "my car does
not start, what could be wrong?"
(my procmail, my wifi, whatever).
What could be wrong?
Instead of facile retorts, why not ask a question if you think
particular information may help? In fact someone with more sense
has helped me off-list, if only to confirm that my install is
broken beyond what would be a sensible repair.
Just as a matter of interest, when I ask a question with only
outline information, as this was, it's because I need a pointer
as to which particular bit of the problem is most likely to need
investigation, in order to avoid swamping the list with
irrelevancies. You spectacularly failed to give this.
Anne, I know you are not a newby. But your question was sort of
vague and seemed to betray a failure to perform some basic
troubleshooting 101 steps, "man procmail" is one. (There IS a lot
to read there in the various files. But learning the basics of how
procmail works is going to be step one for a lasting good solution.
This is hard for ancient bitches like me but I persevere. Having
learned is a nice feeling. The distressing part is how fast it all
dribbles away these days.)
{o.o}
That I can empathise with. However, procmail has worked for me for
several years until this problem, so I was pretty sure that it was not
the obvious problem of broken procmailrc. As I said, I wanted a
pointer to other things that could affect the working.
Browsing through logs (something that I simply hadn't had time for in
the last few weeks due to family problems) I found that an update had
broken some perl packages, and I couldn't get those mended. The
problem almost certainly started when I followed web-page advice about
fixing priorities on the repos. The more I dig, the more I find that
it has messed up such a large part of the installation that it is
simply not feasible to try to fix it. A new install would be much
quicker.
Look to what procmail calls, like SpamAssassin. THAT might be where the
breakage exists.
{^_^}
Re: Procmail problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/08/12 22:40, jdow wrote:
> On 2012/08/22 11:08, Anne Wilson wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 22/08/12 18:17, Konstantin Olchanski wrote:
>>> On Wed, Aug 22, 2012 at 12:33:09PM +0100, Anne Wilson wrote:
>
>> ... procmail appears to be not doing its stuff
>
>> What could be wrong?
>>>
>>>
>>> Why just had a spike of cartalk style questions "my car does
>>> not start, what could be wrong?"
>>>
>>> (my procmail, my wifi, whatever).
>>>
>>> What could be wrong?
>>>
>>>
>> Instead of facile retorts, why not ask a question if you think
>> particular information may help? In fact someone with more sense
>> has helped me off-list, if only to confirm that my install is
>> broken beyond what would be a sensible repair.
>>
>> Just as a matter of interest, when I ask a question with only
>> outline information, as this was, it's because I need a pointer
>> as to which particular bit of the problem is most likely to need
>> investigation, in order to avoid swamping the list with
>> irrelevancies. You spectacularly failed to give this.
>
> Anne, I know you are not a newby. But your question was sort of
> vague and seemed to betray a failure to perform some basic
> troubleshooting 101 steps, "man procmail" is one. (There IS a lot
> to read there in the various files. But learning the basics of how
> procmail works is going to be step one for a lasting good solution.
> This is hard for ancient bitches like me but I persevere. Having
> learned is a nice feeling. The distressing part is how fast it all
> dribbles away these days.)
>
> {o.o}
That I can empathise with. However, procmail has worked for me for
several years until this problem, so I was pretty sure that it was not
the obvious problem of broken procmailrc. As I said, I wanted a
pointer to other things that could affect the working.
Browsing through logs (something that I simply hadn't had time for in
the last few weeks due to family problems) I found that an update had
broken some perl packages, and I couldn't get those mended. The
problem almost certainly started when I followed web-page advice about
fixing priorities on the repos. The more I dig, the more I find that
it has messed up such a large part of the installation that it is
simply not feasible to try to fix it. A new install would be much
quicker.
Anne
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlA14/wACgkQj93fyh4cnBcO/QCeOs9A04H28djiYoHkC4X77OYk
/XkAn2I96R/DAHnSxdlvz0wRTQYhm86T
=6K4X
-END PGP SIGNATURE-
Re: Procmail problem
On 2012/08/22 11:08, Anne Wilson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/08/12 18:17, Konstantin Olchanski wrote:
On Wed, Aug 22, 2012 at 12:33:09PM +0100, Anne Wilson wrote:
... procmail appears to be not doing its stuff
What could be wrong?
Why just had a spike of cartalk style questions "my car does not
start, what could be wrong?"
(my procmail, my wifi, whatever).
What could be wrong?
Instead of facile retorts, why not ask a question if you think
particular information may help? In fact someone with more sense has
helped me off-list, if only to confirm that my install is broken
beyond what would be a sensible repair.
Just as a matter of interest, when I ask a question with only outline
information, as this was, it's because I need a pointer as to which
particular bit of the problem is most likely to need investigation, in
order to avoid swamping the list with irrelevancies. You
spectacularly failed to give this.
Anne, I know you are not a newby. But your question was sort of vague
and seemed to betray a failure to perform some basic troubleshooting
101 steps, "man procmail" is one. (There IS a lot to read there in the
various files. But learning the basics of how procmail works is going
to be step one for a lasting good solution. This is hard for ancient
bitches like me but I persevere. Having learned is a nice feeling. The
distressing part is how fast it all dribbles away these days.)
{o.o}
Re: Procmail problem
On 2012/08/22 04:33, Anne Wilson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/08/12 20:02, Gerald Waugh wrote:
On 08/21/2012 01:50 PM, Anne Wilson wrote:
For reasons not relevant to this list, I've been using GMail to
read my mail for a while, so I hadn't noticed that my local mail
server now has big problems.
I see mail arriving there in maillog, and my .forward file
passes it to procmail - but procmail appears to be not doing its
stuff - the messages aren't being delivered at all.
What could be wrong?
Anne
What is in your .procmailrc $HOME/.procmailrc
Thanks for answering. .procmailrc is a restored file that worked
perfectly before - I'll give you the details if you still want to see
it after reading this.
Digging around in logs I found that there have been some problems with
perl updates - and I assume that procmail is a perl app. It seems
likely that I messed things up when setting repo priorities, so I set
out to clean things up.
First I removed the packages that wouldn't update, keeping a list so
that I can restore them as soon as I have the problem sorted, and
tweaked the priorities of rpmforge, since that seems to be the one
that was missing out. At first I thought that had done it, as I got a
clean list of updates about to perform. Unfortunately, I then got a
transaction error -
file /sbin/extlinux from install of syslinux-4.05-1.el6.rfx.x86_64
conflicts with file from package syslinux-extlinux-4.02-4.el6.x86_64
If I try to update the remaining packages as they stand at present I get
Error: glibc-2.12-1.25.el6.i686 (sl)
Requires: glibc-common = 2.12-1.25.el6
Installed: glibc-common-2.12.1.47.el6_2.5.x86_64 (@sl-security)
glibc-common = 2.12.1.47.el6_2.5
Available: glibc-common-2.12-1.25.el6.x86_64 (sl)
glibc-common = 2.12-1.25.el6
I thought of removing glibc, again, to instantly re-install, to ensure
I got the right version, but that promises to remove hundreds of
packages, so I abandoned that idea.
By now I am completely out of my depth. Is it possible to repair this
system, or would be simpler to just abandon it, and try a clean
install, setting up everything afresh? I hate to be beaten, but a
broken system is a liability.
Anne, procmail is not in any way related to perl. It is a modest ELF
binary executable.
So let's start with some basics. Is there an /etc/procmailrc file? What
does it look like. What does your home directory's .procmailrc file look
like? Procmail has been solid for me for two decades or so now. It has
also grown as I put in "discard with extreme prejudice" anti-troll
measures. (That would be sites that require me to verify I am really
me before they will forward a mailing list email to the customer, for
example.) Make sure you have no such filters in your .procmailrc file.
Generally consider procmail as a filter. Text goes in, is manipulated,
and usually flows out the other end ultimately into the user's mailbox.
You CAN cozen procmail into inserting log messages as it processes emails.
(Heck, I had mine rigged to play chimes when I received customer emails at
one time.)
If you have log messages of these emails going into procmail then it is
time to get procmail to tell you what it is doing. You CAN set a "VERBOSE"
flag, "VERBOSE=yes". That gets it to spit out error messages of some use.
Note that sigs USR1 will turn off VERBOSE and USR2 will turn it on.
Note that this little incantation right after any defines in .procmailrc
will preserve emails so you can manually process them after splitting
the email out of the destination file using "mail -f$HOME/mail/rawmbox":
:0c: clone.lock
$HOME/mail/rawmbox
Then you can run procmail manually with a copy of your .procmailrc and
figure out pretty decently what is actually going on.
{^_^}
Re: Procmail problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/08/12 18:17, Konstantin Olchanski wrote: > On Wed, Aug 22, 2012 at 12:33:09PM +0100, Anne Wilson wrote: >>> ... procmail appears to be not doing its stuff >>> What could be wrong? > > > Why just had a spike of cartalk style questions "my car does not > start, what could be wrong?" > > (my procmail, my wifi, whatever). > > What could be wrong? > > Instead of facile retorts, why not ask a question if you think particular information may help? In fact someone with more sense has helped me off-list, if only to confirm that my install is broken beyond what would be a sensible repair. Just as a matter of interest, when I ask a question with only outline information, as this was, it's because I need a pointer as to which particular bit of the problem is most likely to need investigation, in order to avoid swamping the list with irrelevancies. You spectacularly failed to give this. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA1H/8ACgkQj93fyh4cnBcxEQCfR5WDNGPYjJ+y3AaaZaxz8L0W 2rAAmwa9UU2w1MyqL3Orlt5uknhvm9hg =9Q/t -END PGP SIGNATURE-
Re: Procmail problem
On Wed, Aug 22, 2012 at 12:33:09PM +0100, Anne Wilson wrote: > > > >> ... procmail appears to be not doing its stuff > > > >> What could be wrong? Why just had a spike of cartalk style questions "my car does not start, what could be wrong?" (my procmail, my wifi, whatever). What could be wrong? -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: Procmail problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/08/12 20:02, Gerald Waugh wrote: > > On 08/21/2012 01:50 PM, Anne Wilson wrote: >> For reasons not relevant to this list, I've been using GMail to >> read my mail for a while, so I hadn't noticed that my local mail >> server now has big problems. > >> I see mail arriving there in maillog, and my .forward file >> passes it to procmail - but procmail appears to be not doing its >> stuff - the messages aren't being delivered at all. > >> What could be wrong? > >> Anne > What is in your .procmailrc $HOME/.procmailrc > Thanks for answering. .procmailrc is a restored file that worked perfectly before - I'll give you the details if you still want to see it after reading this. Digging around in logs I found that there have been some problems with perl updates - and I assume that procmail is a perl app. It seems likely that I messed things up when setting repo priorities, so I set out to clean things up. First I removed the packages that wouldn't update, keeping a list so that I can restore them as soon as I have the problem sorted, and tweaked the priorities of rpmforge, since that seems to be the one that was missing out. At first I thought that had done it, as I got a clean list of updates about to perform. Unfortunately, I then got a transaction error - file /sbin/extlinux from install of syslinux-4.05-1.el6.rfx.x86_64 conflicts with file from package syslinux-extlinux-4.02-4.el6.x86_64 If I try to update the remaining packages as they stand at present I get Error: glibc-2.12-1.25.el6.i686 (sl) Requires: glibc-common = 2.12-1.25.el6 Installed: glibc-common-2.12.1.47.el6_2.5.x86_64 (@sl-security) glibc-common = 2.12.1.47.el6_2.5 Available: glibc-common-2.12-1.25.el6.x86_64 (sl) glibc-common = 2.12-1.25.el6 I thought of removing glibc, again, to instantly re-install, to ensure I got the right version, but that promises to remove hundreds of packages, so I abandoned that idea. By now I am completely out of my depth. Is it possible to repair this system, or would be simpler to just abandon it, and try a clean install, setting up everything afresh? I hate to be beaten, but a broken system is a liability. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA0w3MACgkQj93fyh4cnBcTLACgivsdNoODcfSkS1WvRvKi6kQ1 YlYAn0R5Dy/JE5nJKjxHxBNKtOJSJl+s =3oqy -END PGP SIGNATURE-
Re: Procmail problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/21/2012 01:50 PM, Anne Wilson wrote: > For reasons not relevant to this list, I've been using GMail to read my > mail for a while, so I hadn't noticed that my local mail server now has > big problems. > > I see mail arriving there in maillog, and my .forward file passes it to > procmail - but procmail appears to be not doing its stuff - the messages > aren't being delivered at all. > > What could be wrong? > > Anne What is in your .procmailrc $HOME/.procmailrc - -- Gerald -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBUDPbYawFZStizgrfAQKzDwgA5bcoGvIBnugxjsmFpPMGrTZw9kaoujmx Cv6d6r80CvQUS7bUiLOQgflf+zYBC+MbnCvs1gCa05Z55qc4q3m9/dfdarg/N+Zb /g6lg3kvZJC60v3k66YzDBwQA031mmlCXxIz+5xJVV8QhbiZMxEe4u2oxflA3iR+ dm6Yd2Fi+MXyksSkKJplaW4mFnzCDrtYJVWahHejNlAq3Ojy3Jr8j64bttEPa4Y4 fCD7Y8nPyOjlgFjVH04tcXaV1qkz+K+pM7hNpe/3HcvRSroMqWXPwXqgAHahS37Z oVvj/bNZ9kHmiTKCDH2BqcxNSSWL6rjzaTBkadAw0on8QtirxgVzCQ== =W/tm -END PGP SIGNATURE-
Procmail problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For reasons not relevant to this list, I've been using GMail to read my mail for a while, so I hadn't noticed that my local mail server now has big problems. I see mail arriving there in maillog, and my .forward file passes it to procmail - but procmail appears to be not doing its stuff - the messages aren't being delivered at all. What could be wrong? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAz2IUACgkQj93fyh4cnBfDnQCggJDh+BYC2UnJo1P0zsW7ye6p +LYAnA781VB3ATMP8YKwvEZvNfQr1jZy =AXTf -END PGP SIGNATURE-
