Scambled German umlauts when replying to and forwarding mails

[Martin Sebald]

Hello all,

I'm sure this is a common problem and has nothing to do with plugins but I
want to place this here anyway.

When replying to mails or forwarding mails German umlauts get scrambled.

Before in the original mail:

> Jürgen
> daß

In the reply:

> Jürgen
> daß

This affects not only the text in the message field itself but also the TO
and Subject fields.

Can anybody help?

Kindest regards,
Martin


------------------------------------------------------------------------------
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Tomas Kuliavas]

Martin Sebald wrote:

Hello all,

I'm sure this is a common problem and has nothing to do with plugins but I
want to place this here anyway.

When replying to mails or forwarding mails German umlauts get scrambled.

Before in the original mail:

> Jürgen
> daß

In the reply:

> Jürgen
> daß

This affects not only the text in the message field itself but also the TO
and Subject fields.

Can anybody help?

Turn on lossy encoding in SquirrelMail configuration or switch translation to utf-8.

[Martin Sebald]

Hello Tomas!

> Turn on lossy encoding in SquirrelMail configuration or switch
> translation to utf-8.

Great, worked great!

Translation was on iso-8859-1 and lossy encoding was of. I turned
translation to utf-8 and turned lossy encoding on.

Is there a problem changing both values?

Regards,
Martin


------------------------------------------------------------------------------
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Tomas Kuliavas]

Martin Sebald wrote:

Hello Tomas!

> Turn on lossy encoding in SquirrelMail configuration or switch
> translation to utf-8.

Great, worked great!

Translation was on iso-8859-1 and lossy encoding was of. I turned
translation to utf-8 and turned lossy encoding on.

Is there a problem changing both values?

Default charset option is applied only to US English translation. German translation is still running in ISO-8859-1 and you will have issues with euro. Changing default charset value does not convert translation to utf-8.

These settings are not related. Your problem with umlauts was fixed, because when user replies or forwards email, charset conversion is applied only in utf-8 translations, in some input and output charset combinations and when lossy encoding option is turned on.

--
Tomas

[Martin Sebald]

Hello all,

after I turned on lossy encoding in SquirrelMail configuration the umlaut
problem was solved for most mails. But I experienced that in some mails it
does not work. Instead of scambled umlauts like ü instead of ü I now see
questionmarks instead of every umlaut in the reply field.

I noticed that in the original mail the header just shows:

> Content-type: text/plain

and not like in other mails where it works something like this:

> Content-Type: text/plain;
>      charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> Content-Language: de

Is it possible that the missing of a charset (I don't think that it makes a
difference if the charset is iso-8859 or utf-8) and the other information
given screws up SquirrelMail?

Regards,
Martin


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Fredrik Jervfors-4]

> after I turned on lossy encoding in SquirrelMail configuration the umlaut
> problem was solved for most mails. But I experienced that in some mails
> it does not work. Instead of scambled umlauts like ü instead of ü I now
> see questionmarks instead of every umlaut in the reply field.

The question marks are what the lossy encoding does when it finds encoding
that doesn't make sense in the context.

> I noticed that in the original mail the header just shows:
>
>> Content-type: text/plain
>
> and not like in other mails where it works something like this:
>
>> Content-Type: text/plain; charset="iso-8859-1"
>> Content-Transfer-Encoding: quoted-printable
>> Content-Language: de
>
> Is it possible that the missing of a charset (I don't think that it makes
> a difference if the charset is iso-8859 or utf-8) and the other
> information given screws up SquirrelMail?

SquirrelMail depends on the meta data specified in the RfCs to be there.
If it's not, SquirrelMail has to make a guess how the sender of the mail
intended the information to be structured. So yes, I think you've come to
the right conclusion.

Possible ways to go:

1. Fix the broken mailer.

2. Make a plugin with a great guessing algorithm and install it (and share
it with the rest of us).

Sincerely,
Fredrik

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Tomas Kuliavas]

2009.06.10 13:52 Martin Sebald rašė:

