Does this mean the senders in question are still in NoProcessingDomains?
In this particular case, the 'sender' was my mail server. It was sending the
nightly postfix report to me. For some reason, it would randomly match against
either lists.digium.com or mythtv.org.
Those domains are still
Does this mean the senders in question are still in NoProcessingDomains?
Daniel
On 1/19/2015 2:17 AM, Doug Lytle wrote:
Thomas Eckardt wrote:
noScanIP
I can't reproduce this issue - it works for me.
After moving the 2 IP addresses out of the web interface and into a file
If you feel more comfortable, change the option back to (
file:files/noscanav.txt) :):)
It wasn't effecting anybody but me. I'll revert my changes when I get home
tonight.
Doug
--
New Year. New Location. New
After moving the 2 IP addresses out of the web interface and into a file
(file:files/noscanav.txt), this problem went away.
I double checked this again. The IP regular expression is working for both
setup options 'ip' and 'file:'. Doug, could it be possible that there was
a hidden character in
Thomas Eckardt wrote:
After moving the 2 IP addresses out of the web interface and into a file
configuration - following these steps:
1 - look in to the folder: files/optRE and find the file 'noScanIPs.txt'
2 - make a backup of this file
3 - now change the config back to plain IP - take
