1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] Mailing list migration: this list is closing
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mailing%20list%20migration%3A%20this%20list%20is%20closing&In-Reply-To=%3C516286FF.10308%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009397.html">
<LINK REL="Next" HREF="009403.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] Mailing list migration: this list is closing</H1>
<B>andre999</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mailing%20list%20migration%3A%20this%20list%20is%20closing&In-Reply-To=%3C516286FF.10308%40laposte.net%3E"
TITLE="[Mageia-discuss] Mailing list migration: this list is closing">andre999mga at laposte.net
</A><BR>
<I>Mon Apr 8 10:59:43 CEST 2013</I>
<P><UL>
<LI>Previous message: <A HREF="009397.html">[Mageia-discuss] Mailing list migration: this list is closing
</A></li>
<LI>Next message: <A HREF="009403.html">[Mageia-discuss] Mailing list migration: this list is closing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9399">[ date ]</a>
<a href="thread.html#9399">[ thread ]</a>
<a href="subject.html#9399">[ subject ]</a>
<a href="author.html#9399">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Ludovic Meyer a écrit :
><i> On Sun, Apr 07, 2013 at 10:02:18PM -0400, andre999 wrote:
</I>>><i> nicolas vigier a écrit :
</I>><i>
</I>>>><i>
</I>>>><i> The only way currently is to create an identity account for each address
</I>>>><i> you want to use. We can look if it would possible to support an other
</I>>>><i> way to do it, but I don't know if that's possible. And of course any
</I>>>><i> suggestion about how sympa could be configured to manage multiple email
</I>>>><i> addresses with only one ldap account is welcome.
</I>>>><i>
</I>>>><i>
</I>>><i> I don't know if this is easily configurable, but the online
</I>>><i> documentation for sympa 6.1 has an example that seems to permit
</I>>><i> filtering by multiple addresses with ldap.
</I>>><i> see <A HREF="http://www.sympa.org/manual/authorization-scenarios#search_condition">http://www.sympa.org/manual/authorization-scenarios#search_condition</A>
</I>>><i>
</I>>><i> Their example shows both
</I>>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">salaun at cru.fr</A>
</I>>><i> and
</I>>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">O.salaun at cru.fr</A>
</I>>><i> being accepted with the same filter, whereas only the first is coded
</I>>><i> as such.
</I>>><i>
</I>>><i> This seems to offer interesting possibilities, allowing users to
</I>>><i> have alternate email adresses with different prefixes of their ldap
</I>>><i> adresse.
</I>>><i> (by automatically adding * to the beginning of user ldap adresses.)
</I>>><i> The code could require a minimum length to minimise false positives,
</I>>><i> and/or add the * just before @.
</I>>><i>
</I>>><i> Would this work, and without too much effort ?
</I>><i>
</I>><i> The goal of having 1 unified login is to reduce ( usually in a company ) the amount
</I>><i> of support of helpdesk, and the work of user because they need to have 1 login/password.
</I>><i>
</I>><i> This also prevent login conflict, since there is 1 single place where this is resolved
</I>><i> for uniqueness.
</I>
Apparently my comment wasn't clear.
It is not related to mageia identity login, which would remain unchanged.
><i>
</I>><i> Your suggestion will just increase the support time due to increased complexity, and so
</I>><i> reduce the time avaliable for the sysadmin team, since from what I see, they are in
</I>><i> charge of the servers, and the function of support.
</I>
It would be a one-shot change. If it is properly commented, it
shouldn't cause any support problems.
It is up to sysadmin to decide if they want to do it.
I was only reacting to the posts of solbu and boklm.
(boklm is on the sysadmin team.)
><i>
</I>><i> So if you think they have no better way to spend their time and that this is so
</I>><i> "business critical" to permit to have a mess regarding who said what, sure, go ahead
</I>><i> and provides a patch. If I am not wrong, the configuration is on :
</I>><i> <A HREF="http://svnweb.mageia.org/adm/puppet/modules/sympa/">http://svnweb.mageia.org/adm/puppet/modules/sympa/</A>
</I>><i>
</I>><i> But if the only goal is to satisfy the special need of a few unique snowflakes, that's not really a
</I>><i> good move.
</I>><i>
</I>Not very clear why you are taking offense.
We are talking about a minor change to solve a perceived need of a user.
More significant changes are being done all the time.
Maybe you should re-read my post ?
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009397.html">[Mageia-discuss] Mailing list migration: this list is closing
</A></li>
<LI>Next message: <A HREF="009403.html">[Mageia-discuss] Mailing list migration: this list is closing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9399">[ date ]</a>
<a href="thread.html#9399">[ thread ]</a>
<a href="subject.html#9399">[ subject ]</a>
<a href="author.html#9399">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>
|