> Hello all,
>
> after I turned on lossy encoding in SquirrelMail configuration the umlaut
> problem was solved for most mails. But I experienced that in some mails it
> does not work. Instead of scambled umlauts like ?? instead of ? I now see
> questionmarks instead of every umlaut in the reply field.
>
> I noticed that in the original mail the header just shows:
>
>> Content-type: text/plain
>
> and not like in other mails where it works something like this:
>
>> Content-Type: text/plain;
>>      charset="iso-8859-1"
>> Content-Transfer-Encoding: quoted-printable
>> Content-Language: de
>
> Is it possible that the missing of a charset (I don't think that it makes
> a
> difference if the charset is iso-8859 or utf-8) and the other information
> given screws up SquirrelMail?

Are these emails displayed correctly?

Do they have a MIME-Version header?

--
Tomas



------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Martin Sebald]

Hello Tomas!

>> after I turned on lossy encoding in SquirrelMail configuration the
>> umlaut problem was solved for most mails. But I experienced that in some
>> mails it does not work. Instead of scambled umlauts like ?? instead of ?
>> I now see questionmarks instead of every umlaut in the reply field.
>> I noticed that in the original mail the header just shows:
>>> Content-type: text/plain
>> and not like in other mails where it works something like this:
>>> Content-Type: text/plain;
>>>      charset="iso-8859-1"
>>> Content-Transfer-Encoding: quoted-printable
>>> Content-Language: de
>> Is it possible that the missing of a charset (I don't think that it
>> makes a difference if the charset is iso-8859 or utf-8) and the other
>> information given screws up SquirrelMail?
> Are these emails displayed correctly?

Yes. I see all umlauts when opening these mails in SquirrelMail. The
questionmarks just appear when replying or forwarding.

> Do they have a MIME-Version header?

No. Nothing.

Most of those mails are mails from robots like contact forms so I believe
that the authors of those programs did not care about correct mail headers.
Though most mail clients like TheBat! are able to reply without crambling
the umlauts. So it seems to be possible.

@ Fredrik: As nobody can change things out of his/her competence (external
servers somewhere in the internet) I thought focusing on the thing I can
change is the best way to handle this. ;-) As I cannot do any programming I
bring this to the attention of the people here. At least I can do this
because I believe that every SM user and therefore every SM administrator
should have the same problem.

Kindest regards,
Martin


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Fredrik Jervfors-4]

>>> after I turned on lossy encoding in SquirrelMail configuration the
>>> umlaut problem was solved for most mails. But I experienced that in
>>> some mails it does not work. Instead of scambled umlauts like ??
>>> instead of ? I now see questionmarks instead of every umlaut in the
>>> reply field. I noticed that in the original mail the header just
>>> shows:
>>>
>>>> Content-type: text/plain
>>>
>>> and not like in other mails where it works something like this:
>>>
>>>> Content-Type: text/plain;
>>>> charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
>>>> Content-Language: de
>>>
>>> Is it possible that the missing of a charset (I don't think that it
>>> makes a difference if the charset is iso-8859 or utf-8) and the other
>>> information given screws up SquirrelMail?
>>
>> Are these emails displayed correctly?
>
> Yes. I see all umlauts when opening these mails in SquirrelMail. The
> questionmarks just appear when replying or forwarding.

Ah. I didn't understand this until now.

>> Do they have a MIME-Version header?
>
> No. Nothing.
>
> Most of those mails are mails from robots like contact forms so I believe
> that the authors of those programs did not care about correct mail
> headers. Though most mail clients like TheBat! are able to reply without
> crambling the umlauts. So it seems to be possible.
>
> @ Fredrik: As nobody can change things out of his/her competence
> (external servers somewhere in the internet) I thought focusing on the
> thing I can change is the best way to handle this. ;-)

Well if it were a "real" mail program one could file a bug report, but if
it's sloppy web forms I guess this is not a path one could choose. :(

> As I cannot do any programming I bring this to the attention of the
> people here. At least I can do this because I believe that every SM user
> and therefore every SM administrator should have the same problem.

