Nicholas D Steeves dixit:
>So it looks to me like this bug fell through the cracks during the
>process of changing submitter of your bugs from the former to the
I didn’t, because I have my From set to the mirbsd.de address for
historical reasons and mailing lists that check the Header-From :/
and changing the address for all bugs, plus the reportbug config
on way too many systems, isn’t worth it. Maintainers are encouraged
to use nnnnnn-submitter@b.d.o anyway.
>who use self-hosted email to work towards DD: eg, then users who
>aren't familiar with advanced BTS use can follow-up on bugs, and reach
>the pkg's maintainer, because the debian.org address forwards it.
No, the BTS can do this, see above.
>> >Would you please test 1.4.2+dfsg-1 currently available in testing and
>> >unstable? I can provide a buster-backport for testing purposes if
>>
>> I can do that, but it’ll probably take me some days, first I
>> need to find that device… (and something to flash).
>
>Thanks, much appreciated! I'm guessing that by now your device could
>use a TWRP upgrade, so maybe that?
It does, but I had to actually *find* it first. I mostly use the
HTC Desire instead because it both works better (especially GPS)
and is smaller than the Note 3.
>It sounds like your greylist could benefit from SPF Record
>updates--either supervised, or automatic, as you prefer.
No, greylisting takes (ip, HELO, MAIL From, RECV To) tuples
and requires them to match in the second connection, then it
updates the firewall so the third connection from that IP
will reach the MTA.
Anyway, back to topic: the TWRP update went problemless,
so the bug can be closed.
Thanks,
//mirabilos
--
"Using Lynx is like wearing a really good pair of shades: cuts out
the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
-- Henry Nelson, March 1999
