L-Edit 可以把GDS 文件转层DXF 或DWG格式嘛？
坛内有兄弟姐妹用L-Edit 的嘛？这个软件可以把GDS 文件转成DXF 或DWG格式（AUTOCAD　格式）？
leonlee at
我感觉也不行，但我的R/D counterpart说可以，太奇怪了。
谢谢LS 童鞋。
andy2000a at
GDS 和 dxf 間
有其他軟體可轉
有人 try&&過 gds 轉到 dxf
使用 pda 上開 dxf 軟體開圖
但是 gds 內 因為很多線&&轉成dxf&&會database很大
幾 m 圖&&pda開不了
幾百k 內還ok
但是 還是可以使用 ..
lonelylong at
dxf& &好像只记得提pad的位置的时候用到过&&不了解&&学学
还没有转化过
phydora at
DXF格式没问题,DWG没用过.
L-Edit14.0
zy-photomask at
可以. for mask FAB.
用 linkcad&&转成 dxf格式后 原先的图层颜色消失了&&只剩下线框（例如 圆饼变成圆环）
这该怎么解决啊？？？&&求教啊
最新更新主题
月度关注热点2015年最新公共基础真题练习第41-80期(可以转成TXT文本手机l练习)_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
2015年最新公共基础真题练习第41-80期(可以转成TXT文本手机l练习)
上传于||文档简介
&&21年​最​新​公​共​基​础​真​题​练​习​第1​-0​期​(​可​以​转​成​T​X​T​文​本​手​机​l​练​习​)
阅读已结束，如果下载本文需要使用2下载券
想免费下载本文？
下载文档到电脑，查找使用更方便
还剩474页未读，继续阅读
你可能喜欢Translations of this page:
Sympa is an open source mailing list manager. It provides advanced features with a rich and secure web interface.
Original features :
scalable for big mailings lists ( & 1.000.000 list members)
list member provisioning using LDAP, SQL or other data sources
various authentication method (SSO, LDAP, X509)
S/MIME and DKIM
web archive with access control, message removal etc
virtual hosting for service providers.
automatic bounce management
easily customizable web interface
SOAP interface for integration with other applications
June 17th, 2016
is proud to release the newest version of Sympa to the open-source community.
Sympa 6.2.16 is the new stable version of Sympa.
This version finally fixes the old problem for primo-installation when the sympa wizard would not start to generate the sympa.conf... because the sympa.conf file was empty. Our thoughts go to the listmasters who had to fight this problem. Let them get rest knowing that, thanks to their reports, future generations will never ever have to face it. Kudos.
In addition, Soji fixed a timeout problem when Sympa closed a list, because Sympa spent ages checking whether the list was included or not in another one. He simply added a table registering the lists inclusions to speed up the checking process. And because fixing the problem was not enough to him, he also added a new page in the Sympa web interface to visualize lists inclusions. In summary, what you have now is:
“including_lists” page to get lists including particular lists.
This page is accessible only by list owners and listmasters.
Now looping by include_list settings can be detected.
Inclusion is skipped if a setting will cause looping.
the new 'include_sympa_list' parameter obsoletes 'include_list' in list config and named data sources. Older one may still be used as it is mapped to newer one internally.
This version fixes also several bugs. Please have a look at the release notes to see which ones. Some points of interest are:
[Reported by P. Kissman, Commonwealth of Massachusetts and D. Stoye, Univ. Berlin] The subindex page did not allow to actually accept/reject subscriptions. This was because of a badly named parameter being passed to the templates.
Improved sympa.service by ensuring other daemons will be started after invocation of sympa_msg.pl.
Note that this fix does not solve starting order of database service and Sympa: sympa.service should be customized if necessary.
May 12th, 2016
The most important change in this version is WWSympa does no longer respect HTTP request header fields noticing the request was forwarded (“X-Forwarded-Host:” etc.).
In particular cases, you may require adjusting configuration.
Now wwsympa_url parameter defines the URL publicly accessed by users.
Contrarily “http_host” and “cookie_domain” parameters indicate the URI and/or domain which are locally recognized by wwsympa, i.e taken form “http_host” (“Host:” field) and “request_uri” CGI environments.
“Location:” response field sent by wwsympa to cause redirection also gives local URL.
If requests sent from users to wwsympa are rewritten by intermediate server(s), you should make sure that wwsympa server and rewriting server(s) are appropriately configured. For example when the server is placed behind some sort of reverse-proxy including Apache mod_proxy (with ProxyPass), nginx (using proxy_pass) and squid (in accelerator mode). Note that not all reverse-proxies rewrite requests. For example, Pound does never rewrite requests by default. If it is not the case, existing configuration need not changing.
A few other changes in this version:
configure can take an option ”&with-unitsdir=DIR” to install Systemd unit files.
It would be used with ”&without-initdir” not to install System V init scripts. If specified, five unit files will be installed.
A few more unit files to support nginx environment are provided but they are not installed automatically.
a new parameter, use_tls, appears to replace obsoleted
“use_ssl” and “use_start_tls” note that these obsoleted parameters can stil be used. But the new one is way more convenient: “use_tls” takes one of following values corresponding to old ones:
“starttls” : use_ssl=0, use_start_tls=1.
“ldaps” : use_ssl=1, use_start_tls=0.
“none” : TLS/SSL is disabled.
Now STARTTLS may be enabled in LDAP datasource configuration of lists along with LDAPS.
The “Feedback” link will now be visible by listmasters only! We received enough mails from end users mis-interpreting this link with their local helpdesk.
Now [% path_cgi %] template variable respects “wwsympa_url” configuration parameter.
Previously it was taken from CGI environment variable.
This version fixes also several bugs. Please have a look at the release notes to see which ones.
May 12th, 2016
Sympa 6.1.25 is a maintenance version for the previous 6.1 branch of Sympa.
Since a long time, the Debian packagers of Sympa maintained several patches for some Sympa bugs. We finally incorporated them to the Sympa core, so the the fine packagers don't have to maintain these patches. As the 6.1 version is the one currently supported by Debian stable releases, we found relevant to tag a new 6.1 version.
Many thank to E. Bouthenot for both maintaining the Debian package and pointing us these patches that really needed to be integrated upstream.
Please note that, as we did with 6.0 branch when 6.1 was the current stable branch, we will maintain the 6.1 branch and fix blocking bugs or security issues.
Matter of factedely enough, the 6.1.25 version is an anagram of the 6.2.15 version, the stable tag which was released the same day. It doesn't mean a thing but I realized this while typing the announce so I thought I would underline it for all of you, numerologist friends around.
February 26th, 2016
is proud to release the newest version of Sympa to the open-source community.
Sympa 6.2.14 is the new stable version of Sympa.
The 6.2.13 version had a typo that made SOAP service fail. This is fixed, along with an annoying web error log that appeared when querying the lists SOAP service. Thanks to Bruno Malaval for reporting this!
Soji also improved Sympa daemons to capture the SIGCHLD signal, so that defunct children will be closed quicker.
As we tend to change the CSS regularly according to the different feedback you send us, we added the Sympa version number in the CSS file URL, so that it will be automatically reloaded, ignoring cache, when your users arrive on the web interface after an upgrade.
A set of other bugs were fixed in this version, among which:
[Reported by D. Pritts, Internet2] Changing web_archive_spam_protection did not update spam protection mode on past archives. Fixed by applying spam protection at the time of display, not when archives were created / rebuilt.
[Reported by A. Epstein, Cornell Univ.] base element in web output should be eliminated, because it will mess reverse proxy and so on. Fixed by making partial URIs to be redirected to base URI.
WWSympa: Cannot view attachments in bounce messages and moderated messages.
Fixed by correcting inappropriate relative URL paths.
Once again, Soji was the spearhead in fixing these bugs. Many thanks to him and his dedication to Sympa!
A word about translators:
Sympa is now - again - 100 % translated into Spanish. Thanks to A. Casado for this great work!
There was a lot of work on the following languages:
German, thanks to D. Stoye,
Brazilian Portuguese,
Estonian, thanks to U. Buhvestov,
Translation is what makes Sympa usable to non-English speaking people, so many thanks to all these great people involved in translating Sympa. Please let me know if, by any chance, I missed your work in internationalization.
February 12th, 2016
This version mainly introduces some bug fixes, code refactoring and several improvments to the web interface.
Soji had an ongoing work on bug fixes and overall refactoring for better maintainability. Many thanks again to him!
We had a lot of feedbacks about the web interface. Though most people agreed that it was more modern than previously, not so rare people also mentioned the bulky fonts and presentation, along with weird welcome page with lonely buttons.
We heard you, people! The main page and Sympa menu were reorganized for - we hope - better clarity. Several bugs were fixed.
November 18th, 2015
This version mainly introduces some bug fixes, code refactoring and several improvments to the web interface.
November 5th, 2015
Release 6.2.10 never existed actually: we had engineering problems when tagging the version - nothing to see with the code. As the branch was still created, the 6.2.10 was removed from Sympa oficiaal history. As it still existed, we changed the version number anyway.
This version mainly introduces non-blocking bug fixes.
October 13th, 2015
This version fixes bugs:
owner_include addition failed because the source parameter was improperly used.
single sympa.conf parameters with a value of '0' were considered unset, because of a badly built test,
for packagers: the root user could not run “make check”
October 2nd, 2015
This version introduces a table of content in Sympa help, as well as several bug fixes.
September 25th, 2015
This version mainly fixes a severe bug introduced in 6.2.4: Parsing of VERP bounces files in spool was broken due to a typo. Consequently, VERP, tracking and automatic unsubscription for service messages did not work.
September 22th, 2015
This version mainly introduces bug fixes.
Thanks to a suggestion by Y. Baouch (university of Colorado) - and development by S. Ikeda , the following problem is fixed: If DMARC protection feature munges originator field, many mail client cache such address by the replaced display name, and misleadingly associate the list address with the sender name. Now, the dmarc_protection.phrase can take the value “list_for_email”. In that case, the From field will take the value : “List (on behalf of SENDER) &munged_email
September 15th, 2015
Attention : Cette formation, organisée par RENATER, tutelle du projet Sympa, est réservée à la communauté Enseignement Supérieur / Recherche fran?aise.
les 6 et 7 octobre 2015 à l'Université de Strasbourg, UFR Math-info, 7 rue René Descartes
9h00 - 13h00 et 14h00 - 17h00
Public visé
Taille : 20 personnes.
Profil :Des administrateurs actuels ou potentiels du logiciel Sympa appartenant à la communauté Enseignement supérieur / Recherche fran?aise. Le TP peut convenir à des personnes connaissant déjà le logiciel et désirant explorer des fonctionnalités plus avancées, ainsi qu'à des personnes désirant découvrir le logiciel et ses potentialités.
Pré-requis techniques :
Le public doit disposer de compétences techniques raisonnables en administration Unix, messagerie et web.
Il est nécessaire de disposer d'une bo?te mail, professionnelle ou privée, capable de faire de la signature et de la vérification DKIM. Cette bo?te mail doit être accessible par webmail.
Aucun matériel n'est nécessaire : les moyens matériels sont fournis (ordinateurs et serveurs). Il est possible d'amener son propre ordinateur si vous préférez disposer de votre environnement.
Formateurs : La formation est assurée par les auteurs du logiciel Sympa (?tienne Méléard et David Verdin).
Formation gratuite
Repas non fournis
Aucun matériel n'est nécessaire : les moyens matériels sont fournis (ordinateurs et serveurs). Il est possible d'amener son propre ordinateur si vous préférez disposer de votre environnement
Architecture et organisation d'un serveur Sympa
Concepts de base : r?les utilisateurs, création et configuration des listes
La messagerie dans Sympa
Les interfaces de Sympa (web, mail, ligne de commande et SOAP)
Mécanismes d'autorisation : les scénarios
Sources de données pour l'alimentation des listes
==== Journée 2 ====
H?tes virtuels
Authentification externe
Personnalisation de Sympa : paramètres, le langage TT2, les éléments personnalisables
Industrialisation de la gestion des listes : familles de listes et listes automatiques
Fonctionnalités de messagerie avancées : VERP, tracking, personnalisation de messages, S/MIME
Couplage Sympa - Dokuwiki
September 10th, 2015
This version mainly introduces bug fixes.
September 1st, 2015
This version mainly introduces bug fixes. Many thanks to all the users who reported troubles on the mailing lists!
July 16, 2015
This version mainly introduces bug fixes.
July 01, 2015
This version mainly introduces bug fixes, most of them being related to tweaks in the new Sympa skin.
Amongst the bugs fixed, some notables are the following:
include_datasource_ca parameters were editbale by li This is wrong AND confusing, as users erroneously take these parameters as subscribers data sources.
[Reported by J.L. Marrion, univ. Louvain] when testing if list admins needed to be synced, all the test cases returned true because the test was badly formed.
[REported by B. Eliassen] “make” failed on Solaris.
A variable name conflicted with a predefined preprocessor macro.
It was not mentioned in previous release notes, but a lot of translations have been update by our numerous contributors. Thanks to all of them!
June 17, 2015
is proud to release the newest version of Sympa to the open-source community.
Sympa 6.2.1 “Damien” is the new stable version of Sympa.
This version mainly introduces bug fixes, most of them being related to tweaks in the new Sympa skin.
Amongst the bugs fixed, some notables are the following:
[Reported by D. Lalot, univ. Aix Marseille] When a list is at 100 % error, nobody receives the message, and nobody was warned that the message had been lost. Fixed by warning the message sender, the list owners and the listmaster when the bounce rate is at 100%.
[Reported by P. Grzesina, univ. Regina] The CAS button was not showed because the cas_number value in conf was never updated.
[Fixed by Soji!] If the user is listmaster of the host with large number of lists, loading create_list_request page will slow down. Fixed by not getting all lists but only owned lists.
[Fixed by Soji!] “make install” fails when install(1) omitting directory arguments.
It was not mentioned in previous release notes, but a lot of translations have been update by our numerous contributors. Thanks to all of them!
June 10, 2015
After 5 months of intensive beta testing,
is proud to release the newest version of Sympa to the open-source community.
Sympa 6.2 is the new stable major version of Sympa.
This version owes a lot to Soji Ikeda, one of the nice Sympa core developers. Soji is probably the most notable not-in-RENATER actor of Sympa 6.2's birth. He did a really great work at revamping large parts of the code. He was also the one who had the idea to put the bulk spools back to filesystem, though retaining all the bulk.pl specificities. He was eager to debug, analyze and finally solve a lot of the problems we had while working on it. May he be warmly thanked.
This version introduces a great deal of new functionnalities. Consequently, we can only highlight the main improvements in this announce.
To our numerous contributors: if your contribution does not appear in this announce, it does not mean we consider it less important. Actually, for some users, it can even be the key feature that will encourage them to switch to 6.2. But we prefer a reasonnably short announce that will be read rather than an exhaustive list of features. So we focused on:
what is the largest change in code or Sympa behaviour,
what represents a point of attention during upgrade
what is the most visible
Please refer to the release notes above for a full list of new functionnalities.
Unless the name of the contributor is specified, all theses change were done by the .
A great contrib from French army DGA Information
Superiority (Guillaume Colotte and laurent Cailleux) The tracking feature is a way to request DSN or DSN + MDN when sending a
message to each subscribers. In that case, Sympa (bounced.pl) collect both
DSN and MDN and store them in a new table “notification_table”.
each message, the list owner can display which subscribers has displayed,
received or not received the message. This can be used for some important lists where list owner need to collect the proof of reception or display of
each message. This page is accessible via archive (button “tracking”).
This feature is controlled by 2 list parameters see “tracking” paragraph in “edit list config”/bounce.
One of the reasons why this new version took so long to be issued is that we tried to move all spools in database. Testing of this change in actual conditions proved it to be completely unscalable. we then had to revert our changes. In addition, a lot of people had recurring trouble with the current bulk spool tables, dut to limits showing in fields length or n RDBMS availability.
Spool for bulk sending no longer depend on database tables: It is based on filesystem.
Packets and messages stored in database by earlier version of Sympa should be migrated using upgrade_bulk_spool.pl utility. (See
for when and how to run this utility).
[Submitted by W. Roquet]
Now Sympa stores data whenever one of
the following event occurs:
a user unsu
a user is added to a
a user is removed from a
a user is removed from a list by the automat
a file is uploaded to
a file is del
a message to a list is re
a user logs in
a human user (not a harvester) hits a page.
These data are regularly aggregated by the task_manager, in order to make them anonymous and to have easily displayable data. The aggregated data are available to users, owners and listmaster in their respective interfaces. Only relevant data are presented. They are displayed in graphs to help people see trends and activity peaks. To be able to display these graphs, you must enable the static_content URL. In addition, the stats are accessible through the web interface, so if you customized
your web templates, you must update them to include the links and template processing.
The most visible is probably the new web interface skin. Contributed by the Massey university, it is nicer, simpler, responsive and retains all the customization capabilities that make Sympa adaptable to your needs. Many thanks to Patrick Rynhart and his colleagues for this great contributions! (in addition, outputs by WWSympa have HTML5 document type definitions).
Olivier Lumineau, from RENATER, worked a lot to still improve the work done by Massey. For those of you who were in the beta, you'll notice several improvments in the responsivity. Also, the Sympa top menu is back. If you don't like it, all you have to do is simply edit the main.tt2 template, then set the “top_menu” variable to 0 instead of 1!
Exclusion table was just a display of the users excluded. list owners could not do anything to r This page is now a form, similar to the review page, which allows to restore users subscriptions.
Added “Add subscriber” button to modindex page if the sender is not subscribed.
It may be useful because users need not know about SUB command and sympa command address. The buttons appear only when Web user is the list owner.
The “Customizing” link was moved from main list admin to list config sub section as list related text files are in a way list configuration parameters as well.
[Submitted by Evoltech, Riseup] Better password validation. When the user requests change of password via WWSympa or SympaSOAP, new password may be checked its strength. New parameter password_validation may be used to customize policy of password validation.
See help text of the parameter for more details.
[Submitted by M. Overmeer, overmeer.net, funded and led by Surfnet, ] Full VOOT 2.0 protocol support. VOOT is an opensocial subset to manage group membership. full details on this IETF draft here: . This feature enables Sympa to be both group provider and consumer in the VOOT protocol. VOOT in Sympa uses both Oauth 1.0 and 2.0 for authorization from and to a peer in the VOOT protocol.
The soap server now exposes full review with owners, editors and gecos to list masters and list owners.
[Submitted by S. Shipway, Univ. of Auckland] Adding new functions to SympaSOAP: getDetails, setDetails, getCustom and setCustom.
We added or improved several ways to plug new functionnalities in Sympa.
This feature allows to package code to be used in templates. It enables foreign data integration in Sympa's UI and emails, user specific UI enhancement and much more! Integrating user targeted data retreived through a call to a webservice becomes possible in a simple way, automatically adding info from a database to outgoing emails as well ! Further details here :
Custom actions are used to run specific code and/or display user defined templates. They can be executed in list or global context (it is up to you to decide what to do in both cases). Previously, a custom action was a simple TT2 template added to the web interface. It could only display data, not process them. They were improved to allow greater expressiveness. You can now develop a perl module to process the data passed to your custom action.
Warning: AFTER UPGRADING TO 6.2, ANY PRE-EXISTING CUSTOM ACTION MUST BE MOVED TO THE RELEVANT CUSTOM_ACTION DIRECTORY TO KEEP WORKING. Check .
for full details on this functionnality.
Sympa::Message::Plugin provides hook mechanism to intervene in processing by Sympa.
Each hook may modify messages or may break ordinary processing. This functionnality is quite new and still experimental. Please read the perldoc of Sympa::Message::Plugin for more details about how to create and enable hooks in message handling.
If you have no idea what a “perldoc” or a “Sympa::Message::Plugin”” are, you should not try to use this functionnality. Ask a Perl developer nearby instead.
Custom attributes can now be provisionned using external data sources, the same way as email addresses. For now, only SQL or LDAP datasources are supported. To use this feature, you need first to define the custom attributes as previously. This attribute must have the same name as the fields used in your queries.
For example, if your query returns the user name in a field called “u_name”, then your custom_attribute must also be called “u_name”.
New parameters:
include_sql_ca
include_ldap_ca
includeldap2level_ca
In several organizations, nightly maintenances make the datasources unavailable during some period of times. a new sub-parameter in data sources definition allow to prevent Sympa from trying to synchronize list members with these sources during a defined time range.
documentation for details.
A recurrent question regarding list inclusion was to be able to extract not the whole list, but only a subset. It is now possible.
include_list parameter value can now look like this:
&code&&listname& filter &filter_condition&&/code&
filter_condition is a TT2-compatible condition expression, it inherits current potential subscriber properties such as email, gecos, custom_attributes, etc. Tests like isSubscriberOf, isEditorOf and isOwnerOf are also available.
Test examples :
include_list foo filter email.match('@bar.tld$') &rA Includes members from list “foo” whose email domain is “bar.tld”
include_list foo filter isSubscriberOf('bar') &rA Includes members from list “foo” who are also subscribed to list “bar”
include_list foo filter reception == 'mail' and not 'gecos'
&rA Includes members from list “foo” who have their reception mode set to mail and no gecos
Please see the
for a full description on how to extract subsets from mailing lists.
[Submitted by S. Shipway, univ. Auckland] ODBC is now supported for email data sources.
[Submitted by Patrick von der Hagen, Renan Manola and Steve Shipway] sql, ldap and ldap2 user inclusions now handles gecos. It uses 2nd returned column for sql and 2nd given attribute for ldap (comma separated).
Now “host” parameter of the LDAP datasource in list config may include URLs (ldap, ldaps and ldapi) along with hostnames. So “port” and “use_ssl” parameters would be obsoleted.
Now CustomCondition can set the action to take (do_it, reject ...) by setting $&underscore&, this allows for complex, single-module CustomConditions.
”[msg_header-&field][index]” returns the value of particular field.
Index may be negative. - ”[msg_header&field]” still returns list of field values, additionally, ordering will be preserved. Fixes:
Conditions is_listmaster, is_owner, is_editor and is_subscriber can handle multiple values.
They also parse arguments as header field values to get address parts.
New list parameter: 'member_include'. This parameters allows to defined .incl files to include list members, the same way it is done for list admins. This grants extended flexibility in datasources, allowing list owners to tweak their own data sources without accessing to the actual details of the query made to gather email addresses.
New sympa.conf config parameter “sender_headers” to specify header fields by which message sender is detected. This is a enhancement to S. Shipway's improvement. RFC: What is the reasonable default for this parameter?
Behavior of one time ticket lock-out is configurable. Two new robot parameters were introduced:
one_time_ticket_lockout:
“one_time” won't allow access again. This is previous behavior.
“remote_addr” will lock the ticket on remote address accessed at first time.
“open” will never lock-out tickets.
one_time_ticket_lifetime: Duration before ticket expires.
Default is “2d”, previous hardcoded value.
New 'auth_service_friendly_name' in auth.conf CAS paragraph. This allows to set a display name for the CAS server, without the constraints that 'auth_service_name' entry has ([\w-.]).
Changes of list config parameters on archiving. New parameter “process_archive” controls archiving. The default is “off”: To enable archiving, it must be set to “on” explicitly.
OTOH even if archiving is disabled by setting it “off”, past archives will be kept and accessible according to access settings.
Renamed parameters. web_archive.access to archive.web_ archive.access to archive.mail_ web_archive.quota to archive. web_archive,max_month to archive.max_month. Though config files of exisiting lists will be updated during upgrading process, listmasters are highly recommended to check new configuration. Customized scenarios, list creation templates and edit_list.conf will never be upgraded automatically.
They should be modified manually, if neccessary.
Now messages sent via WWSympa will be stored in bulk spool, directly if they are outbound messages.
On earlier releases outbound messages were injected in msg spool with special checksum. A program upgrade_send_spool.pl to migrate messages with old format is proveded. Check .
Postgresql RDBMS are now automatically upgraded!
wwsympa.conf will no longer be used: it would be migrated to sympa.conf.
Makefile.am: no longer create wwsympa.conf during installation.
sympa_wizard.pl: &create argument disallows “wwsympa.conf” option.
Upgrade.pm: migrate wwsympa.conf during upgrade process.
Note: Run “sympa.pl &upgrade” to migrate wwsympa.conf into sympa.conf. Check .
Default config
location is now /etc/sympa/ (or $sysconfig/sympa/) instead of /etc/. This solves the problem of config file lock creation being denied when trying to read the binary version of the config file at startup.
WARNING : to upgrade the config location one MUST run sympa.pl &upgrade_config_location before any other upgrading operation. Check .
Now alias maintenance utilities other than newaliases may be used without special configure options nor patch to alias_manager.pl.
aliaswrapper and virtualwrapper were deprecated and replaced with sympa_newaliases-wrapper.
New alias management program sympa_newaliases.pl which will typically be called by alias_manager.pl via sympa_newaliases-wrapper.
New site configuration parameters aliases_db_type and aliases_program will control behaviour of alias database maintenance.
configure script:
Options &with-sendmail_aliases and &with-virtual_aliases were deprecated. Use &with-aliases_file instead.
New options &with-makemap and &with-postalias, along with options &with-newaliases and &with-postmap are available.
Option &with-postmap_arg was removed.
Alias managers can handle postmap/makemap style maps (delimited by whitespace), not only newaliases style maps (delimited by colon).
openssl(1) utility is no longer required.
Instead, a few CPAN modules are required to use S/MIME or SSL features:
Crypt::SMIME
Crypt::OpenSSL::X509
The parameter “openssl” in sympa.conf was obsoleted. Note that p12topem.pl still needs openssl: To make it work, PATH environment variable should be set appropriately.
i18n titles in configuration.
title.lang lines in scenario files are available again, though this feature was broken for a while.
Now topics.conf recognizes “title.gettext” lines. - scenario, task and topics.conf recognize “title” line for default title.
lang value in user_table
title.lang line in scenario files
title.lang line in task files
title.lang line in topics.conf
lang names in charset.conf
lang parameters of list config, robot.conf and sympa.conf.
Note that canonicalization will be done internally so that existing config must not be changed.
Now you can define a “scenari” directory in the lists family directory. These scenarii will be available for lists instantiated from this family. The “scenari” directory must be put directly in the family directory, not in the overall “families” directory. For example, if you want to define scenarii specific to the “staff” family, you must define a scenari directory in the /home/sympa/etc/families/staff/ directory. Not in /home/sympa/etc/families/.
Until now, only the config.tt2 file was parsed when the family was instantiated, thus producing the lists' config file. As a lot of other files can be used to configure a list (footer, header, etc.), we added the possibility to instantiate these files as well.
The list of files parsed (in addition to config.tt2) when instantiating a family are defined in a new (sympa.conf and robot.conf) parameter called 'parsed_family_files'. This parameter must contain a comma-separated list of file names. If these files exist, with the '.tt2' extension added to their name, in a family, they will be parsed and added to the list directory.
The default value of the parameter is:
'message.footer,message.header,message.footer.mime,message.header.mime,info'.
These files are updated in existing lists when a family is instantiated. note that it will overwrite any other customization.
This feature existed in 6.1 but it deserved a little more advertisment.
[Requested and funded by the CNRS] Automatic lists can now be manipulated through the sympa web interface, in a “user friendly” form. This is merely a web layer around the general autmatic lists feature. This feature is fully documented here:
Additionnally, it is now possible to unsubscribe to all the lists of a given family in two clicks.
Widely extended logs when the log_module parameter is activated with the value 'scenario': all scenario results are evaluated.
Remember that extended logs can be limited by the IP or the email of the user, using the 'log_condition' parameter. log_module and log_condition are now declared in sympa.conf instead of wwsympa.conf.
Remember these parameters syntax:
log_module: can take the value “scenario” - only.
log condition: takes a character string as value. The form is “ip=&an.ip&,email=&an_email&”. You can put ip alone, email alone or both, with the comma-separated form.
Listmaster notifications can now be grouped. If, for a specific robot, several notifications are issued within a short period of time with the same operation code only the first ones are sent, the next ones are stacked. The stacking ends when no notifications are issued anymore, or when the first one is too old. All the stacked notifications are then sent as attachments of a single message. Internal settings :
Stack if more than 3 notifications with the same operation code are issued for the same robot - Send stacked notifications if no new one satisfying the condition above was received for more than 30 seconds - Send stacked notifications if the oldest one was issued more than 60 seconds ago
sympa.pl &health_check checks config files, database connection and structure, and data structure version.
It is invoked at first time in sympa init script and reports errors if any. Instead, daemons such as sympa.pl no longer check database structure nor data version.
File extension of lock files are changed from ”.lock” to ”.LOCK”, because lowercase name can conflict with domain part in the future.
Attention : Cette formation, organisée par RENATER, tutelle du projet Sympa, est réservée à la communauté Ensignement Supérieur / Recherche fran?aise.
les 8 et 9 avril 2015 à l'?cole supérieure du professorat et de l'éducation (ESPE) - 63 la Canebière 13001 Marseille - salle 59
9h00 - 13h00 et 14h00 - 17h00
Public visé
Taille : 20 personnes.
Profil :Des administrateurs actuels ou potentiels du logiciel Sympa appartenant à la communauté Enseignement supérieur / Recherche fran?aise. Le TP peut convenir à des personnes connaissant déjà le logiciel et désirant explorer des fonctionnalités plus avancées, ainsi qu'à des personnes désirant découvrir le logiciel et ses potentialités.
Pré-requis techniques :
Le public doit disposer de compétences techniques raisonnables en administration Unix, messagerie et web.
Il est nécessaire de disposer d'une bo?te mail, professionnelle ou privée, capable de faire de la signature et de la vérification DKIM. Cette bo?te mail doit être accessible par webmail.
Aucun matériel n'est nécessaire : les moyens matériels sont fournis (ordinateurs et serveurs). Il est possible d'amener son propre ordinateur si vous préférez disposer de votre environnement.
Formateurs : La formation est assurée par les auteurs du logiciel Sympa (?tienne Méléard et David Verdin).
Formation gratuite
Repas non fournis
Aucun matériel n'est nécessaire : les moyens matériels sont fournis (ordinateurs et serveurs). Il est possible d'amener son propre ordinateur si vous préférez disposer de votre environnement
Installation et configuration
Architecture et organisation d'un serveur Sympa
Concepts de base : r?les utilisateurs, création et configuration des listes
La messagerie dans Sympa
Les interfaces de Sympa (web, mail, ligne de commande et SOAP)
Mécanismes d'autorisation : les scénarios
Sources de données pour l'alimentation des listes
==== Journée 2 ====
H?tes virtuels
Authentification externe
Personnalisation de Sympa : paramètres, le langage TT2, les éléments personnalisables
Industrialisation de la gestion des listes : familles de listes et listes automatiques
Fonctionnalités de messagerie avancées : VERP, tracking, personnalisation de messages, S/MIME
Couplage Sympa - Dokuwiki
January 13, 2015
is proud to release the newest version of Sympa to the open-source community.
Sympa 6.1.24 is the new stable version of Sympa branch 6.1
Sympa 6.0.10 is the new stable version of Sympa branch 6.0
These two versions fix a security breach. Please read the .
David and ?tienne went to YAPC::Europe at Sofia in August 2014. We finally dare presenting our software to the cream of the European Perl community. Big pressure, but the speech went quite well.
This speech by David is available on the
or just below if you prefer:
In addition to boosting our ego (Hi mom! I'm on the interwebs!) the speech is a good sneak peek at the main Sympa features and gives an insight on how the Sympa project works and what we plan for the future.
index.txt & Last modified:
17:29 by etienne.meleard@renater.fr