I haven't looked at the lossy encoding code at all, so I don't know how it
works in detail. It would be best if Tomas can help out and mail a patch
if a bug is found. I don't know when I can do anything about this on my
own. :(

Sincerely,
Fredrik

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Tomas Kuliavas]

Martin Sebald wrote:

Hello Tomas!

>> after I turned on lossy encoding in SquirrelMail configuration the
>> umlaut problem was solved for most mails. But I experienced that in some
>> mails it does not work. Instead of scambled umlauts like ?? instead of ?
>> I now see questionmarks instead of every umlaut in the reply field.
>> I noticed that in the original mail the header just shows:
>>> Content-type: text/plain
>> and not like in other mails where it works something like this:
>>> Content-Type: text/plain;
>>>      charset="iso-8859-1"
>>> Content-Transfer-Encoding: quoted-printable
>>> Content-Language: de
>> Is it possible that the missing of a charset (I don't think that it
>> makes a difference if the charset is iso-8859 or utf-8) and the other
>> information given screws up SquirrelMail?
> Are these emails displayed correctly?

Yes. I see all umlauts when opening these mails in SquirrelMail. The
questionmarks just appear when replying or forwarding.

Are you sure that we are talking about some plain text emails and not about html formated emails?

Have you installed view_as_html plugin?

Martin Sebald wrote:

> Do they have a MIME-Version header?

No. Nothing.

Most of those mails are mails from robots like contact forms so I believe
that the authors of those programs did not care about correct mail headers.
Though most mail clients like TheBat! are able to reply without crambling
the umlauts. So it seems to be possible.

There you go. One of the most common RFC 2045 violations. If MIME-Version header is not set, RFC 2045 complaint software should ignore Content-Type headers.

Most email clients have their own email structure parsers and some of them apply incorrect default charset or ignore RFC2045 chapter 4 violation. SquirrelMail asks IMAP server to parse email structure. Any sane parser would check for MIME-Version before reading whole email and wouldn't waste time in processing of email structure, when this header is missing. RFC 2045 says that header is required. If header is missing, email is not formated according to RFC 2045 and should be handled as plain text email in US-ASCII charset.

Ask developers of those buggy web forms to fix their scripts.

--
Tomas

[Hans-Juergen Beie]

Martin Sebald schrieb am 11.06.2009 14:34 Uhr:

> Hello Tomas!
>
>>> after I turned on lossy encoding in SquirrelMail configuration the
>>> umlaut problem was solved for most mails. But I experienced that in some
>>> mails it does not work. Instead of scambled umlauts like ?? instead of ?
>>> I now see questionmarks instead of every umlaut in the reply field.
>>> I noticed that in the original mail the header just shows:
>>>> Content-type: text/plain
>>> and not like in other mails where it works something like this:
>>>> Content-Type: text/plain;
>>>>      charset="iso-8859-1"
>>>> Content-Transfer-Encoding: quoted-printable
>>>> Content-Language: de
>>> Is it possible that the missing of a charset (I don't think that it
>>> makes a difference if the charset is iso-8859 or utf-8) and the other
>>> information given screws up SquirrelMail?
>> Are these emails displayed correctly?
>
> Yes. I see all umlauts when opening these mails in SquirrelMail. The
> questionmarks just appear when replying or forwarding.
>
>> Do they have a MIME-Version header?
>
> No. Nothing.
>
> Most of those mails are mails from robots like contact forms so I believe
> that the authors of those programs did not care about correct mail headers.
> Though most mail clients like TheBat! are able to reply without crambling
> the umlauts. So it seems to be possible.
>
> @ Fredrik: As nobody can change things out of his/her competence (external
> servers somewhere in the internet) I thought focusing on the thing I can
> change is the best way to handle this. ;-) As I cannot do any programming I
> bring this to the attention of the people here. At least I can do this
> because I believe that every SM user and therefore every SM administrator
> should have the same problem.
>
> Kindest regards,
> Martin

I had this effect with replying to mails originally sent with
   Content-Type: text/plain;
          charset="utf-8"

