You weren't unclear, I just have more questions and didn't realize a couple
of things. I appreciate your patience with me and continual guidance.
I removed the local IP's from the WhitelistedIPs. I have been using the
same config file for LocalIPs as I did for WhitelistedIPs for as long as
I've been using ASSP (at least 2003). I can't say why I had it set this
way, surely confusion, but I haven't seen negative consequences because of
it. Whatever the case, I've followed your guidance and now have a blank
WhitelistedIPs config file.
Now that I've done this, when i sent a message to an external NoProcessing
email address, the X-ASSP lines are better-
X-ASSP-Re-noProcessing: mynoproctestemailaddr...@gmail.com
X-ASSP-NoProcessing: YES <--- without the reason the email passed.
What I still don't understand is:
1) Why would we want to show the X-ASSP-Re-noProcessing line to an outside
recipient? We strip other X-ASSP lines to the outside, why not this one?
And why show X-ASSp-NoProcessing line externally? Again, not a big deal,
but curious.
2) Why would the first reason that a message passed (in my case, the poorly
configured white ip list) be listed in the the X-AASP-NoProcessing line?
That confused me and made me think that is was the whitelist that caused it
to be no processing
a) Once I removed the bad whitelist ip config, now the externally
recieved email just says X-ASSP-NoProcessing: YES with no reason the mail
passed in the first line. Seems inconsistent logic, so I'm trying to get a
grasp on the purpose of having it set this way
None of this is really important, just looking to satisfy curiosity.
On Sun, Jan 7, 2018 at 12:18 PM, Thomas Eckardt <thomas.ecka...@thockar.com>
wrote:
> >It's like the NoProcessing to email address is erroneously triggering
> the IP to show in the header,
>
> No - what was unclear in my explanation ???
>
> X-ASSP-NoProcessing: YES - shows that the email address is in noprocessing
>
> (whiteListedIPs '*10.11.12.0/24* <http://10.11.12.0/24>') shows the first
> passing reason for the mail - the connected IP is whitelisted and this
> was detected before
>
> The header line shows both - noprocessing and the first passing reason.
>
> btw.: local IP's should not be whitelisted.
>
> Thomas
>
>
>
>
>
> Von: "K Post" <nntp.p...@gmail.com>
> An: "ASSP development mailing list" <assp-test@lists.sourceforge.
> net>
> Datum: 07.01.2018 18:12
> Betreff: Re: [Assp-test] No processing regex through relay port,
> X-ASSP lines
> ------------------------------
>
>
>
> But *10.11.12.0/24* <http://10.11.12.0/24> isn't listed in any no
> processing file. It IS listed in AcceptAllMail
>
> If I send an email through the same internal Exchange server to an address
> that isn't listed in NoProcessing, I don't get the two 2 X-ASSP lines on
> the receiver, which sounds normal to me. It's still going through the same
> ASSP relay, from the same exchange Ip.
>
> It's like the NoProcessing to email address is erroneously triggering the
> IP to show in the header, either that or I've got something misconfigured
> (which certainly wouldn't be the first time). I've got no idea how long
> this has been going on, I just happened to notice it.
>
> Confused, but this isn't urgent!
>
> On Wed, Jan 3, 2018 at 10:48 PM, Thomas Eckardt <
> *thomas.ecka...@thockar.com* <thomas.ecka...@thockar.com>> wrote:
> >X-ASSP-Re-noProcessing: *mynoproctestemailaddr...@gmail.com*
> <mynoproctestemailaddr...@gmail.com>
>
> this shows the match and possible reason for noprocessing
>
> >X-ASSP-NoProcessing: YES - (whiteListedIPs '*10.11.12.0/24*
> <http://10.11.12.0/24>')
>
> this show that noprocessing is active - (whiteListedIPs '*10.11.12.0/24*
> <http://10.11.12.0/24>') shows the first passing reason for the mail
>
> So, this is by design and OK.
>
> Thomas
>
>
>
> Von: "K Post" <*nntp.p...@gmail.com* <nntp.p...@gmail.com>>
> An: "ASSP development mailing list" <
> *assp-test@lists.sourceforge.net* <assp-test@lists.sourceforge.net>>
> Datum: 03.01.2018 17:22
> Betreff: [Assp-test] No processing regex through relay port,
> X-ASSP lines
> ------------------------------
>
>
>
>
> Happy new year all!
>
> I happened to catch in an email that I sent to a gmail account which is in
> my no processing RE file, that when the message was received on the gmail
> side, the no processing X-ASSP lines hadn't been stripped.
>
> I don't know if it matters, but I send via MS Exchange through ASSP's
> relay port.
>
> Is this normal behavior?
>
> X-ASSP-Re-noProcessing: *mynoproctestemailaddr...@gmail.com*
> <mynoproctestemailaddr...@gmail.com>
> X-ASSP-NoProcessing: YES - (whiteListedIPs '*10.11.12.0/24*
> <http://10.11.12.0/24>')
>
> *10.11.12.0/24* <http://10.11.12.0/24> is our internal subnet, but that's
> not no-processing. If I send the same way to a gmail address that isn't in
> npRE,neither of the above 2 lines show up (As expected).
>
> Not urgent, but I'd appreciate some guidance.
>
> Thanks
> Ken
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! *http://sdm.link/slashdot*
> <http://sdm.link/slashdot>
> _______________________________________________
> Assp-test mailing list
> *Assp-test@lists.sourceforge.net* <Assp-test@lists.sourceforge.net>
> *https://lists.sourceforge.net/lists/listinfo/assp-test*
> <https://lists.sourceforge.net/lists/listinfo/assp-test>
>
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, legally
> privileged and protected in law and are intended solely for the use of the
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! *http://sdm.link/slashdot*
> <http://sdm.link/slashdot>
> _______________________________________________
> Assp-test mailing list
> *Assp-test@lists.sourceforge.net* <Assp-test@lists.sourceforge.net>
> *https://lists.sourceforge.net/lists/listinfo/assp-test*
> <https://lists.sourceforge.net/lists/listinfo/assp-test>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, legally
> privileged and protected in law and are intended solely for the use of the
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
