Christoph Groth | 28 Oct 18:19 2015

Message visible in gmane, but does not appear in gmane list archive


The message [1] has been sent simultanously to the two mailing lists [2]
and [3].  While it is visible over NNTP in both groups, the gmane web
interface only shows it for [3].  It can be, however, found also in [2]
when searching for "1.1" for example.

Is this a bug in gmane?


James Sumners | 15 Oct 01:56 2015

ISSUE: gmane.linux.drivers.hostap sending to wrong address

The gmane.linux.drivers.hostap group is sending to the wrong email 
address. It is sending to "hostap <at>" when it should be sending 
to "hostap <at>".
Matthieu Rakotojaona | 29 Sep 21:48 2015

Out of date RSS feeds in Gwene


I've been using Gwene for some time now and realized that gwene.antirez
(linked to isn't updated (last post was 3 days
ago yet gwene.antirez says it was in 2012)

Is there something to do to update feeds that are not updated ?
Gmane-discuss mailing list
Gmane-discuss <at>
Joe | 24 Sep 16:08 2015

Does gmane still send those confirmation required messages?

Note: reposting with old email in the From: header. Because posting to
gmane.discuss with my new email in the From: doesn't seem to work either.
At least I can't find my post, And I waited overnight to allow for any slow
processing... Could be part of same problem????? 

Does gmane have a problem with mail addresses from
I mean it can't be a problem with gmx's sendmail server, when it's an NNTP 
post to a group on gmane that's not getting there right?

 =================== reposted message ===================

My memory is a little vague because it's been a while since I needed to 
post to a group that gmane hadn't confirmed me for. But I remember getting 
something I had to reply to, before gmane would send the post to the actual
mailing list.

But I'm in the process of changing my email. I subscribed to
lyx-users(at) with my new email.
But if I try to post to gmane.editors.lyx.general using it. NOTHING happens.
The post doesn't make it to the list. I don't get any kind of bounce notice
from anybody. I most especially don't get anything from gmane asking me to
confirm my post.

And yes, I checked my spam folders for it...

If I post the same message on gmane using my old, soon to be defunct email,
it gets posted.

If I send a post from my new email, by direct mail to:
(Continue reading)

Oliver.Graute | 24 Sep 15:43 2015

Web Interface still down


since yesterday the webinterface of is not reachable for me.

Couldn't contact ciao:8010
The web interface is down for maintenance.

Best Regards,


Attachment (smime.p7s): application/x-pkcs7-signature, 3315 bytes
Gmane-discuss mailing list
Gmane-discuss <at>
rh_ | 23 Sep 22:13 2015

results of ./

Not a very good report it seems. 
Will try 119 next.

Question for crypto people, should a good client fail if it cannot get a good,
secure connection?


###########################################################       2.6 from    
    (1.379A 2015/09/21 12:03:47)

      This program is free software. Distribution and 
             modification under GPLv2 permitted. 

       Please file bugs  <at>


 Using "OpenSSL 1.0.2-chacha (1.0.2d-dev)" [~181 ciphers] on
 (built: "Jul  6 18:05:33 2015", platform: "linux-x86_64")