Changing the 'Default Charset' via config.pl or
$default_charset in config.php doesn't fix this issue.

Today, I changed the following lines in functions/i18n.php:
-----> cut here >-------------------------
/*
$languages['de_DE']['NAME']='Deutsch';
$languages['de_DE']['CHARSET']='iso-8859-1';
$languages['de_DE']['LOCALE']=array('de_DE.ISO8859-1','de_DE.ISO-8859-1','de_DE');
$languages['de']['ALIAS']='de_DE';
*/
$languages['de_DE']['NAME']    = 'Deutsch';
$languages['de_DE']['CHARSET'] = 'utf-8';
$languages['de_DE']['LOCALE']  = array('de_DE.UTF-8','de_DE');
$languages['de']['ALIAS']      = 'de_DE';
-----< cut here <-------------------------

Now it seems to work.

BTW: I'm talkig about squirrelmail-1.4.15-2 on debian/etch.

hjb :-?
--
Hans-Juergen Beie
mailto:hjb@...


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Tomas Kuliavas]

2009.06.16 22:35 Hans-Juergen Beie rašė:

> Martin Sebald schrieb am 11.06.2009 14:34 Uhr:
>> Hello Tomas!
>>
>>>> after I turned on lossy encoding in SquirrelMail configuration the
>>>> umlaut problem was solved for most mails. But I experienced that in
>>>> some
>>>> mails it does not work. Instead of scambled umlauts like ?? instead of
>>>> ?
>>>> I now see questionmarks instead of every umlaut in the reply field.
>>>> I noticed that in the original mail the header just shows:
>>>>> Content-type: text/plain
>>>> and not like in other mails where it works something like this:
>>>>> Content-Type: text/plain;
>>>>>      charset="iso-8859-1"
>>>>> Content-Transfer-Encoding: quoted-printable
>>>>> Content-Language: de
>>>> Is it possible that the missing of a charset (I don't think that it
>>>> makes a difference if the charset is iso-8859 or utf-8) and the other
>>>> information given screws up SquirrelMail?
>>> Are these emails displayed correctly?
>>
>> Yes. I see all umlauts when opening these mails in SquirrelMail. The
>> questionmarks just appear when replying or forwarding.
>>
>>> Do they have a MIME-Version header?
>>
>> No. Nothing.
>>
>> Most of those mails are mails from robots like contact forms so I
>> believe
>> that the authors of those programs did not care about correct mail
>> headers.
>> Though most mail clients like TheBat! are able to reply without
>> crambling
>> the umlauts. So it seems to be possible.
>>
>> @ Fredrik: As nobody can change things out of his/her competence
>> (external
>> servers somewhere in the internet) I thought focusing on the thing I can
>> change is the best way to handle this. ;-) As I cannot do any
>> programming I
>> bring this to the attention of the people here. At least I can do this
>> because I believe that every SM user and therefore every SM
>> administrator
>> should have the same problem.
>>
>> Kindest regards,
>> Martin
>
> I had this effect with replying to mails originally sent with
>    Content-Type: text/plain;
>  charset="utf-8"
>
> Changing the 'Default Charset' via config.pl or
> $default_charset in config.php doesn't fix this issue.

$default_charset is used only with US English translation. It is ignored,
when user uses any other translation.

> Today, I changed the following lines in functions/i18n.php:
> -----> cut here >-------------------------
> /*
> $languages['de_DE']['NAME']='Deutsch';
> $languages['de_DE']['CHARSET']='iso-8859-1';
> $languages['de_DE']['LOCALE']=array('de_DE.ISO8859-1','de_DE.ISO-8859-1','de_DE');
> $languages['de']['ALIAS']='de_DE';
> */
> $languages['de_DE']['NAME']    = 'Deutsch';
> $languages['de_DE']['CHARSET'] = 'utf-8';
> $languages['de_DE']['LOCALE']  = array('de_DE.UTF-8','de_DE');
> $languages['de']['ALIAS']      = 'de_DE';
> -----< cut here <-------------------------
>
> Now it seems to work.

