1 |
Be forewarned that deliberate evasion of blocking methods in some |
2 |
jurisdictions could be construed as harassment, computer trespass, or both. |
3 |
|
4 |
I would strongly recommend that anyone doing so immediately cease and |
5 |
desist to avoid possible criminal charges. |
6 |
|
7 |
On Mon, Dec 5, 2016 at 2:05 PM, William L. Thomson Jr. <wlt-ml@××××××.com> |
8 |
wrote: |
9 |
|
10 |
> On Monday, December 5, 2016 9:52:26 PM EST Robin H. Johnson wrote: |
11 |
> > |
12 |
> > Why did your mail server (mail1.obsidian-studios.com) allow the |
13 |
> > forgeries to be sent? Even as an authenticated client allowed to relay |
14 |
> > email, it should be checking the envelope sender (and ideally the From |
15 |
> > header inside the email as well). |
16 |
> |
17 |
> I am looking into such. It reveled a series of problems. I filed 2 bugs |
18 |
> already |
19 |
> with KDE. |
20 |
> https://bugs.kde.org/show_bug.cgi?id=373313 |
21 |
> https://bugs.kde.org/show_bug.cgi?id=373314 |
22 |
> |
23 |
> I am looking into what happened with ASSP. I have one inquiry there already |
24 |
> https://sourceforge.net/p/assp/mailman/message/35533609/ |
25 |
> |
26 |
> ASSP likely did a SPF lookup but due to relaxed rules it did not flag nor |
27 |
> reject. Plus I am sending from internal authorized so may be bypassing some |
28 |
> checks. I have another issue where assp is not working with syslog |
29 |
> anymore. I |
30 |
> cannot look into logs to see what occurred. I never spoof emails, nor did |
31 |
> I do |
32 |
> it intentionally. I have to go see how this happened. |
33 |
> |
34 |
> I will take all the blame for something I stumbled across. So its my |
35 |
> problem. |
36 |
> Though anyone else in the world could have stumbled across it just the |
37 |
> same..... |
38 |
> |
39 |
> > Your MUA should have issued a warning, but it's not an error in any way. |
40 |
> |
41 |
> I agree, I filed a bug on such. |
42 |
> |
43 |
> -- |
44 |
> William L. Thomson Jr. |
45 |
> |