Re: Strange problem when posting via news.gmane.org

On Thu, Mar 21, 2013 at 10:44:52AM +0000, Chris Green wrote:
[tin]
> >>> [10:06:10.929393] POST
> <<< [10:06:11.862543] 340 Ok, recommended message-ID <[email protected]>
> nntp_command(POST) OK
> >>> [10:06:11.862679] Path: not-for-mail
> >>> [10:06:11.862711] Message-ID: <[email protected]>
> >>> [10:06:11.862808] Cancel-Lock: sha1:/k5t2HqOu72oRJPt1jhOKam+V5I=
> >>> [10:06:11.862853] From: [email protected]
> >>> [10:06:11.862888] Subject: Attempt another post using tin
> >>> [10:06:11.862920] Newsgroups: gmane.org.clubs.dba.bargelife
> >>> [10:06:11.862952] User-Agent: tin/2.1.1-20120623 ("Mulindry") (UNIX) (Linux/3.5.0-25-generic (x>
> >>> [10:06:11.862985]
> >>> [10:06:11.863020] This is a test with tin's debug turned on
> >>> [10:06:11.863052]
> >>> [10:06:11.863083]
> >>> [10:06:11.863114] --  
> >>> [10:06:11.863145] Chris Green
> >>> [10:06:11.863178] .^M   
> <<< [10:06:12.995709] 240 Article received (mailed to moderator)

[thuderbird]
> 0) Next state: SEND_FIRST_NNTP_COMMAND
> -82385088[7fa2f9e15480]: (7fa2cf033c00) Sending: POST^M
> -82385088[7fa2f9e15480]: (7fa2cf033c00) Next state: NNTP_RESPONSE
> -82385088[7fa2f9e15480]: (7fa2cf033c00) Receiving: 340 Ok, recommended message-ID <kient9$f9i$1@ger>
> -82385088[7fa2f9e15480]: (7fa2cf033c00) Next state: SEND_FIRST_NNTP_COMMAND_RESPONSE
> -82385088[7fa2f9e15480]: (7fa2cf033c00) Next state: SETUP_NEWS_STREAM
> -82385088[7fa2f9e15480]: (7fa2cf033c00) Next state: NNTP_SEND_POST_DATA
> -82385088[7fa2f9e15480]: (7fa2cf033c00) nsNNTPProtocol::PostData()
> -82385088[7fa2f9e15480]: (7fa2cf033c00) Sending: Date: Thu, 21 Mar 2013 10:37:33 +0000^M

thuderbird sends a date header whereas tin does not (Date is arequired
header, but may be left out from the client. in that case the server must
add it). Maybe that's the problem. But I guess the problem is on the
moderators side so the best ist to ask him what's going wrong any why.

there is no easy way to tell tin to send the Date header on its own, but it
can be achieved via the attributes machanism (see tin(5)) with someting
like the following in ${TIN_HOMEDIR:-"$HOME"}/.tin/attributes (gnu-date
assumed):

scope=gmane.org.clubs.dba.*
x_headers=!LC_MESSAGES=C date -u +"Date: %%d %%b %%Y %%T %%Z"

> I'm pretty certain the problem is that the DBA site isn't handling the
> LF only line endings from tin.

tin uses \r\n but only shows \n in the logs (to make things more readable).
see nntplib.c:put_server():

[...]
        if (*string && strlen(string)) {
                DEBUG_IO((stderr, "put_server(%s)\n", string));
                s_puts(string, nntp_wr_fp);
                s_puts("\r\n", nntp_wr_fp);
#       ifdef DEBUG
                if (debug & DEBUG_NNTP)
                        debug_print_file("NNTP", ">>>%s%s", logtime(), string);
#       endif /* DEBUG */

[...]

urs
-- 
"Only whimps use tape backup: _real_ men just upload their important stuff
 on ftp, and let the rest of the world mirror it ;)" - Linus