Goodmorning everyone,
I'm setting up a mail server to manage a mailinglist.
I installed mailman3-full and configured everything.
I can create a list, add members to the list, but when I create a new thread, I only get it on the email from the same domain as the list. While all the other members of the list, they do not receive the thread.
I tried to check the logs, but I don't see anything significant.
What can I check?
Thank you in advance
Max
Hi Team,
I am currently running Mailman 3 with version 3.3.1 and in built
postfix version 2.10.1-6 on RHEL 7.5 in production environment from the
past 2 months almost.
Recently I observed a peculiar case. There is a list say
testlist(a)lists.testdom.com has a non member say testuser(a)testdom.com whose
Moderation attribute is set to "Accept immediately (bypass all other rules).
This testuser(a)testdom.com has sent a mail to testlist(a)lists.testdom.com
and postfix of my Maliman 3 received the request and handed over to Mailman
at 0.0.0.0:8024 socket running on the same machine and the same is logged
in /var/log/maillog.
Since the user has the moderation attribute set to Accept, the
/var/lib/mailman/mailman/var/logs/vette.log also displayed "ACCEPT" on
searching with the same message id.
At this point, to my expectations, there should be 2 entries for this
message id in smtp.log one for smtp and one for post. But I don't find any
log records with this message id in smtp.log and of course the mail is not
delivered even.
Could you please help me out if I have missed any point or improperly
understood the mail flow while using the mailman 3?
Please also let me know if I need to see any more log files for tracing
the issue.
--
Thanks & Regards,
Shashi Kanth.K
9052671936
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Hi,
A completely different question: Is there anyone that has a working
non-naive setup for ARC signing of mail list mail in mailman? I've
tried both the built-in version but it was not usable in the version I
tried for the case where there are several domains with different
selectors and keys and where the outgoing mail also is DKIM-signed.
This might be that the documentation is lacking but a very shallow
look in the source gave me the impression that the implementation is
limited to one domain which is not enough for my use case as I have
lists in several domains.
I use DKIM on outgoing mail with a setup where each domain has its own
keys and selectors. As discussed here earlier, the DKIM signature
should be added before the ARC signature. I have tried to use rspamd
after a tip here for this but without luck so far, but this is
somewhat off topic for mailman although related of course. rspamd
seems very good for other purposes and solves my other problems with
greylisting, DKIM-signing and spam filtering. That said, ARC seems
difficult to get to work for forwarded mails there also...
cheers
// David
Hi all,
I want to update some list member's display_name either with mailman shell or mailmanclient. These mostly aren't users in Postorius so I only want to operate on the subscribed list member. I've tried everything I can find in the docs and am stuck.
I've tried using `user_manager.get_user()` and then updating `user.display_name` followed by a `commit()` but it doesn't seem to persist the change.
The `absorb_existing` flag for mailmanclient's `User.add_address()` looks promising but the docs read "It will import the existing user into the current one, not overwriting any previously set value." which in some cases, the member already has a display_name set. I haven't tried this yet.
I'd appreciate any help pointing in the right direction.
Thanks,
Nick
Hi,
I am in the process of configuring a new mailman3 server based on my
old one. This includes upgrading to the latest version of mailman and
installing a database upgrade.
To my surprise mailman core started by sending tens of mails and
blocking the corresponding users for very old bounces. What is worse
is that this happens every time I start mailman core. Now I have
blocked (almost) all outgoing mail in postfix using a transport map
which discards it but this is a temporary testing measure of course.
When I deploy this server into production, I do not want these
recipients to be blocked as the old problems have been solved since
very long. My plan is to reload the database from a newer backup
anyway... Would it be enough to empty the bounce table (bounceevent)
or is there anything else driving this behaviour? Or is there a better
way to do this via the mailman shell? For me a "delete from
bounceevent" seems a lot simpler than anything via the shell but there
may be dependencies in the database.
Cheers
// David
This is actually an mbox file generated by mailman3.
(venv) mailman@mail:/opt/mailman/mm$ /opt/mailman/mm/bin/django-admin hyperkitty_import --since 2020-02-19 -l trackjunkies(a)pdc-racing.net /temp/archive/trackjunkies-new-1.mbox
Importing from mbox file /temp/archive/trackjunkies-new-1.mbox to trackjunkies(a)pdc-racing.net
\Traceback (most recent call last):
File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module>
sys.exit(execute_from_command_line())
File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 327, in handle
importer.from_mbox(mbfile)
File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 152, in from_mbox
for msg in mbox:
File "/usr/lib/python3.8/mailbox.py", line 109, in itervalues
value = self[key]
File "/usr/lib/python3.8/mailbox.py", line 73, in __getitem__
return self.get_message(key)
File "/usr/lib/python3.8/mailbox.py", line 781, in get_message
msg.set_from(from_line[5:].decode('ascii'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 27: ordinal not in range(128)
mailman 3.3.1 / core 3.1
Easy fix? I’m missing about 10 days' worth of archives as a result of this.
- Mark
-----
mark(a)pdc-racing.net | 408-348-2878
So I got a shiny new instance of Mailman3 installed (thanks Brian!).
I recreated my lists and I am now importing large historical list archives from an mbox file (24GB).
It takes a couple of hours to run this import, so I killed the import task after about 20 minutes so I could restart it in a screen session.
Now when I restart the import, it finishes almost immediately:
(venv) mailman@mail:/opt/mailman/mm$ /opt/mailman/mm/bin/django-admin hyperkitty_import -l trackjunkies(a)pdc-racing.net trackjunkies.mbox
Importing from mbox file trackjunkies.mbox to trackjunkies(a)pdc-racing.net
Computing thread structure
Synchronizing properties with Mailman
Warming up cache
The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list trackjunkies(a)pdc-racing.xn--net-to0a.
(venv) mailman@mail:/opt/mailman/mm$
Which is clearly not correct.
Anyone have an idea on how to restart this import?
THanks!
- Mark
-----
mark(a)pdc-racing.net | 408-348-2878
Hi!
After upgrading to HyperKitty 1.3.x I get the following error for
qcluster:
File ".../lib/python3.7/site-packages/django_q/cluster.py", line 300,
in pusher
task = SignedPackage.loads(task[1])
File ".../lib/python3.7/site-packages/django_q/signing.py", line 31,
in loads
serializer=PickleSerializer)
File ".../lib/python3.7/site-packages/django_q/core_signing.py", line
38, in loads
return serializer().loads(data)
File ".../lib/python3.7/site-packages/django_q/signing.py", line 44,
in loads
return pickle.loads(data)
AttributeError: Can't get attribute 'process_task_result' on <module
'hyperkitty.tasks' from
'.../lib/python3.7/site-packages/hyperkitty/tasks.py'>
How do I recover from that? It seems like there are still persisted
tasks in the qcluster queue using the old code from 1.2.x with the old
locking implementation.
Regards,
Florian Schulze
