Mireka provides very simple mailing lists. This implementation is appropriate for small, internal, closed membership lists. There is no archiving, automatized subscription/unsubscription address, moderation etc. If the requirements are more complex, then a dedicated list manager software should be used.
Edit local-recipients.js
and insert a new mailing list definition below the
comment ENTER YOUR RECIPIENT-DESTINATION MAPPINGS HERE.
For example if you want that all mails sent to the address admin@example.com
be
distributed to john@example.com
and jane@example.net
, then insert the following lines:
... mailingList({ address: "admin@example.com", subjectPrefix: "[SYS-ADMIN]", // Subject of mails will be prefixed by this text. Default: no prefix. membersOnly: false, // Only members are allowed to send mails to the list. Default: true attachmentsAllowed: true, // Default is true. replyToList: true, reversePath: "list-owner@example.com", // Bounce messages will go to this address. Required. membersOnlyMessage: "Only example.com system administrators can post onto this list.", nonMemberSenderValidator: setup(SubjectRegexpValidator, { pattern: ".*TICKET-NO.*" }), members: listMembers([ "john@example.com", "jane@example.net", ]), }), ...
Fields not commented above:
replyToList
: If true, pressing the Reply button in a mail client send a mail to the list, and not the original sender. Default: true.
membersOnlyMessage
: Mails from non-members (if they are disabled) will be bounced with this message. Default:
Only members of the list are allowed to send a message to this list address.
nonMemberSenderValidator
: Mails from non-members with subjects matching the supplied regular expressions will be always allowed. Optional.