So you've converted German translation to utf-8 and it fixed all issues.
Are you sure that lossy encoding was turned on?

Please note that you forgot to convert help files. They are still in
ISO-8859-1.

--
Tomas



------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[Hans-Juergen Beie]

Tomas Kuliavas schrieb am 19.06.2009 12:18 Uhr:

> 2009.06.16 22:35 Hans-Juergen Beie rašė:
>> Martin Sebald schrieb am 11.06.2009 14:34 Uhr:
>>> Hello Tomas!
>>>
>>>>> after I turned on lossy encoding in SquirrelMail configuration the
>>>>> umlaut problem was solved for most mails. But I experienced that in
>>>>> some
>>>>> mails it does not work. Instead of scambled umlauts like ?? instead of
>>>>> ?
>>>>> I now see questionmarks instead of every umlaut in the reply field.
>>>>> I noticed that in the original mail the header just shows:
>>>>>> Content-type: text/plain
>>>>> and not like in other mails where it works something like this:
>>>>>> Content-Type: text/plain;
>>>>>>      charset="iso-8859-1"
>>>>>> Content-Transfer-Encoding: quoted-printable
>>>>>> Content-Language: de
>>>>> Is it possible that the missing of a charset (I don't think that it
>>>>> makes a difference if the charset is iso-8859 or utf-8) and the other
>>>>> information given screws up SquirrelMail?
>>>> Are these emails displayed correctly?
>>> Yes. I see all umlauts when opening these mails in SquirrelMail. The
>>> questionmarks just appear when replying or forwarding.
>>>
>>>> Do they have a MIME-Version header?
>>> No. Nothing.
>>>
>>> Most of those mails are mails from robots like contact forms so I
>>> believe
>>> that the authors of those programs did not care about correct mail
>>> headers.
>>> Though most mail clients like TheBat! are able to reply without
>>> crambling
>>> the umlauts. So it seems to be possible.
>>>
>>> @ Fredrik: As nobody can change things out of his/her competence
>>> (external
>>> servers somewhere in the internet) I thought focusing on the thing I can
>>> change is the best way to handle this. ;-) As I cannot do any
>>> programming I
>>> bring this to the attention of the people here. At least I can do this
>>> because I believe that every SM user and therefore every SM
>>> administrator
>>> should have the same problem.
>>>
>>> Kindest regards,
>>> Martin
>> I had this effect with replying to mails originally sent with
>>    Content-Type: text/plain;
>>  charset="utf-8"
>>
>> Changing the 'Default Charset' via config.pl or
>> $default_charset in config.php doesn't fix this issue.
>
> $default_charset is used only with US English translation. It is ignored,
> when user uses any other translation.
>
>> Today, I changed the following lines in functions/i18n.php:
>> -----> cut here >-------------------------
>> /*
>> $languages['de_DE']['NAME']='Deutsch';
>> $languages['de_DE']['CHARSET']='iso-8859-1';
>> $languages['de_DE']['LOCALE']=array('de_DE.ISO8859-1','de_DE.ISO-8859-1','de_DE');
>> $languages['de']['ALIAS']='de_DE';
>> */
>> $languages['de_DE']['NAME']    = 'Deutsch';
>> $languages['de_DE']['CHARSET'] = 'utf-8';
>> $languages['de_DE']['LOCALE']  = array('de_DE.UTF-8','de_DE');
>> $languages['de']['ALIAS']      = 'de_DE';
>> -----< cut here <-------------------------
>>
>> Now it seems to work.
>
> So you've converted German translation to utf-8 and it fixed all issues.
> Are you sure that lossy encoding was turned on?

Yes and no. I didn't notice any difference up to now.

> Please note that you forgot to convert help files. They are still in
> ISO-8859-1.

Indeed, I didn't think of that. But it appears not to be necessary,
because all non-ascii characters in the help files seem to be in &...;
notation.

The only (new) issue is now: umlauts in my address book are now
"wrongly" encoded.

hjb :-?



------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins