I am be interested :-)
On Tue, 2019-01-01 at 19:40 -0800, Russell Senior wrote:
> Excellent! Moar days to procrastinate!
>
> If people want to hear about my temperature sensor array re-
> engineering
> project, an update to the talk I did in 2013, including zeromq and
> software
> defined radio,
Is anyone running a MTA checking with njabl and having it reject legitimate
incoming messages?
This is happening here with postfix-3.3.1, apparently started some time
overnight. I've commented it out in main.cf but am curious why it started
mis-fuctioning.
Rich
__
njabl, no. I'm using postscreen with the following weights:
postscreen_dnsbl_sites =
list.dnswl.org=127.0.[0..255].0*-2
list.dnswl.org=127.0.[0..255].1*-4
list.dnswl.org=127.0.[0..255].2*-6
list.dnswl.org=127.0.[0..255].3*-8
zen.spamhaus.org=127.0.0.9*25
zen.spamhaus.org=127.0.0.3*10
On Wed, 2 Jan 2019, Alexandre Bedard wrote:
Afaik they don't exist anymore. It's common place for RBLs to return
positive to all queries when they cease operations, as a heads up to
sysadmins to remove them from their configuration.
Alexandre,
Thanks for the insight. They must have pulled
On Wed, 2 Jan 2019, Louis Kowolowski wrote:
njabl, no. I'm using postscreen with the following weights:
postscreen_dnsbl_sites =
Louis,
I'm unfamiliar with postscreen and will learn how to use it. Here, the
rbls are in smtpd_client_restrictions as, for example,
reject_rbl_client zen.spamhau
Postscreen is something you can run "in front" of postfix to provide additional
screening options for incoming mail. Something like greylisting, policy, etc,
but part of postfix.
http://www.postfix.org/POSTSCREEN_README.html
> On Jan 2, 2019, at 9:57 AM, Rich Shepard wrote:
>
> On Wed, 2 Jan
On Wed, 2 Jan 2019, Louis Kowolowski wrote:
Postscreen is something you can run "in front" of postfix to provide
additional screening options for incoming mail. Something like
greylisting, policy, etc, but part of postfix.
http://www.postfix.org/POSTSCREEN_README.html
Thanks, Louis. Long ago
On Jan 2, 2019, at 11:14 AM, Rich Shepard wrote:
>
> On Wed, 2 Jan 2019, Louis Kowolowski wrote:
>
>> Postscreen is something you can run "in front" of postfix to provide
>> additional screening options for incoming mail. Something like
>> greylisting, policy, etc, but part of postfix.
>> http:/
I can run ssh -X on my Slackware machine and connect to my Ubuntu 18
machine. But I can't run caja on that connection. I get this error message:
dick@ENU-1$ caja
Could not parse arguments: Cannot open display:
dick@ENU-1$
Is there something else I need to do on the Slackware machine to make
th
On 1/2/19 10:01 AM, Dick Steffens wrote:
I can run ssh -X on my Slackware machine and connect to my Ubuntu 18
machine. But I can't run caja on that connection. I get this error message:
dick@ENU-1$ caja
Could not parse arguments: Cannot open display:
dick@ENU-1$
Try looking at the -Y flag to
On 1/2/19 10:04 AM, David wrote:
On 1/2/19 10:01 AM, Dick Steffens wrote:
I can run ssh -X on my Slackware machine and connect to my Ubuntu 18
machine. But I can't run caja on that connection. I get this error
message:
dick@ENU-1$ caja
Could not parse arguments: Cannot open display:
dick@ENU-
On 1/2/19 10:17 AM, Dick Steffens wrote:
On 1/2/19 10:04 AM, David wrote:
On 1/2/19 10:01 AM, Dick Steffens wrote:
I can run ssh -X on my Slackware machine and connect to my Ubuntu 18
machine. But I can't run caja on that connection. I get this error
message:
dick@ENU-1$ caja
Could not parse
That's good enough for me. I'll be at Lucky Lab NW (on Quimby) around 7pm
on Thursday with some toys.
On Wed, Jan 2, 2019 at 1:41 AM Tomas K wrote:
> I am be interested :-)
>
> On Tue, 2019-01-01 at 19:40 -0800, Russell Senior wrote:
> > Excellent! Moar days to procrastinate!
> >
> > If people w
On 1/2/19 10:17 AM, Dick Steffens wrote:
Another doh situation, but it doesn't change everything.
I managed to mistype the url when attempting to connect from the Ubuntu
machine to the Slackware machine. When I redid it with the right address
I got an error message telling me that the host key
Noticed this, this morning, from my browser trying to load either
https://pdxlinux.org or https://www.pdxlinux.org
www.pdxlinux.org uses an invalid security certificate. The certificate is
only valid for the following names: *.spiretech.com, spiretech.com Error
code: SSL_ERROR_BAD_CERT_DOMAIN
The
On 1/2/19 10:26 AM, David wrote:
<...>
When you connect each way, what is the response from the command:
echo $DISPLAY
In each case echo $DISPLAY returns a blank line.
If you get back a blank line, something is preventing the variable
from being set. If you get a line similar to "host:10.
On 1/2/19 10:42 AM, Dick Steffens wrote:
On 1/2/19 10:26 AM, David wrote:
<...>
Sounds like I need to figure out how to set DISPLAY.
Your sshd configuration may explicitly deny the variable from being set.
In my config file:
$ sudo grep X11Forwarding /etc/ssh/sshd_config
X11Forwarding ye
On Wed, 2 Jan 2019, David wrote:
If you edit that file to read as I have it, you will need to restart the
service.
Which on Slackware is done by root:
# /etc/rc.d/rc.sshd restart
Happy New Year,
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http:
On 1/2/19 10:51 AM, David wrote:
On 1/2/19 10:42 AM, Dick Steffens wrote:
On 1/2/19 10:26 AM, David wrote:
<...>
Sounds like I need to figure out how to set DISPLAY.
Your sshd configuration may explicitly deny the variable from being set.
In my config file:
$ sudo grep X11Forwarding /et
On 1/2/19 11:05 AM, Rich Shepard wrote:
On Wed, 2 Jan 2019, David wrote:
If you edit that file to read as I have it, you will need to restart
the service.
Which on Slackware is done by root:
# /etc/rc.d/rc.sshd restart
Yes. Thanks.
--
Regards,
Dick Steffens
__
On 1/2/19 11:07 AM, Dick Steffens wrote:
On 1/2/19 10:51 AM, David wrote:
On 1/2/19 10:42 AM, Dick Steffens wrote:
On 1/2/19 10:26 AM, David wrote:
<...>
In my config file:
$ sudo grep X11Forwarding /etc/ssh/sshd_config
X11Forwarding yes
If you have a "no" (which I think is the default) t
On 1/2/19 11:26 AM, David wrote:
On 1/2/19 11:07 AM, Dick Steffens wrote:
On 1/2/19 10:51 AM, David wrote:
On 1/2/19 10:42 AM, Dick Steffens wrote:
On 1/2/19 10:26 AM, David wrote:
<...>
In my config file:
$ sudo grep X11Forwarding /etc/ssh/sshd_config
X11Forwarding yes
If you have a "no
This my be related to my ssh -X "Could not parse arguments: Cannot open
display:" problem.
I ran the various SlackBuilds scripts to install the nVidia driver. It
all looked normal, like the other installs I've been doing. But, when I
try to run nvidia-settings I get this error message:
ERROR
$DISPLAY is set by X11, you shouldn't be setting it.
It's one of those things that you only set if you know that you need to set
it.
Which desktop are you using? XFCE?
On Wed, Jan 2, 2019 at 3:21 PM Dick Steffens wrote:
> This my be related to my ssh -X "Could not parse arguments: Cannot open
Ran some DDG searches, found a few old articles, maybe give this one a read?
https://www.linuxquestions.org/questions/slackware-14/x-forwarding-in-slack-over-ssh-unable-to-open-display-451697-print/
On Wed, Jan 2, 2019 at 11:39 AM Dick Steffens wrote:
> On 1/2/19 11:26 AM, David wrote:
> > On
On 1/2/19 6:07 PM, Ben Koenig wrote:
$DISPLAY is set by X11, you shouldn't be setting it.
It's one of those things that you only set if you know that you need to set
it.
I wondered about that.
Which desktop are you using? XFCE?
Yes. XFCE.
--
Regards,
Dick Steffens
___
On 1/2/19 6:28 PM, Ben Koenig wrote:
Ran some DDG searches, found a few old articles, maybe give this one a read?
https://www.linuxquestions.org/questions/slackware-14/x-forwarding-in-slack-over-ssh-unable-to-open-display-451697-print/
Thanks. I see some lines I haven't looked at in my ssh_co
Maybe I'm stating the obvious. Normally you would be running this command
from a local X client where the shell would have the $DISPLAY value set.
Like this:
echo $DISPLAY
127.0.0.1:0.0
Once I connect via ssh -X, the same command produces this output:
echo $DISPLAY
localhost:10.0
You have three
28 matches
Mail list logo
