obscuring emailadress glitch/bug

[ZapZombie 0]

Hi

With preference "obscure identifying info" on,

reporting spam via webinterface, after clicking "report spam" button,

I noticed:

"Delivered-To: x"..

"X-Sieve-Redirected-From: mynot_obscured@mailaddress.com"..

Regards

[Lking 0]

A full example would help all us understand ~~ a Tracking URL

[ZapZombie 0]

https://www.spamcop.net/mcgi?action=gettrack&reportid=6804862617

At my ISP I have an alias address that forwards to the well obscured address at "Delivered-To:"

The spam was sent to that alias. In the above example I replaced it.

Edited April 5, 2018 by ZapZombie

[Lking 0]

You provided a "Report id" which only you can view.   At the top of the report page you will see "Parse"  when you click on that, at the top of the next page

Quote

SpamCop v 4.9.0 © 2018 Cisco Systems, Inc. All rights reserved.
Here is your TRACKING URL - it may be saved for future reference:
https://www.spamcop.net/sc?id=z6456238576z3a31b84e0c282f137df43c5480053e72z

That is the Tracking URL

[ZapZombie 0]

Tracking URL :

https://www.spamcop.net/sc?id=z6457316120z2ce5a5054be23932c67d47b2baa08f09z

[Lking 0]

I have not seen a "X-" line added there in the header before, not that means anything.

Quote

X-Sieve: Pigeonhole Sieve 0.4.20 (11e3001)
X-Sieve-Redirected-From: myaddressThatForwardsToDeliveredTo@replaced.nl

Those two lines were added by some email processing app along the line.  Sense that type of header entry can be made by any application that 'touches' the email I believe the parser just skips over them.

[lisati 0]

Good luck getting this sorted out.

I'm mildly disappointed that the parser detected a problem with the chain of received headers, it would have been nice for Spark NZ (who "own" the xtra.co.nz domain) to have another prod to sort out their email system.

Edited April 5, 2018 by lisati