The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

Hi Sabine,

Funny, I'm working on this exact problem right now.

Here are the problems I found until now :

1- the access authorization to urlized documents is regulated by the 
archive_webaccess scenario, which is wrong: people need to authenticate 
to get the document. We should either:

    - use another scenario

    - or simply the urlized docuemnts freely available,

    - or just check whether the user is susbscribed to the list.

I'd rather use the second option but forcnig users to authenticate can 
be too limitative.

For now, I added the following line to the archive_webaccess scenario:

            match([env->REQUEST_URI], /attach/) md5,smime -> do_it

2- In some cases, the entire mail is urlized (and produces the ".bin" 
attachment you found). It is because the first thing made by the 
_urlize_part function is to check whether the entity being urlized is in 
Multipart/mixed. And it urlizes its content. When a mail is directly in 
multipart/alternative, the entire mail is considered as an attachment 
and urlized. I still don't know how to fix it but I'm working on it.

3- when an attachment contains a character that needs escaping, the "@" 
in the file name is escaped too. It should not, as "@" can be used 
directly in URL. Consequently, the file becomes unreachable.

I'm working on it because I would like, for environmental reasons, for 
all list on some servers to be in urlize mode by defautl, instead of 
"mail" mode.

More news soon, I hope.


Best regards,

David

On 17/10/2019 12:30, Lorenz, Sabine (SCC) wrote:
> Hi all,
>
> I received this e-mail from the list address@concealed, where I 
> am registered with the option urlize.
>
> Apparently the URL mode does not work correctly, because neither of the two 
> links given in the mail works correctly.
>
> Neither the link given in the text of the mail nor the link contained in the 
> attachment of the mail can be called up:
> https://listes.renater.fr/sympa/attach/sympa-users/CY4PR1101MB2231B8AB426DCACE1445FD90B5920%40CY4PR1101MB2231.namprd11.prod.outlook.
> com/msg.0.bin
> https://listes.renater.fr/sympa/attach/sympa-users/CY4PR1101MB2231B8AB426DCACE1445FD90B5920%40CY4PR1101MB2231.namprd11.prod.outlook.
> com/my.cnf-MySQL%2520config%2520optimized%2520for%2520Sympa.pdf
>
> Both links provide error messages.
> We also have this problem on our mailing list server (Sympa 6.2.16). Since 
> the problem also occurs with your own mailing list, it
> seems to be a general problem and not a problem with our Sympa instance.
> Does anyone have an idea how to fix this problem or is the problem known?
> Or should I report the problem as a bug in Github?
>
> Best regards,
> Sabine Lorenz
>
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: address@concealed 
> [mailto:address@concealed] Im Auftrag von McLaren, Terry
> Gesendet: Mittwoch, 16. Oktober 2019 16:35
> An: Kazim Koybasi <address@concealed>
> Cc: address@concealed
> Betreff: RE: [sympa-users] Slowness at sympa web interface
>
> The msg_0_bin file that was initially attached to this message has been 
> stored on the mailing lists server:
> https://listes.renater.fr/sympa/attach/sympa-users/CY4PR1101MB2231B8AB426DCACE1445FD90B5920%40CY4PR1101MB2231.namprd11.prod.outlook.
> com/msg.0.bin

--
"Mieux vaut viser la perfection et la rater que viser la médiocrité et 
l'atteindre."
- Francis Blanche

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature