I'm in an odd situation where I need to rename a bunch of lists. They
were all created on mailman2 originally and migrated to mailman3 (very
successfully, TYVM) but the names were all originally
discuss-<foo>@domain and it's very confusing to be sure you're always
sending to the correct <foo>. We want to completely rename the lists to
<foo>-discuss@domain.
These lists do not keep archives, so if I have to resort to extracting
the subscriber lists and the configs and building new lists, I'm
completely fine with that. Problem is, I'm really used to MM2 and
config_list and could do this without thinking using those tools... that
I don't have.
Running MM3 3.2.2 trying to make this happen. Any assistance I could
get will be greatly appreciated.
THANKS!
--
Joel Lord
Web Administrator, Alpha Psi Omega Grand Cast
etc... etc... etc...
Hello,
I'm trying to figure out how to show the display_name of a member in postorius in Members > Subscriber.
I was trying to add {{ member.diplay_name }} in the template ${postorius}/templates/postorius/lists/members.html
Here an abstract of where I inserted the code:
[...]
{% for member in members %}
<tr>
{% if role == 'subscriber' %}
<td>
<label class="checkbox-inline">
<input type="checkbox" class="member-checkbox" name="choices" id="id_choices_{{ forloop.counter0 }}" value="{{ member.email }}" />
{{ member.display_name }} <{{ member.email }}>
</label>
[...]
I could not figure out why it wouldn't work.
I'm running mailman3 Version 3.1.1-9 on an Ubuntu 18.04.
Any idea what I was missing there?
Thanks in advance for any help.
- Ruben
Hi,
im trying to setup mailman and have an issue:
first my environment:
- I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/
- I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/
I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected:
In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp.
Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps?
For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/
Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)?
Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?)
Thanks and greetings,
Marc
Hi all,
After I setup mailman3 and run mailman-suite, I can do:
1. Register user
2. Login
3. Create new Domain
4. Create new List
5. Subscribe to the list
When I try to send email to the list by run command: echo ��test email�� | mail �Cs ��test email�� test(a)example.com<mailto:test@example.com>
User test can receive this email, but I cannot find it on Archives, and other members cannot receive this email too.
Can anyone help me?
Thank you!
Regards,
Qiuhong
*************************************************************************
This email message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message. [Delta Electronics, INC. China]
*************************************************************************
Hello,
I'm new to mailman3 and started to setup an instance from scratch per
hand, but I'm struggeling running the peaces with the correct
user/permissions.
I can't find anything regarding running this and that with that user in
the docs, so I have the following:
virtualenv_dir: /opt/venvs/mailman3
Installed packages in venv:
- "Django>=1.11"
- "django-haystack"
- "libsass"
- "mailman==3.3.0"
- "mailmanclient"
- "mailman-hyperkitty==1.1.0"
- "postorius==1.3.0"
- "hyperkitty==1.3.0"
- "whoosh"
- "uwsgi"
I have installed the core stuff in /opt/mailman3/core, all is owned by
user+group "mailman3":
root@host:/opt/mailman3# tree
.
├── core
│ ├── etc
│ │ ├── hyperkitty.cfg
│ │ ├── mailman.cfg
│ │ └── uwsgi.ini
│ ├── log
│ │ ├── bounce.log
│ │ ├── debug.log
│ │ ├── mailman.log
│ │ ├── plugins.log
│ │ └── smtp.log
│ └── var
│ ├── archives
│ │ └── hyperkitty
│ │ └── spool
│ │ ├── ...
│ ├── cache
│ ├── data
│ │ ├── mailman.db
│ │ ├── postfix_domains
│ │ ├── postfix_domains.db
│ │ ├── postfix_lmtp
│ │ └── postfix_lmtp.db
│ ├── lists
│ │ └── admin.lists....
│ ├── locks
│ ├── master.lck
│ ├── master.lck|...|...|...
│ ├── master.pid
│ ├── message"
│ │ ├── ...
│ ├── queue
│ │ ├── archive
│ │ ├── bad
│ │ ├── bounces
│ │ ├── command
│ │ ├── digest
│ │ ├── in
│ │ ├── nntp
│ │ ├── out
│ │ ├── pipeline
│ │ ├── retry
│ │ ├── shunt
│ │ └── virgin
│ └── templates
The django project is installed in /opt/mailman3/web, all is owned by
user+group "nginx":
└── web
└── project
├── db
│ └── mailmansuite.db
├── emails
├── fulltext_index
│ └── _MAIN_0.toc
├── logs
│ ├── mailmansuite.log
│ ├── uwsgi-error.log
│ └── uwsgi.log
├── manage.py
├── __pycache__
│ ├── settings.cpython-35.pyc
│ └── urls.cpython-35.pyc
├── run
│ └── uwsgi.sock
├── settings.py
├── static
├── urls.py
└── wsgi.py
The mailman3 core ist running with user+group "mailman3".
And the uwsgi service is running as root with drops privileges to
user+group "nginx".
Now, running the scheduled tasks (which run from user+group "nginx") for
django I ran into permission problems, because the nginx user can't
access/write to the needed files in /opt/mailman3/core/...
If anyone of you is able to read ansible tasks, this is how I set this
up via ansible:
https://github.com/freifunk-mwu/ansible-ffmwu/blob/mail/roles/service-bundl…
I would appreciate any hints how to run the different peaces of mailman3
with the correct user/groups/permissions.
Thanks in advance,
Tobias
On 9/23/19 12:03 AM, Paul Arenson wrote:
> Thank you Mark.
>
> I found my solution. Simplifies things. People do not have to even
> think about subscribing…..
<snip>
> How does that sound?
OK
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Hello all,
I'm currently trying to convert a Debian based mailman2 installation to
a docker based mailman3 installation.
I successfully running the mailman-web and mailman-core containers
together with the database container but I'm struggling with the import
of the old mailing lists. In the core container I'm running this two
commands for every mailing list:
mailman create mailman(a)example.com
mailman import21 mailman(a)example.com
/oldmailman/lists/mailman/config.pck
Then I'm switching over to the mailman-web container and running this
two commands:
python3.6 manage.py hyperkitty_import -l mailman(a)example.com
/oldmailman/archives/private/mailman.mbox/mailman.mbox
python3.6 manage.py update_index_one_list mailman(a)example.com
I'm getting no errors or something else which could indicate a problem.
After that I'm looking into the web interface
http://example.com/postorius/lists/
There I can only see the public mailing list and the private ones are
not shown there (as expected). When I then try to login with the List
Manager credentials of the lists (from mailman2) I can't login in. So I
thought maybe I have to "register" myself again to than get access to
the list management.
So I tried that but when I filled out the form and click "Register" I'm
presented with an error page which titles "Serverfehler" (Server error
in german) and the message "An error occurred while processing your
request."
When I then go back a step and try to register again I got the error
message that the username is already taken.
When I then try to login I can't login I always get the "An error
occurred while processing your request." page.
Does anyone have an idea what point I'm missing?
--
With best Regards
Uwe Grasshoff
I accidentally posted to a test account I had not actually used. Am reposting to my correct account. Sorry to the moderators.
In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself?
1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres…
2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below"
3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org
4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER?
5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows:
"Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account.
To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com"
6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list!
To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by
sending a message to....... I then get a notice:
"Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member"
7) While if they send FROM THE interface it goes through.
8) What I am confused about.
Signing up for an account should make them a member, right? Subscribing should make them a non member, no? But here it seems that both make them a non member. And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post.
Before I can move my actual members over from another mailing list provider, I want to make sure what works and what doesn't.
Thanks.
PS I am running out of test accounts to use to test my own setup. Thanks.
paul!!!Subscribe to this list
still shows up at the bottom.
Hello,
I've been getting "Cannot connect to SMTP server localhost on port 25"
from runner "out" in mailman.log over some mails stuck in shunt queue,
postfix logs show nothing when this happens, tcpdump on lo interface
port 25 shows nothing. The log shows up when I start mailman, and then
it seems not to show up again.
This is my mailman.cfg's relevant parts:
[mta]
verp_confirmations: yes
verp_personalized_deliveries: yes
verp_delivery_interval: 1
incoming: mailman.mta.postfix.LMTP
outgoing: mailman.mta.deliver.deliver
lmtp_host: localhost
lmtp_port: 8024
smtp_host: localhost
smtp_port: 25
configuration: python:mailman.config.postfix
I can do 'telnet localhost 25' just fine, including as mailman user. I
can send and receive mail on my mail server. I tried making a test list
and sent/received messages fine.
smtp debug logs show "Using agent: <mailman.mta.deliver.Deliver object
at 0x7fdd9793c940>" and "IndividualDelivery to: <email(a)address.tld>" on
repeat, where the email address is one of the addresses of the shunted
mails.
version 3.2.2
