Re: [PLUG] incron issue

My sample code works like this in principle: 1. You said 4-ish invocations per print file. That means that there would be 4-ish instances of your script running, if I would not use that lock file in /tmp to detect that another script instance is already dealing with the print file. So, the script

Re: [PLUG] incron issue

Me looking at kernel software would be no more educational than me reading about it in Greek. And I did not think I wanted to debug the spooler, whatever that is. So to get down to the essentials, using only IN_CLOSE_WRITE, I get four events (with this particular application printing). For a

Re: [PLUG] SMTP communications question

On Tue, 21 Nov 2017, Rich Shepard wrote:     To improve your emails deliverability, your MTA-EHLO/PTR/MX hostnames should all match. If you use an inbound/cloud filtering service, the hostname in your DNS MX record doesn't need to match, but the MTA EHLO and PTR/reverse DNS should match.

Re: [PLUG] SMTP communications question

> > > BTW, if you can suggest a mail list or web forum for openDKIM assistance > I'd appreciate it. > > I gave up on trying to make mail work a long time ago. In fact, now that I think of it, I believe it was trying to get DKIM to work that finally pushed me over the edge to giving up. -wes

Re: [PLUG] SMTP communications question

On Tue, 21 Nov 2017, Alexandre Bedard wrote:     Your EHLO hostname is controlled by your MTA (Postfix, Sendmail,qmail, etc), not the MUA. Most MTA's have a configuration option to specify your mail server's EHLO hostname. Most Linux distros/MTA's will default to the contents of /etc/mailname.

Re: [PLUG] SMTP communications question

On Tue, 21 Nov 2017, wes wrote: This is up to the administrator of the recipient MTA. They can decide whether to reject mail from senders who claim to be host x in their HELO, but have a different name in their PTR record. In my experience, most of them simply check that a PTR record exists at

Re: [PLUG] SMTP communications question

This is up to the administrator of the recipient MTA. They can decide whether to reject mail from senders who claim to be host x in their HELO, but have a different name in their PTR record. In my experience, most of them simply check that a PTR record exists at all, as it used to be hard to get

[PLUG] SMTP communications question

I understand that when an e-mail message is sent the client MTA initiates communications with the receiving/relaying server MTA with a HELO or EHLO command. The recipient MTA is identified by its DNS MX record. Both HELO/EHLO and MX have a host name prefixed to the domain name. Does it

Re: [PLUG] incron issue

Of course that you see some/many invocations without any file names when you trigger on all directory events. All sorts of of processes go by all sorts of directories all the time on modern desktop. Not all of them look at files. What your aim is, I believe/hope, to respond to print file write

Re: [PLUG] incron issue

It is fully my intention to use only IN_CLOSE_WRITE in the final version. I currently am using IN_ALL_EVENTS just to see what the print driver/application is doing. In fact, when I first started working on this I used just IN_CLOSE_WRITE and saw 4 invocations. That is what sent me exploring.

Re: [PLUG] Reality check

On 11/20/2017 07:58 PM, Mke C> wrote: On 11/20/2017 05:54 PM, plug-requ...@pdxlinux.org wrote: -clip - When the firewall receives an ICMP packet, ping and traceroute both will show failure and/or lack of "up: state. If the attacker knows the device is there by DNS resolution or IP

Re: [PLUG] Reality check

Not the original poster - BUT, thank you very much for such positive post Mike. ... more or these please ... and Knipex tools too! On Nov 20, 2017 7:58 PM, "Mke C" wrote: On 11/20/2017 05:54 PM, plug-requ...@pdxlinux.org wrote: > With the mail/phone issues I've had

Re: [PLUG] incron issue

$(some command) will simply execute the command and give return value. You do not see any time stamp because you are not giving stat a file. $1, in your case, doesn't contain file name. I have asked or suggested before to only use IN_CLOSE_WRITE event. That is what you want - run the script