[Noffle-devel] [ noffle-Feature Requests-1513395 ] Disable message-id generation
Brought to you by:
bears
From: SourceForge.net <no...@so...> - 2006-07-12 19:28:35
|
Feature Requests item #1513395, was opened at 2006-06-27 15:48 Message generated for change (Comment added) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Priority: 5 Submitted By: Jan De Luyck (devilkin) Assigned to: Jim Hague (bears) Summary: Disable message-id generation Initial Comment: Hello, I've got an account at astraweb, and unfortunately their servers are quite picky on how the message-id must be constructed. I've had trouble in the past with leafnode, and now with noffle, that the server will _not_ accept the msg- id generated by noffle. What I'd like to request is a way to tell noffle to not create a messageid, and just send the message as- is to the upstream server, so that the upstream server will generate a msgid for the message. Ofcourse, this would have to be used together with the post-locally entry, so that they can't be stored in the local spool. Thanks! Jan ---------------------------------------------------------------------- >Comment By: Jim Hague (bears) Date: 2006-07-12 20:28 Message: Logged In: YES user_id=184 Patch now committed. I hope you'll forgive me; I changed message-id to messageid in your config name to be consistent with replace-messageid. ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2006-06-30 20:21 Message: Logged In: YES user_id=184 Semi-broken upstream NNTP servers. Oh, I love them, I do :-( Terrific idea, terrific patch. Simple, effective, neat. Thanks very much indeed; I will commit it the moment I can find the time. I guess I'd better let the world know I've moved the repository to Subversion too. :-) Glad you find the code easy to work with. Markus did an excellent job writing it in the first place, and I've tried to stick to the style he established. ---------------------------------------------------------------------- Comment By: Jan De Luyck (devilkin) Date: 2006-06-27 17:50 Message: Logged In: YES user_id=95363 Unfortunately, I have no clue. Sometimes, after posting the same message again and again for 10-ish times, the server will suddenly accept it. No idea why. The error returned by the astraweb server is: [ NOFFLE: POSTING OF ARTICLE FAILED ] [ The posting of your article failed. ] [ Reason of failure at remote server: ] [ 441 437 Rejected 679 000001 MsgIdMismatch ] [ Full article text has been appended. ] Newsgroups: be.test From: Jan De Luyck <jan...@kc...> Subject: test 2 User-Agent: slrn/0.9.8.1pl1 (Debian) Date: Tue, 27 Jun 2006 16:34:13 +0200 Message-ID: <200...@ru...cks- ass.org> Path: rutabaga.kicks-ass.org!not-for-mail Reply-To: Jan De Luyck <jan...@kc...> 1 2 hupsakdrie -- Linux rutabaga 2.6.17 #1 PREEMPT Mon Jun 19 08:02:42 CEST 2006 i686 GNU/Linux It's a poor workman who blames his tools. . ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2006-06-27 17:27 Message: Logged In: YES user_id=184 I understand the reason for what you want. Ideally I'd prefer to have Noffle generate a message ID acceptable to astraweb. Have you got any clues as to the problem with the Noffle message ID? I can't find any hints on the astraweb site, and I'm pretty sure the message IDs Noffle generates are 100% RFC compliant. If that does prove impossible, then it should be not too difficult to add an option for Noffle to strip out the message ID when forwarding the article upstream. ---------------------------------------------------------------------- Comment By: Jan De Luyck (devilkin) Date: 2006-06-27 17:22 Message: Logged In: YES user_id=95363 I did a bit of a dig through the Noffle sourcecode (it's damn clean code!) of which the Debian Sid packages are made, and this is the patch I came up with. It adds a new configuration option, add-message-id-if- missing (bool), through which you can control if a message id should be generated inside the message, or not. If you pick yes, Noffle works like it used to. If you choose no, it will not store a Message-ID: header in the text, but it will generate one to be able to store it in the outgoing queue. I've tested it locally, works like a charm ehre. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 |