I want to whitelist an email address on all lists to bypass moderation.
The email address is not a subscriber. On google I
found accept_these_nonmembers but I do not know how to use it.
Please show me some examples how to whitelist someone(a)example.org.
Thanks in advance.
I'm not sure if this is the correct forum for this question, but I'm pretty
sure if there is expertise on how to do what I want to do, it can be found
Overview of what I am looking to do:
Due to the impending shutdown (in the next 6 months) of the data center
where our mailman server lives, we are being forced to move the
installation. We are going to be moving it to a different location.
Here is our problem...
Moving things is not really a problem in and of itself - I'm confident that
I can get things set up correctly elsewhere. However, our email server
sends somewhere around 100,000 emails per day, and if you cut over from one
IP address to another IP address, my understanding is that most ISPs will
start to ban you, because they are not used to that sort of volume coming
from an unknown IP. I know it would be better if we could keep the IP
address, but again, due to circumstances beyond my control, this is not
going to be a possibility.
We have been told that "warming up" the IP is the way to go - that is,
cutting over just some of the traffic a little at a time. So what I am
looking for is a way for all mail on our domain to be sent to our current
mailman installation, and based on some configuration (certain mailing
lists?) certain emails being sent out to the list subscribers will first be
forwarded to the new server and be sent from the new IP address.
Does that make sense?
Does anyone know a way that mailman/postfix can be configured to accomplish
Is there a different forum where I might be able to ask experts about this?
I saw in the docs:
> We have it! We just don’t have proper documentation here yet.
Could you please be more specific - can I switch Mailman 3 installation to
is it possible to migrate a mailman3-mysql-database to a
I tried to convert it with pgloader, but some identifiers had to be cut off:
2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner
wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac
I want to make you aware of a potential privacy problem in Mailman's
Hyperkitty. Under the upcoming EU General Data Protection Regulation
(GDPR), which will be in force as of 2018-05-25, it is illegal to
transmit data to third parties without a right to do so. Without going
into the details, the inclusion of third party services into one's
website is usually deemed such a transmission, and unless one has
explicit consent of the user (e.g., by an optional (!), unticked ticking
box) this is normally illegal (if one targets EU users).
The GDPR does not affect private and family use (Art. 2(2)(c) GDPR), but
the exact reach of that clause is yet to be determined; it certainly
does not exclude company use of Mailman.
I've found it's possible to disable the social login providers quite
easily (we had this discussion here on the mailinglist recently), but I
don't see an option to disable Gravatar. If there is one, please
enlighten me, but anyway I want to propose this as a feature request
against Hyperkitty. A GDPR-compliant implementation of Gravatar in
Mailman would look like this:
* In order to not transmit website visitor's data (IP address, browser
info, etc) to Gravatar, Hyperkitty has to request the avatar image
itself and not leave that to the user's browsers to do. In other
words, the HTTP GET request needs to come from the server running
Hyperkitty and the user's browser then just requests the avatar from
the Hyperkitty server. Most likely easiest way to do this is to
pre-download the avatar when an email is archived.
* In order to not transmit the subscribers' data (email address, allows
Gravatar to track the subscriber) to Gravatar illegally,
the retrieval of the avatar image from Gravatar has to be disabled by
default. Instead, an option needs to be added to the subscriber's
control panel which he has to actively enable in order to have his
Gravatar downloaded and thus used (privacy-by-default rule).
I'm not saying Gravatar tracks people and sells the information
gathered, though I have doubts on how Automattic makes money with the
service. I'm just outlining the legal duties under the upcoming GDPR for
service owners, which are independant of how Automattic processes the
data in this specific case.
Please don't dismiss this as some side feature not needed. The fines
that can be imposed on service owners due to violation of the GDPR are
very high (up to 20,000,000 € [that's 20 million euros, really]).
PGP/GPG ID: F1D8799FBCC8BC4F
I am making a serious attempt at installing Mailman 3 using docker. I have a CentOS 7 server setup via Linode. I am using the following documentation to setup a Mailman 3 server:
I have Docker, Postfix, and Nginx installed and working fine. The installation of the Mailman 3 container went fine. However I am getting the following error when I go to test Posterius via shell:
curl: (7) Failed connect to 172.19.199.3:8000; Connection refused
I assume this has something to do with uwsgi which I have no experience with.
Appreciate any assistance with getting Mailman 3 up and running. Thanks!
After doing a lot of googling I can't seem to find solid answers to a couple of basic mailman hosting questions so I thought I would ask here.
I'm looking to build an auto scaling group so that my mailman services can self heal if the EC2 instance goes away. What state if any is stored locally on the filesystem that would need to be backed up and restored when an instance is replaced?
I'm also interested in a high availability deployment so I would like to do some basic load balancing to ensure that this requirement is met but I haven't been able to find much on this topic for mailman 3. Can someone point me in the direction of a write up on this problem or comment on it?
Hah, adding the extension did the trick. Should have inferred that. Thanks!
John W. Hathaway | IT Director
LOCKRIDGE GRINDAL NAUEN P.L.L.P.
100 Washington Avenue S | Suite 2200 | Minneapolis MN 55401
V: 612-339-6900 | F: 612-339-0981 | www.locklaw.com<http://www.locklaw.com/>
This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient or otherwise have received this message in error, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you are not the intended recipient or otherwise have received this message in error, please notify us immediately by e-mail, discard any paper copies and delete all electronic files of the message.