[Fiware] Some hints required for management of mailing lists

[Juanjo Hierro]

Dear Pier,

   I reply you copying the fiware mailing list because I believe my
response might be of interest to the rest of partners.

On 16/05/11 15:11, Garino Pierangelo wrote:
> Dear Juanjo,
>
>   I'd need your help to properly manage some automatic mails I have received concerning the FI-WARE mail reflectors.
>
> 1) I sent today a message to a number of recipients and to the fiware-i2nd lists, but I got a reply message asking for authorisation to send because of 'too many recipients', since I'm one of admins of the list. What should I do? I believe I'll authorise to send, but maybe there are some defaults which could be increased about the max number of recipients allowed. (see first mail)

   This was something we have had to fix in the initial configuration of
mailing lists.   It seems like they had been created with a limit of 10
destinees (without moderation) and now has been increased to 100.
Please check that everything works properly now and sorry for the
inconvenience.
> 2) I got a message from one partner who is not yet in the list and he tried to use the reflector address, which is not allowed. Should we manage all such situations in a centralised way on your side (I believe you receive the same messages), or can I answer to him to ask for registration to fiware-i2nd through my personal email so that he can be included in the list and use it? This was a case of 'cc-ing' a mail to our reflector: I expect this will be a frequent situation, if someone is not in a list but wants to send at least in 'cc' to the other lists of FI-WARE for their information. Which means: either we impose a very strict rule to send only to lists we are registered to, or to register each of us to most of the lists, otherwise we would be flooded by these admin messages to be managed... (see second mail)

   This is to avoid spam so that administrators of each mailing list
should handle this in a case by case basis.   There are two choices.
On one hand, you may add the address of the person who sent the email in
the mailing list membership list, using the Admin web page.   Another
choice is to setup a rule for automatically accepting all messages
coming from the originator of the email that you have been asked to
moderate.   When you receive a notification asking to moderate a given
message, it would include a link you may navigate to.   That link will
drive you to a web page where, as I have just explained, you may
establish as a rule that all future messages coming from the same source
get automatically accepted.

   It may take a few days/weeks until all people get properly registered
in the mailing list but, after some transition, it should work.   But we
believe we shouldn't deactivate the rule that establish that mails
coming from people not listed in the membership mailing list should be
moderated since it will help us to avoid spam.

   Best regards,

-- Juanjo
> Thanks a lot for your suggestions.
>
> BR
> Pier
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
>
> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
>

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jhierro.vcf
Type: text/x-vcard
Size: 429 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware/attachments/20110516/94155da7/attachment.vcf>