Trying to subscribe to freebsd-hackers, I filled in my name and email address and clicked "subscribe", but it seems not to have been processed, as I see: freebsd-hackers Subscription results You must GET the form before submitting it.
Close the bug: blisses.org is badly configured. I (jhs@berklix.com) mailed to mason@blisses.org That bounced: ] ----- The following addresses had permanent fatal errors ----- ] <mason@blisses.org> ] (reason: 550 5.7.1 go away) ] ] ----- Transcript of session follows ----- ] ... while talking to phlegethon.blisses.org.: ] >>> DATA ] <<< 550 5.7.1 go away ] 554 5.0.0 Service unavailable I then wrote: To: postmaster@blisses.org That bounced too ] ----- The following addresses had permanent fatal errors ----- ] <postmaster@blisses.org> ] (reason: 550 5.7.1 go away) ] ] ----- Transcript of session follows ----- ] ... while talking to phlegethon.blisses.org.: ] >>> DATA ] <<< 550 5.7.1 go away ] 554 5.0.0 Service unavailable
It's not badly configured at all. One of my users reported abuse from the noted domain, resulting in: header_checks:/^from:.*berklix.com/ REJECT go away What does this have to do with the bug? I'm unaware of berklix.com having anything to do with FreeBSD. Am I incorrect in this belief?
Ah, I see the issue now. A user in that domain reposted private email publically, hence the block. Anyway, the notion of closing this bug because of the issue with abuse from berklix.com is fairly bizarre, and I assume we'll be disregarding the suggestion.
Bliss abuses. My berklix.com has Never spammed anyone, & does not hide domain ownership (unlike blisses.org). Bliss's "One of my users reported" is subterfuge for himself. Bliss is a long forgotten name just found in my ~/.procmailrc discard list. His bug assertion no longer interests me.
(In reply to jhs from comment #4) If you insist I can drag out the complete mail record, which I retained, and put it on record so that folks can decide for themselves whether I was justified in blocking your domain. Rather than a procmail entry, I have the entire enchange saved here. Tell me if this would help. Thanks!
So, a quick search found this: https://mail.python.org/pipermail/mailman-users/2015-April/078945.html Another example of a user reporting it, on another Mailman installation: https://lists.gnu.org/archive/html/bug-parallel/2014-11/msg00006.html I don't think my usage pattern quite matched what was described in the first message, but it seems like the bug is probably not worth significant time to resolve on the FreeBSD side. I'll close or otherwise resolve this as soon as I've learned the best way to leave it as a resource for other folks who might try to report the issue if they see it.
Please keep comments focused only on the issue as reported. In particular, keep any unrelated, personal comments that do not add new information, that helps to isolate, or reproduce the issue, as reported.
FreeBSD is better off this way. Sorry for the bother.