http://permalink.gmane.org/gmane.mail.sympa.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.mail.sympa.user/1355 <pre>Your are subscriber of list sympa-users-wA9P2NSfqiUqvlmFElCZGVAUjnlXr6A1&lt; at &gt;public.gmane.org with email gmsu- sympa-users&lt; at &gt;m.gmane.org Everything about this list: https://listes.renater.fr/sympa/info/sympa-users Unsubscription: mailto:sympa-wA9P2NSfqiUqvlmFElCZGVAUjnlXr6A1&lt; at &gt;public.gmane.org?subject=sig%20sympa-users%20gmsu-sympa-users%40m.gmane.org </pre> sympa-users-request-wA9P2NSfqiUqvlmFElCZGVAUjnlXr6A1< at >public.gmane.org 2013-06-14T11:17:47 http://permalink.gmane.org/gmane.mail.sympa.user/1354 <pre>Your are subscriber of list sympa-users-wA9P2NSfqiUqvlmFElCZGVAUjnlXr6A1&lt; at &gt;public.gmane.org with email gmsu- sympa-users&lt; at &gt;m.gmane.org Everything about this list: https://listes.renater.fr/sympa/info/sympa-users Unsubscription: mailto:sympa-wA9P2NSfqiUqvlmFElCZGVAUjnlXr6A1&lt; at &gt;public.gmane.org?subject=sig%20sympa-users%20gmsu-sympa-users%40m.gmane.org </pre> sympa-users-request-wA9P2NSfqiUqvlmFElCZGVAUjnlXr6A1< at >public.gmane.org 2013-06-13T13:52:03 http://permalink.gmane.org/gmane.mail.sympa.user/1353 <pre> If you create the list using a custom template, you should be able to set the template's config.tt2 to have anything you want in the owner field. Customise create_list_request.tt2 to add a new data entry field (we've done this, but for a different reason) and then customise the config.tt2 in your template to use this field rather than the 'owner' variable. Of course, this would be open to abuse and so on... Yes, of course. Just set the subscribe scenario appropriately. The 'owner' subscription scenario is likely what you want, but far more complex ones can be made -- for example, we have one that will let staff members subscribe without approval if they are on campus or are using an S/MIME signature; otherwise they need approval from owner or moderator. Other people are not allowed to subscribe. You have very detailed control over if they are using web or email to subscribe; where they are; how they authenticate; and so on - take a look in the Sympa docco online under scenari. Steve Steve Shipway</pre> Steve Shipway 2013-06-12T22:35:10 http://permalink.gmane.org/gmane.mail.sympa.user/1352 <pre>Hi Olaf, Thanks for the quick reply &amp; the suggestions. Great tip creating a template, took me a while to figure it out, but very handy for creating new lists. Eventually I managed to hack create_list_request.tt2 &amp; wwsympa.fcgi to allow an owner's email address to be specified on creation. Please bear in mind this was a quick fix &amp; I'm not sure if it would have adverse effects later. However I've confirmed that the entry registers correctly in the database &amp; with Sympa. I'll test this more extensively, Regards, Adrian O' Riordan CAD/Engineering IS System Admin Ext : 4451 Email:  adrian.oriordan-OyLXuOCK7orQT0dZR+AlfA&lt; at &gt;public.gmane.org -----Original Message----- From: Menkens Olaf [mailto:olaf.menkens-wAlPVner0lqatNDF+KUbs4QuADTiUCJX&lt; at &gt;public.gmane.org] Sent: 12 June 2013 09:09 To: ORiordan, Adrian Subject: AW: [sympa-users] Sympa Create List/ List Owner Questions Hi Adrian, afaik you cannot specify the list owner during creation, but you can change the list owner or add more list owners via the web int</pre> ORiordan, Adrian 2013-06-12T09:12:36 http://permalink.gmane.org/gmane.mail.sympa.user/1351 <pre>Hi all, Recently I've started using Sympa as our mail list manager on a local sub-net. It's a great piece of software, very well written. I've come across a couple issues I'd like to resolve, hopefully with your guys help. Firstly, is it possible to specify the list owner when Creating a List using the web interface? At the moment, the owner address is automatically parsed to the logged in person. In the create_list_request.tt2 file the lines : &lt;strong&gt;[%|loc%]Owner:[%END%]&lt;/strong&gt; &lt;em&gt;[% user.email %]&lt;/em&gt;&lt;br /&gt; Can this be modified to allow entering of a list owner's email address? Also is it possible to have subscriptions confirmed by the list owner? Subscriptions would be submitted through the web interface &amp; allowed/denied by the list owner. Thanks for your help, Regards, Adrian </pre> adrian.oriordan-OyLXuOCK7orQT0dZR+AlfA< at >public.gmane.org 2013-06-12T07:44:43 http://permalink.gmane.org/gmane.mail.sympa.user/1350 <pre>I created a custom list action page that would delete ALL list members; you could do something similar to zap by regexp, if you want? I can send you a copy of the web_tt2 script if you'd like. Steve Steve Shipway University of Auckland ITS UNIX Systems Design Lead s.shipway-1/NbpDiVQt6SYBAHRPvY1A&lt; at &gt;public.gmane.org Ph: +64 9 373 7599 ext 86487 ________________________________________ From: sympa-users-request-wA9P2NSfqiUqvlmFElCZGVAUjnlXr6A1&lt; at &gt;public.gmane.org [sympa-users-request&lt; at &gt;listes.renater.fr] on behalf of Cyril Sarrauste de Menthière [Cyril.Sarrauste&lt; at &gt;igh.cnrs.fr] Sent: Friday, 7 June 2013 6:57 p.m. To: sympa-users-wA9P2NSfqiUqvlmFElCZGVAUjnlXr6A1&lt; at &gt;public.gmane.org Subject: [sympa-users] SYMPA commands by email Sorry for my previous messages in French. ;-) Is there any wildcards characters in order to use SYMPA commands by email, for exemple to bulk delete : DEL &lt;list&gt; *&lt; at &gt;igh.cnrs.fr or something like that ? Thanks Cyril -- Cyril Sarrauste de Menthière Institute of Human Genetics CNRS UPR 1142 - </pre> Steve Shipway 2013-06-08T06:51:39 http://permalink.gmane.org/gmane.mail.sympa.user/1349 <pre>Hi, No, I just want to delete some group of users from a single list Cyril Le 07/06/2013 16:15, Aaron Wyatt a écrit : </pre> Cyril Sarrauste de Menthière 2013-06-07T14:35:45 http://permalink.gmane.org/gmane.mail.sympa.user/1348 <pre>On Jun 7, 2013, at 2:57 AM, Cyril Sarrauste de Menthière &lt;Cyril.Sarrauste-RBxg8RIYzqNWj0EZb7rXcA&lt; at &gt;public.gmane.org&gt; wrote: Are you asking about deleting every list for a particular robot, or just a subset? My initial thought is that if you have the list of lists to be deleted you could script this (bash) and run the script as the sympa user. aaron _______________________________ Aaron Wyatt Collaborative Services Boston College IT Services aaron.wyatt-Qs1XVtlgrJU&lt; at &gt;public.gmane.org 617.552.1278 _______________________________ </pre> Aaron Wyatt 2013-06-07T14:15:46 http://permalink.gmane.org/gmane.mail.sympa.user/1347 <pre>Sorry for my previous messages in French. ;-) Is there any wildcards characters in order to use SYMPA commands by email, for exemple to bulk delete : DEL &lt;list&gt; *&lt; at &gt;igh.cnrs.fr or something like that ? Thanks Cyril </pre> Cyril Sarrauste de Menthière 2013-06-07T06:57:49 http://permalink.gmane.org/gmane.mail.sympa.user/1346 <pre>Hi folks- I'm working on a problem I'm having with a sympa 6.1.17 install. The problem isn't really a problem, but rather expected and programmed behavior, however I'm looking for a way do disable the feature. I've put together a summary of the problem below, including a description, cause, and known solutions. The basic gist of it is that unsecured http session cookies can pretty easily become out of sync between wwsympa and the client. This causes the session to be renewed and forces the user to re-auth. The solution is to use SSL which doesn't require the session cookies to keep changing. So here' s my problem: Our sympa CAS sits behind an F5 load balancer which does SSL termination for the CAS. What that means is that the load balancer holds onto the server certificate and handles all the https encryption/decryption. It then passes the decrypted http traffic back and forth between the CAS and itself. This means, as far as wwsympa is concerned, all traffic coming to it is over unsecured http, </pre> Aaron Wyatt 2013-06-06T20:35:34 http://permalink.gmane.org/gmane.mail.sympa.user/1345 <pre> le problème c'est que ce n'est pas un humain qui (dans mon voeux) envoie et/ou reçoit les mails, ce sont 2 machines sur 2 domaines différents . Merci tout de même ! cyril Le 06/06/2013 16:47, Anne Durand a écrit : </pre> Cyril Sarrauste de Menthière 2013-06-06T14:57:54 http://permalink.gmane.org/gmane.mail.sympa.user/1344 <pre>je n'ai pas dû être assez précise, vous pouvez envoyer la commande REWIND par mail au serveur de listes. Il vous renverra par mail la liste des abonnés. Il restera un travail un peu fastidieux de copier en tête de chaque ligne QUIET DEL mais avec un bon éditeur de texte s'il y a beaucoup d'abonnés, cela devrait être faisable. Anne Le 06/06/2013 16:09, Cyril Sarrauste de Menthière a écrit : </pre> Anne Durand 2013-06-06T14:14:04 http://permalink.gmane.org/gmane.mail.sympa.user/1343 <pre>Bonjour pour un ajout silencieux, j'utilise la commande QUIET ADD nomliste mailuser pour une suppression globlale, je ferais d'abord un REWIND de la liste pour obtenir la liste des abonnés, puis j'ajouterais au début de chaque ligne, avant le mail de l'utilisateur QUIET DEL nomliste (inutile d'effacer la fin de ligne qui comporte le nom et l'option d'abonnement, sympa les ignore dans la commande DEL, par contre il faudrait les supprimer si on utilisait ADD, je crois). je mettrais quit en fin de liste de commandes http://www.sympa.org/manual/sympa-commands Anne Le 05/06/2013 16:32, Cyril Sarrauste de Menthière a écrit : </pre> Anne Durand 2013-06-06T11:26:23 http://permalink.gmane.org/gmane.mail.sympa.user/1342 <pre>Bonjour, Après avoir lu la doc et cherché dans le FAQ je n'ai rien trouver. 2 questions pour un propriétaire de liste que je suis: 1 ) Comment supprimer tous les membres d'une liste*par commande mail *(DELL )sans à avoir à le faire user par user ? 2) Comment faire pour que les personnes que je vais inscrire ou supprimer*par commande mail *(ADD) ne reçoivent pas de mail leur indiquant qu'elles ont été inscrites ou supprimées ? En vous remerciant; cyril. </pre> Cyril Sarrauste de Menthière 2013-06-05T14:32:16 http://permalink.gmane.org/gmane.mail.sympa.user/1341 <pre> On 05/24/2013 05:06 AM, Steve Shipway wrote: Adding a special header would be easy for this particular case. Good idea! Mike </pre> Michael D. Sofka 2013-05-28T16:55:45 http://permalink.gmane.org/gmane.mail.sympa.user/1340 <pre>Excerpts from C. Morgan Hamill's message of 2013-05-20 16:20:49 -0400: Double-checking: nobody has any ideas? -- C. Morgan Hamill &lt;chamill-KaPM4R2U43T2fBVCVOL8/A&lt; at &gt;public.gmane.org&gt; </pre> C. Morgan Hamill 2013-05-28T13:49:23 http://permalink.gmane.org/gmane.mail.sympa.user/1339 <pre>So, I’m migrating yet another departmental MailMan server to our central Sympa server. In order for their old MailMan archive URLs to continue to work, I’ve set up a few special redirects in our Apache server. These might be of some use to anyone else doing the same sort of move. Note that this is setup so that it will work also correctly when you have multiple list domains! First of all, create /etc/httpd/conf.d/monthmap.txt to map month names (as used in Mailman) to month numbers (as used in Sympa). # /etc/httpd/conf.d/monthmap.txt January 01 February 02 March 03 April 04 May 05 June 06 July 07 August 08 September 09 October 10 November 11 December 12 Next, add the following /etc/httpd/conf.d/mailman.conf to map archives to their correct location, as well as doing its best to map list info pages and so on to a corresponding page in Sympa. RewriteEngine On RewriteMap monthmap txt:/etc/httpd/conf.d/monthmap.txt RewriteRule ^/mailman/listinfo/(.*)$ /sympa/info/$1 [R=30</pre> Steve Shipway 2013-05-28T00:49:13 http://permalink.gmane.org/gmane.mail.sympa.user/1338 <pre>Thanks Steve. An alternative way to disable the "cleaning" is simply to not call the clean_html() method in clean_archived_message in archived.pl (see below): This does what we want - the 'security' around lists is something that we handle via moderation etc. In short, anything that actually gets posted should be (verbatim) in the archives also. Can I please suggest that an option to disable the archive cleaning is added to wwsympa.conf ? Thanks, Patrick ------------------------------------------------------------------------ sub clean_archived_message{ my $params = shift; &amp;do_log('debug',"Cleaning HTML in archived file '%s/%s' (overwrite: %s).",$params-&gt;{'path'},$params-&gt;{'file'},$params-&gt;{'overwrite'}); my $filtered_file; if ($params-&gt;{'overwrite'}){ $filtered_file = $params-&gt;{'path'}.'/'.$params-&gt;{'file'}; }else{ $filtered_file = $Conf::Conf{'tmpdir'}.'/'.$params-&gt;{'file'}; } my $file_to_archive = $params-&gt;{'path'}.'/'.$params-&gt;{'file'}; </pre> Patrick Rynhart 2013-05-28T00:33:48 http://permalink.gmane.org/gmane.mail.sympa.user/1337 <pre> I also noticed this. I think the rationale was that, by making links and email addresses in messages unclickable, it prevents link spam via mailing list archives and the like. However, I don't like it... and our users want to retain clickable links in archives, as with the old MailMan system. So, this is how to get rid of it! First, you need to edit the file mhonarc-ressources.tt2 (yes, that double s is correct) in your Sympa config directory. Look for the MIMEARGS definition. Set the following options: &lt;MIMEARGS&gt; text/plain; asis=us-ascii:iso-8859-1:iso-8859-2 nonfixed quote htmlcheck maxwidth=78 link="http,https,ftp,mailto" text/html; asis=us-ascii:iso-8859-1:iso-8859-2 allownoncidurls m2h_external::filter; subdir usename &lt;/MIMEARGS&gt; This allows the archives to make embedded URLs in archived text postings into hotlinks. The next part requires you to modify the Sympa code... 8-O In sympa/lib/tools.pm you need to add a couple of options to the StripScripts::Parser. Around line 111 or so, add the </pre> Steve Shipway 2013-05-28T00:16:19 http://permalink.gmane.org/gmane.mail.sympa.user/1336 <pre>We have recently upgraded from Sympa 5 to 6, and have since noticed that archived.pl now "cleans" HTML messages (via a subroutine clean_archived_message()). In emails going out to a wide audience, we have used linked images to avoid bloating users Exchange mailboxes (i.e. not use embedded images). In Sympa 6, we have found that the HTML cleaning breaks with this approach, so if someone visits the archives afterwards, the images are stripped. Here is a minimal example. If we send an HTML email to a Sympa 6 mailing list consisting of: &lt;html&gt; &lt;head&gt;&lt;meta http-equiv="content-type" content="text/html; charset=ISO-8859- 1"&gt;&lt;/head&gt; &lt;body&gt;linked image test&lt;img src="https://path/to/my/image/on/server"&gt;&lt;/body&gt; &lt;/html&gt; then the image presents fine in subscribers inboxes, but the image is not present in the list archives. On the archive page (i.e. https://sympaserver/arc/listname/2013-05/msg00010.html) instead the following HTML is embedded in the archive page (which doesn't contain an img tag at all!): &lt;tab</pre> p.rynhart-GuuZuZYZZ9vScTE++YW6Eg< at >public.gmane.org 2013-05-26T23:31:35 http://permalink.gmane.org/gmane.mail.sympa.user/1335 <pre>One option you have, is that you can use an S/MIME signature to validate the email. We have this on some lists. You just obtain an S/MIME signature for the people entitle to post to the list, and make sure your send scenario covers them (maybe make them list editors, or have a separate list in a file). Set the send scenario to require an S/MIME signature. Your current way is a bit insecure if anyone finds out the password - though not as insecure as having no additional confirmation, of course! If moderation and confirmation mails are not acceptable, then S/MIME is probably the way to go, and is more secure anyway. You *could* create a custom send scenario that validates the content of the message to contain the password field, but there is no way I know of to remove the password line from the body before distribution. Another possibility is to have a password *header* -- eg, X-Password: -- and set the list options to strip the header before distribution, similar to the way the Approved header works </pre> Steve Shipway 2013-05-24T09:06:50 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.mail.sympa.user