Closed Bug 32922 Opened 24 years ago Closed 20 years ago

bidirectional gateway deletes lines from messages

Categories

(mozilla.org Graveyard :: Server Operations, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: erik, Unassigned)

References

Details

Please use Bugzilla. The person taking care of news.mozilla.org is not reading
staff@mozilla.org.

Risto

Erik van der Poel wrote:

> Hi Staff at Mozilla dot Org,
>
> I'm forwarding another instance of the newsgroup -> mailing list bug. In
> this case, there is no colon (:) in the first line. There are a few
> spaces at the beginning of the line. I'm forwarding both the newsgroup
> and mailing list version of the message.
>
> Thanks for looking into it,
>
> Erik
>
>   ------------------------------------------------------------------------
>
> Subject: font selection interface
> Date: 22 Mar 2000 17:40:55 GMT
> From: Jungshik Shin <jshin@pantheon.yale.edu>
> Organization: Yale University, Physics Dept.
> Newsgroups: netscape.public.mozilla.i18n
>
>    In Netscape 4.x/3.x for Unix/X11, only fonts relevant to the
> language/encoding currently selected show up in the font selection menu.
> On the other hand, MacOS/MS-Windows version of NS 4.x/3.x list all
> the fonts available whatever lang./encoding/script you specify for
> font selection.  As of 2000-03-21-09 build, Mozilla for Unix/X11 also
> enumerates all the fonts available regardless of the language/encoding
> selected. I guess that this problem is well known and that it's just
> left as it is now for the moment only.
>
>   More serious problem is that only the second element of
> XLFD is listed in the font selection menu. There are some fonts sharing
> the second element but otherwise different. For instance, I've got
> 4 different sets of  'gothic' fonts from different sources(three of
> them are in ksc5601.1987-0 encoding and the fourth one is in Hangul
> Johab) and there's no way to tell which one will be used if I select
> 'gothic'. It seems like at least the first(foundry), the second and the
> last (the encoding) element have to be listed in the font selection menu.
>
>  It just occurred to me that this has something to do with the way
> that fonts are dealt with in CSS(and/or XML?). .........
>
>      Jungshik Shin
>
>   ------------------------------------------------------------------------
>
> Subject: font selection interface
> Resent-Date: Wed, 22 Mar 2000 09:42:10 -0800 (PST)
> Resent-From: mozilla-i18n@mozilla.org
> Date: 22 Mar 2000 17:40:55 GMT
> From: Jungshik Shin <jshin@pantheon.yale.edu>
> Organization: Yale University, Physics Dept.
> To: mozilla-i18n@mozilla.org
> Newsgroups: netscape.public.mozilla.i18n
>
> language/encoding currently selected show up in the font selection menu.
> On the other hand, MacOS/MS-Windows version of NS 4.x/3.x list all
> the fonts available whatever lang./encoding/script you specify for
> font selection.  As of 2000-03-21-09 build, Mozilla for Unix/X11 also
> enumerates all the fonts available regardless of the language/encoding
> selected. I guess that this problem is well known and that it's just
> left as it is now for the moment only.
>
>   More serious problem is that only the second element of
> XLFD is listed in the font selection menu. There are some fonts sharing
> the second element but otherwise different. For instance, I've got
> 4 different sets of  'gothic' fonts from different sources(three of
> them are in ksc5601.1987-0 encoding and the fourth one is in Hangul
> Johab) and there's no way to tell which one will be used if I select
> 'gothic'. It seems like at least the first(foundry), the second and the
> last (the encoding) element have to be listed in the font selection menu.
>
>  It just occurred to me that this has something to do with the way
> that fonts are dealt with in CSS(and/or XML?). .........
>
>      Jungshik Shin
Marya, could you look into this?
Assignee: rko → maryag
Target Milestone: ---
this is a known problem with mail gateway. Its not properly parsing the
header and deletes any lines at the top of the message that begin with
(\w?:) because it thinks they are mail headers. So, if the first line
of your message is an URL or "About:" then you're out of luck. Big bribes
to anyone who finally fixes this annoying problem.  =) 
I think dmose is the author of the gateway... moving this to him. Or is this 
component one of collabra/INN tools?
Assignee: maryag → dmose
I just did some testing, and it seems that the problem is in the news->mail
gateway (which is part of collabra itself) rather than the mail->news gateway
that I maintained.

As I understand it, it is not likely that there will ever be another Collabra
release.  Last I heard, IS was considering at some point moving away from
Collabra towards INN.  Marya, is that still the plan?  Any idea on an
approximate timeframe?
Assignee: dmose → maryag
Well, we had actually only planned to move to INN for some parts of our news
structure (those that need to handle the full feed from the outside world.)  We
were going to stick with collabra for our internal news and the netscape.public
stuff, so that they could still take advantage collabra features such as
categorized newsgroups, pretty names, and access control.  Perhaps we should
reconsider?  In any case we are waiting for some new hardware etc so this would
not be happening for another couple of months I think.
Status: NEW → ASSIGNED
Well, the mozilla groups don't need any of those special features.  And I
suspect that the lack of support for collabra will only hurt more as time goes
on and new technologies (eg for spam control) that we want are integrated into
INN.  Certainly this bug is annoying, and having it never be fixed seems like a
bad thing.  So having at least the mozilla groups move to a more modern server
would be a desirable thing, I think.

Yes, please fix this bug at least for the netscape.public.mozilla.* newsgroups.
These are public, high-volume newsgroups. Misunderstandings arise when some
lines are deleted from messages. It hurts productivity. Yes, the newsgroups are
part of our work! Please, please fix this soon. Thanks in advance!
If you guys want to move to an INN server that is great.  I will add that to our
current proposal.  As I said though, the migration will not be happening for at
least a couple of months.
transfering to mbaur since I will no longer be handling netscape news stuff...
thanks!  marya
Assignee: maryag → mbaur
Status: ASSIGNED → NEW
I'm tired of waiting for new hardware. Anything's better than this crappy old
Sparc20 with plain disk. An Ultra-1 with diskpack will do much better until we
get something else.
`
Status: NEW → ASSIGNED
Moving to nobody until we have better picture of where we'll be going with 
mozilla.org support by IC.
Assignee: mbaur → nobody
Status: ASSIGNED → NEW
this will get fixed by the move to the new mail server and switch to INN.
Depends on: 62228
Blocks: 62228
No longer depends on: 62228
Does anyone know what is going on with this?
This should have been fixed by the move from SmartList to MailMan.  Someone
reopen this if that's not the case.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.