Testing now (2015-09-23 13:04) ---> ( <---

 rDNS (
 Service detected:       NNTP, thus skipping HTTP specific checks

--> Testing protocols (via sockets except TLS 1.2 and SPDY/NPN)

 SSLv2      offered (NOT ok) -- 6 ciphers
 SSLv3      offered (NOT ok)
 TLS 1      offered
 TLS 1.1    not offered
 TLS 1.2    not offered (NOT ok)
 SPDY/NPN   not offered

--> Testing ~standard cipher lists

 Null Ciphers                 not offered (OK)
 Anonymous NULL Ciphers       not offered (OK)
 Anonymous DH Ciphers         not offered (OK)
 40 Bit encryption            offered (NOT ok)
 56 Bit encryption            not offered (OK)
 Export Ciphers (general)     offered (NOT ok)
 Low (<=64 Bit)               offered (NOT ok)
 DES Ciphers                  offered (NOT ok)
 Medium grade encryption      offered (NOT ok)
 Triple DES Ciphers           offered (NOT ok)
 High grade encryption        offered (OK)

--> Testing (perfect) forward secrecy, (P)FS -- omitting 3DES, RC4 and Null Encryption here

 PFS is offered (OK)  DHE-RSA-AES256-SHA DHE-RSA-AES128-SHA 

--> Testing server preferences

 Has server cipher order?     nope (NOT ok)
 Negotiated protocol          TLSv1
 Negotiated cipher            DHE-RSA-AES256-SHA, 1024 bit DH (limited sense as client will pick)
 Negotiated cipher per proto  (limited sense as client will pick)
     DHE-RSA-AES256-SHA:            SSLv3, TLSv1
 No further cipher order check has been done as order is determined by the client

--> Testing server defaults (Server Hello)

 TLS server extensions        renegotiation info, session ticket
 Session Tickets RFC 5077     (none)
 Server key size              1024 bit
 Signature Algorithm          SHA1 with RSA
 Fingerprint / Serial         SHA1 92A244DB6E33227E544CC2C17B09A3BE35805F08 / 9398630D3AB6FFD6
                              SHA256 097354CCA18E87A755738247DB2DA256E83B115FB997AC2D7C8EB0824D55A145
 Common Name (CN)    (matches certificate directly)
 subjectAltName (SAN)         -- 
 Issuer              (Gmane from NO)
 EV cert (experimental)       no 
 Certificate Expiration       >= 60 days (2015-01-13 13:13 --> 2018-01-12 13:13 -0800)
 # of certificates provided   1
 Certificate Revocation List  
 OCSP URI                     --
 OCSP stapling                not offered
 TLS clock skew               +314 sec from localtime

--> Testing vulnerabilities

 Heartbleed (CVE-2014-0160)                not vulnerable (OK) (timed out)
 CCS (CVE-2014-0224)                       VULNERABLE (NOT ok)
 Secure Renegotiation (CVE-2009-3555)      not vulnerable (OK)
 Secure Client-Initiated Renegotiation     not vulnerable (OK)
 CRIME, TLS (CVE-2012-4929)                VULNERABLE (NOT ok), but not using HTTP: probably no exploit known
 POODLE, SSL (CVE-2014-3566)               VULNERABLE (NOT ok), uses SSLv3+CBC (check TLS_FALLBACK_SCSV mitigation below)
 TLS_FALLBACK_SCSV (RFC 7507), experim.    Downgrade attack prevention NOT supported
 FREAK (CVE-2015-0204)                     VULNERABLE (NOT ok), uses EXPORT RSA ciphers
 LOGJAM (CVE-2015-4000), experimental      VULNERABLE (NOT ok), uses DHE EXPORT ciphers, common primes not checked.
 BEAST (CVE-2011-3389)                     SSL3: EDH-RSA-DES-CBC3-SHA DES-CBC3-SHA
                                                 EDH-RSA-DES-CBC-SHA DES-CBC-SHA EXP-EDH-RSA-DES-CBC-SHA
                                           TLS1: EDH-RSA-DES-CBC3-SHA DES-CBC3-SHA
                                                 EDH-RSA-DES-CBC-SHA DES-CBC-SHA EXP-EDH-RSA-DES-CBC-SHA
 RC4 (CVE-2013-2566, CVE-2015-2808)        VULNERABLE (NOT ok): RC4-SHA RC4-MD5 RC4-MD5 

--> Testing all locally available 181 ciphers against the server, ordered by encryption strength

Hexcode  Cipher Suite Name (OpenSSL)    KeyExch.   Encryption Bits        Cipher Suite Name (RFC)
 x39     DHE-RSA-AES256-SHA             DH 1024    AES        256         TLS_DHE_RSA_WITH_AES_256_CBC_SHA                  
 x35     AES256-SHA                     RSA        AES        256         TLS_RSA_WITH_AES_256_CBC_SHA                      
 x33     DHE-RSA-AES128-SHA             DH 1024    AES        128         TLS_DHE_RSA_WITH_AES_128_CBC_SHA                  
 x2f     AES128-SHA                     RSA        AES        128         TLS_RSA_WITH_AES_128_CBC_SHA                      
 x05     RC4-SHA                        RSA        RC4        128         TLS_RSA_WITH_RC4_128_SHA                          
 x04     RC4-MD5                        RSA        RC4        128         TLS_RSA_WITH_RC4_128_MD5                          
 x010080 RC4-MD5                        RSA        RC4        128         SSL_CK_RC4_128_WITH_MD5                           
 x16     EDH-RSA-DES-CBC3-SHA           DH 1024    3DES       168         TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA                 
 x0a     DES-CBC3-SHA                   RSA        3DES       168         TLS_RSA_WITH_3DES_EDE_CBC_SHA                     
 x15     EDH-RSA-DES-CBC-SHA            DH 1024    DES        56          TLS_DHE_RSA_WITH_DES_CBC_SHA                      
 x09     DES-CBC-SHA                    RSA        DES        56          TLS_RSA_WITH_DES_CBC_SHA                          
 x14     EXP-EDH-RSA-DES-CBC-SHA        DH(512)    DES        40,export   TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA             

Done now (2015-09-23 13:07) ---> ( <---
Ryan Pavlik | 17 Sep 20:27 2015

Embedding parameters?


I'd like to improve how I'm embedding the gmane recent view in an iframe. 
However, the link (on every group page, and back when the feature was 
added in nov 2010) for parameter help,
output_params=t , returns an effectively empty document - not strictly a 
broken link, but certainly one that isn't doing what it says it will.

I tried searching for more recent information on embedding, but short of 
searching for others doing it and trying their parameters, I don't see any 
docs on making that (very useful) content fit into my site better.


Tim Landscheidt | 10 Sep 22:38 2015

Lines header changed by Gmane or mailman?


I posted the message at via
NNTP to  Gnus saved a copy of the outgoing
message with the header:

| [...]
| Lines: 14
| [...]

and the (outgoing) message body has indeed 14 lines.

If I read the message via NNTP from (doesn't
the web interface show any longer the raw headers?), the
header is now:

| [...]
| Lines: 10
| [...]
| Original-Lines: 14
| X-Mailman-Version: 2.1.13
| [...]

and six lines have been added to the message body (no doubt
by mailman):

| _______________________________________________
| Labs-l mailing list
| Labs-l <at>

giving a total of 20 lines.

Does Gmane fiddle with the Lines header in any way or is
this a bug in mailman?

Sandy Wilkins | 10 Sep 15:05 2015

Request to remove some messages


I've read the FAQs and they state one must email the admin (Lars) to request messages removed.

Is this all that has to be done? How long is the response time on average?


Gmane-discuss mailing list
Gmane-discuss <at>
Lars Magne Ingebrigtsen | 30 Aug 12:48 2015

The Gmane mailing lists are up again

The mailman qrunner thing had apparently crashed some weeks ago, but I
restarted it now, and it sent out lots and lots of email...


(domestic pets only, the antidote for overdose, milk.)
   bloggy blog:
Me | 29 Aug 04:10 2015

Before I file a bug report with reddit...

I just want to make sure I understand the problem.

Error message:
A feed with this internal ID ( is already
subscribed as

(which appears to be a dead group*411, btw)

for rss feed:

which heads like this:
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc=""
    <atom:link rel="self"
    type="application/rss+xml" />

The problem being the <link></link> tag?  But if that is the
problem then according to the spec <link> should point to the url of the
website hosting the rss feed:
"link         The URL to the HTML website corresponding to the channel."

A website like reddit has _many_ offical feeds with a <link> pointing
back to the official website.  If it isn't <link> I can't figure out what
it is.  If it is, I don't understand why the feed url isn't being used 
as an identifier?  

Should link be:
If so, that page is just a subset of the offical site, which also has
a feed with the same simple <link> tag.