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
Hello everyone, i have being using maxking's docker images for mailman
3 without any issue this far, unfortunately recently i found a problem
with the search option in the archive, if i try to search for anything i
got a error 500
docker exec mailman-web ./manage.py update_index --verbosity 2:
I suspect that at some point while archiving mails something went
wrong, but no sure. Any idea how to fix or debug further.
Thanks in advance.
Carlos R Laguna Mendoza
Subdtor. Grp Técnico Tinored
Joven Club de Computación y Electrónica
Tel: 52793189, 7863-3174, 7868-4230
We would like to give our users the priviledge to create lists per
domain. I Haven't found any options for that in the web interface.
Is this possible somehow with mailman3?
We recently had a phishing message make it through our spam filters and
arrive at a mailing list. The good news is that since it was not from a
list member it was in the held message queue.
I was able to find the message in the var/messages directory by searching
for a keyword in the subject. However, after rejecting the message from
Postorius, the message doesn't seem to be removed from the var/messages
Is this expected behavior? I know that infosec people won't be too happy
about a phishing email sitting around on our disk. (Infosec guys are
notoriously paranoid. :) )
Is there some sort of cleanup process that would remove these messages? If
not, does this pose an issue where over time disk usage will creep up? This
could be a pretty significant problem if that is the case.
What do you think, sirs?
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
We migrated from mailman2 to mailman3 a week ago. Since then we are unable to send messages the our students through the mailing list.
Here are some symptoms:
1. I go to mass subscribe and subscribe 400 emails
2. I click subscribe, the browser (in my case safari) tries to load the page for a few seconds
3. The request times out
4. Once the service becomes responsible again, I see that only part of my emails got subscribed (~50 in this case).
For me this really looks like the emails are sent on the "web-thread" that gets killed once the request times out.
Looking at this https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list... <https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list...> seems to confirm my suspicions.
Some quick overview of our infrastructure: The TCP endpoints are:
browser -> haproxy in kubernetes-entry-router -> nginx in kubernetes-ingress -> nginx in mailman -> mailman
We mitigated the issue by giving it more CPU power and increasing the timeouts in one of the nginx endpoints.
We also have a problem with sending out emails to "large" (>50) groups, as they seem to not getting sent out at all. Do you have any idea what the problem here could be?
We would be really glad if you can help us getting our mailman up and running, as I currently have to send emails out by "hand".
I will happily provide you with more details about our configuration, just let me know what you need.
Jonas Felber <jonas.felber(a)vis.ethz.ch <mailto:email@example.com>>
Aktuar & CTF Präsident
VIS - Verein der Informatik Studierenden an der ETH Zürich
CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich