On Wed, 30 Oct 2019, wes wrote:
testing
Wes,
Thank you! The clog has apparently been cleared.
Regards,
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
On Wed, 30 Oct 2019, Chuck Hast wrote:
Konfuse me, I am interested,
Me, too.
I'm pretty sure everyone is wrong at this point, the world needs a USB
version recap. I see conversations like this one all the time, and all
anyone seems to talk about is the speed. There's actually several reasons
On Wed, 30 Oct 2019, Ben Koenig wrote:
Ok then, you asked for it. This may be the most amazing wall of internet
text to ever grace this mailing list. I am in no way liable for any costs
or damages incured as a result of this message.
Thank you, Ben.
My needs are simple and speed is not an iss
Hello,
A colleague is looking for someone with extensive experience working
with SELinux rules to assist with a specific customer issue initially,
as well as be a general resource and help us come up to speed on
internal knowledge and documentation.
The initial issue centers around SE module
I addition to several mail lists not being properly routed by procmail
recipies, for each incoming message the log records:
procmail: Opening "/log"
procmail: Error while writing to "/log"
The log file in located in ~/procmail/ and has 666 perms.
Web searches find hits on writing to /var/log/pro
On Thu, 31 Oct 2019, Rich Shepard wrote:
I addition to several mail lists not being properly routed by procmail
recipies, for each incoming message the log records:
procmail: Opening "/log"
procmail: Error while writing to "/log"
The log file in located in ~/procmail/ and has 666 perms.
Looki
On Oct 31, 2019, at 4:35 PM, Rich Shepard wrote:
>
> On Thu, 31 Oct 2019, Rich Shepard wrote:
>
>> I addition to several mail lists not being properly routed by procmail
>> recipies, for each incoming message the log records:
>> procmail: Opening "/log"
>> procmail: Error while writing to "/log"
On Thu, 31 Oct 2019, Louis Kowolowski wrote:
If there is an error writing to “/log” that sounds like a path problem.
For permissions, directory permissions?
Louis,
Perhaps. The perms on ~/mail/ were 775 and I just changed that to 777.
But, there are only a few maillists that procmail does no
On 10/31/19 3:13 PM, Louis Kowolowski wrote:
On Oct 31, 2019, at 4:35 PM, Rich Shepard wrote:
On Thu, 31 Oct 2019, Rich Shepard wrote:
I addition to several mail lists not being properly routed by procmail
recipies, for each incoming message the log records:
procmail: Opening "/log"
procmail
On Thu, 31 Oct 2019, David wrote:
This is precisely what I was trying to say here:
http://lists.pdxlinux.org/pipermail/plug/2019-October/093324.html
David,
I don't think I received that one.
I personally don't believe that permissions are the issue here.
Me neither.
Perhaps if a saniti
On 10/31/19 5:11 PM, Rich Shepard wrote:
On Thu, 31 Oct 2019, David wrote:
This is precisely what I was trying to say here:
http://lists.pdxlinux.org/pipermail/plug/2019-October/093324.html
David,
I don't think I received that one.
I personally don't believe that permissions are the issue
On 10/31/19 5:15 PM, David wrote:
On 10/31/19 5:11 PM, Rich Shepard wrote:
On Thu, 31 Oct 2019, David wrote:
This is precisely what I was trying to say here:
http://lists.pdxlinux.org/pipermail/plug/2019-October/093324.html
David,
I don't think I received that one.
I personally don't bel
On Thu, 31 Oct 2019, David wrote:
Try adding this and trying again:
PMDIR=$HOME/.procmail
David,
Now, PMDIR=$HOME/procmail because that's where all the files are stored. The
only procmail dot-file is $HOME/.procmailrc.
Rich
___
PLUG mailing list
PL
On Thu, 31 Oct 2019, David wrote:
MAILDIR=$HOME/mail
DEFAULT=/var/spool/mail/rshepard
ORGMAIL=/var/spool/mail/rshepard
LOGFILE=$PMDIR/log
# Directory for storing procmail-related files
PMDIR=$HOME/procmail
I stand by the suggestion to configure the PMDIR value above the LOGFILE
specification.
14 matches
Mail list logo
