Wikinaut writes:
[ADD] =?utf-8?q?John_=28Foo=29_Doe_=5Bcomment1=5D_=5Bcomment2=5D?=
That's called a MIME word, defined in RFC 2047. It's used when
something in a messages can't be presented verbatim, in this case
because the characters "()[]" have defined syntax in the context of an
address,
Krinetzki, Stephan writes:
> Now in the mailman.log I see the HOLD messages and the approved
> messages. The smtp.log logs just the incoming Mail, which seems to
> be fine.
By that you mean the incoming mail is fine? Or smtp.log is fine?
smtp.log should include two (or more) lines for each su
Wikinaut writes:
> When I use "mailman create --style-name MYSTYLE LISTNAME", I
> suppose MYSTYLE must be defined before, as this cannot be read from
> a file.
>
> When I use the code from
> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/docs/styles.html
> before,
Wikinaut writes:
> I suggest to modify the code so that all member preferences can be
> set via the command line.
They already can be set via "mailman shell", and common settings can
be automated using a withlist script.
> What do you think?
User preferences are extremely complicated becaus
Krinetzki, Stephan writes:
> The logrotate is executed by a system Timer (Rocky 9 OS btw) and is
> planned for: So every day at midnight.
OK, that's confirmed then.
> >That is not normal. Your control process is crashing every 15-20
> >seconds.
> I saw this but I don't have any idea how t
Krinetzki, Stephan writes:
> /opt/mailman/var/queue/bad:
> -rw-rw 1 mailman mailman 221723 Aug 1 17:26
> 1754061973.4885209+46b1ae3716439bf3ef98090296dfce0320fc3017.psv
This one might be spam, but it's weird that it managed to get pickled
but can't be read.
> -rw-rw 1 mailman ma
Mark Sapiro writes:
> Actually, there's more involved in the pipeline between the
> to_archive and to_outgoing handlers. The to-digest, to-usenet,
> after-delivery, acknowledge and dmarc handlers are all invoked
> between to_archive and to_outgoing
IIRC all of the shunted messages that Stephe
Stephan Krinetzki writes:
> And then there is a logrotate:
> And yes, this restarts mailman at midnight. Maybe i should optimize
> the logrotate.
Not sure what you mean by "optimize". Because of the bug I mentioned
earlier, in older versions of Mailman 3 the master process would fail
to close
I see Mark answered some of the same questions already, but it would
be really painstaking to avoid duplication (it took more than an hour
to write this :-), so I'm just gonna scan it quickly and then send.
Stephan Krinetzki writes:
> My queues:
(Omitting the empty ones.)
> /opt/mailman/var/qu
Willie Castillo writes:
> The spool directory now has 8 *.pck files in it. However, I do not
> see the original ones from 7/25
If you mean you don't see any files from 7/25 in the directory
listing, that's right, you won't. Processing a queuefile involves
rewriting the metadata in it (the arch
Mark Sapiro writes:
> On 7/28/25 13:29, Peter Adebahr via Mailman-users wrote:
> > we are receiving a few PGP-signed posts as a S/MIME attachment. Some
> > final recipients check these, and as mailman3 does not munge them - the
> > original mail is signed, not mailman3's final posts - those
willie.casti...@caemilusa.com writes:
> Looks like "hyperkitty" stopped archiving right after the CERT for
> the mailman3 website expired, How can I make the missing archives
> visible on the website? I see there "*pck" files in
> the/opt/mailman/mm/var/archives/hyperkitty/spool/ directory. Th
Christian Schneider writes:
> thank you very much for this detailed and elaborated answer.
You're welcome. I'm sorry I couldn't be more optimistic about
implementing the approach in Mailman.
At some point we in the Mailman project should probably consider
changing the authorization model. The
Christian Schneider writes:
> did you manage to disable the local registration (with django
> accounts)? I am trying to get rid of these locally registered
> accounts as well.
The easist way to do this is to require SSO authentication to access
webapps (this can be done in the front-end webse
Odhiambo Washington via Mailman-users writes:
> The subject appears as part of the output of `systemctl status
> mailman3`.
Nothing broke, so I don't see any hurry to "fix" this.
What is Falcon's suggested fix?
--
GNU Mailman consultant (installation, migration, customization)
Sirius Open So
Hi Paul
Glad you got that sorted! I wonder why those filters were in there?
Not really the kind of thing I'd expect Postfix to be doing out of the
box!
Looks like you didn't send to the list (at least, I got my copy via
personal mail, not the list). Replying for the benefit of
Mailman-Users (no
Asif Muzammil via Mailman-users writes:
> but in my server there is no directory located at
> var/archives/hyperkitty/spool/, i can see the spool
> /var/maliman/spool and there is no files in it
"var" with no leading slash "/" means the Mailman var_dir. You often
can find this set in the mail
johannes.wolf--- via Mailman-users writes:
> Unfortunately, we can't find out how to customise the subject of
> the email. Can anyone help us here?
You can add a prefix in Settings > List Identity > Subject Prefix. If
you want the conventional square brackets "[]" you must put them in
yourself
paul.spa...@us.idemia.com writes:
> I'm setting up a new mailman 3 server and doing some test posts to
How did you get Mailman? git? PyPI? Via the OS distro's packaging?
> a list. This server is intended only as an announcement list with
> limited members allowed to post. The resulting ema
Steve Brown writes:
> Yes, I intended to post to the list. I now see that if I use the
> archives to post (as I'm doing now),
As Mark said, you posted via Gmail (first Received header plus lots of
GoogleMail internal data).
> I don't see any apple iCloud,
Gmail, Yahoo, Hotmail users mostly
refrain from passing them on to my subscriber right now as they would
> probably seem like another PITA.
I agree on that one, although in the long run he'd probably be a lot
happier. Another possibility would be to keep a browser tab open on
HyperKitty's RADG page, and search auth
Steve Brown via Mailman-users writes:
> "For a while now, my e-mail for this list (but not other lists)
> just shows "To RADG" from "RADG" with a "CC" showing the actual
> sender's address.
It's very difficult to figure out what's going on with such an
abbreviated description of what he's seei
Hirayama, Pat writes:
> So, when I try adding entries to a separate vmap file, like:
>
> list-boun...@lists.domain.info lmtp:[mailman-core]:24, u...@gmail.com
>
> It only goes through normal bounce processing.
IIRC the usual configuration uses the virtual map as a transport
file. The tran
Markus Grandpré writes:
> many thanks for your reply. When I create a mailing list without an
> archive,
You cannot do that in Postorius. All of the "style" options provide
for an archive. "Ordinary discussion" and "announce" have public
archives, and the last option is "discussion with priva
Mark Sapiro writes:
> On 6/20/25 06:39, Christian Schneider wrote:
> > What I stumble upon is the RestAPI calls to create a "working"
> > user (with the ability to login via WebUI).
> > When I follow the manual (from the url above) I create a user
> > (including password) that appears in the
STR via Mailman-users writes:
> As for cPanel, that's what my hosting company uses. Since they are
> admirable in every other sense I don't want to leave them. So thank you
> very much for sorting this out.
Mark's point about cPanel is not a recommendation to avoid it, it's a
warning that in m
Jan Eden via Mailman-users writes:
> I did have the same issue about a month ago[1] with the current
> versions
That's the thread that Eggert replied to! ;-)
As Mark explains there, the fix is mildly complicated because *both*
settings are incompatible with some version or other of django-alla
Henry Hartley via Mailman-users writes:
> This isn't doing a lot for my self-esteem.
I don't think you need to worry about you. :-) There are dozens of
moving parts involved, each of which sets its own requirements and is
continuously being updated. And you're working in a virtual
environment,
Hi,
Although I'm replying to Thomas, I'm going to address this message to
Cathy.
Thomas Ward via Mailman-users writes:
> You'll have to talk to EMWD to see if your archives will be kept
> with the migration. They have a completely custom web interface for
> archival.
When I talked with Brian
roughnecks via Mailman-users writes:
> > if you look at this graph you'll notice how my VPS "reacted"
> > after mailman3 install.
Looks right to me. Mailman 3 was designed at a time when it was
reasonable to expect that a serious list host would be actual
hardware, configured pretty much exclu
Andreas Kemper via Mailman-users writes:
> Following this change, list continued operation as usual, but after
> a few days it seemed to be attacked via it's GUI, according to the
> attached Django error message.
If your users are not using socialauth login (that is, OAuth2 login
with ID provi
Odhiambo Washington via Mailman-users writes:
> I must have missed this if it was ever discussed, but is it
> possible to mask the list members' email addresses in the archives?
I saw Mark's response and Danil's issue, but I would recommend not
doing it even if available. People often do want
Christian Schneider writes:
> In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the
> format did not change.
I'm not sure what DATETIME_FORMAT is used for in Django 3.x.
According to the docs for the 'date' and 'time' filters, they both
accept a datetime object as argument, but they use
Steve Bachinsky writes:
> The lists are configured for “require_explicit_destination”.
> However, the email address of the list is clearly in the CC: header
> of the email (no alias or subdomain). Is there some other reason
> why Mailman would hold an email for moderation with the reason of
>
Odhiambo Washington via Mailman-users writes:
> > This is unexpected. What does - mean in that case? Is it unset and some
> > default (from the list?) is used?
>
> You are looking at the subscriber-level configs. The - means that the
> list default settings are used.
It could also
Odhiambo Washington via Mailman-users writes:
>
>
> Order allow,deny
I guess you're using mod_access_compat? Is there some reason you
*want* people using TOR to access the non-mutating methods? If I'm
not going to allow them to signup, I would just deny them acc
Stefan Bauer via Mailman-users writes:
> However venv/data/postfix_lmtp does not contain abuse@domain, so
> postfix rejects the mail.
acceptable_aliases is a Mailman 2 compatibility "feature". It may
contain regular expressions, so in general it is not possible to
update postfix_lmtp or postfi
Many lines removed from each file.
Alexander Inzinger-Zrock via Mailman-users writes:
> /etc/postfix/main.cf
> smtpd_recipient_restrictions = reject_non_fqdn_recipient
*> reject_non_fqdn_sender reject_unknown_sender_domain
*> reject_unknown_recipient_domain
> smtpd_relay_restrictions = per
Odhiambo Washington via Mailman-users writes:
> So this issue can be addressed by making Postorius to log user logins,
> right?
> However, I don't have the patch :)
I would guess it's probably possible to get Django to do this, quite
possibly using standard configuration to do so. I just don'
Hitashi mancho writes:
> *May 01 13:11:43 2025 (673989) li...@example.com :
> Discarded posting:From: us...@example.com
> Subject: subject 2025 - Reg.*
>
> In this log, it is unclear which moderator discarded this message. Is there
> any way we can add that to the log?
Not easil
Alexander Inzinger-Zrock writes:
> It seems i set both *facepalm* while doing [1] and then adding
> changes according to [2]:
It's OK to set both. But you need to coordinate "layout: LAYOUT" and
"[paths.LAYOUT]" if you are going to set any paths such as var_dir.
> so i have empty logs at /op
Matt Blissett via Mailman-users writes:
> Thanks ? it's version 3.1.3, so it's these lines:
> https://github.com/lepture/mistune/blob/v3.1.3/src/mistune/core.py#L212-L216
OK. The version bump and the assert suggest to me that they've made
significant changes. I don't know much about docker, b
Matt Blissett via Mailman-users writes:
> I get exceptions logged when certain pages in the email archives
> (imported from Mailman 2) are opened. For example, this thread:
>
> https://lists.tdwg.org/archives/list/tdwg-...@lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/
>
> Could t
Alexander Inzinger-Zrock via Mailman-users writes:
> What logs?
> Everything under /opt/mailman/mm/var/logs:
>
> + bounce.log
> + debug.log
> + mailman.log
> + plugins.log
> + smtp.log
>
> All empty.
As Odhiambo says, since Mailman 3 is apparently running, mailman.log
should have entr
za...@mta.ca writes:
> web interface but I see the error "Mailman REST API not
> available. Please start Mailman core." I can su to the mailman user
> and run 'mailman start -f' which seems to get things going again
> and shows the lists as they were before the snapshot, which is
> good, but
Hitashi mancho via Mailman-users writes:
> In Mailman 3, is there any way we can log the Owner/Moderator
> actions like moderator "x" approved the posting on
> l...@example.com?
These are logged to the "vette" logging channel, with level "info".
By default, the "vette" channel is directed to t
Hitashi mancho via Mailman-users writes:
> I have migrated around 300 mailing lists from Mailman 2 to Mailman
> 3. In most of the mailing lists we have configured
> "max_days_to_hold" to 2. It was working fine in Mailman 2. However,
> it is not working in Mailman 3.
This doesn't seem to be ex
Alexander Inzinger-Zrock via Mailman-users writes:
> + also checked that command ''postmap'' (under /usr/sbin) is available
> for user 'mailman' (usr/sbin was not in path; it is now).
This should not matter since the full path is in postfix.cfg, so
Mailman should find it and run it unless ther
Alexander Inzinger-Zrock via Mailman-users writes:
> B. /etc/postfix/main.cfg
> local_recipient_maps = proxy:unix:passwd.byname $alias_maps
> hash:/path-to-mailman/var/data/postfix_lmtp
This is the main issue for main.cfg. Others we can deal with later if
they apply to your system.
> C
dgoldsmith--- via Mailman-users writes:
> Here is the activity from the mailman.log file when I send a
> message to the list and it gets held:
Most of the activity you're interested in would be in smtp.log. The
interactions with the mail system are broken out into channels with
separate log fi
Hitashi mancho via Mailman-users writes:
> One of our users posted an email using a Bluemail Desktop client on one of
> the mailing lists. This email bounced with the reason "501 Message has
> defects".
Bouncing the message is arguably an overreaction to this particular
defect, but in fact Blu
Mihai Moldovan writes:
> In order for mailman to query the required data, it has to
> communicate with the archivers (like Hyperkitty) and that in turn
> means that the archiver must be running.
This is true for HyperKitty, it seems, but not true in general. As
long as the algorithm is indepe
Michael Richardson writes:
> Stephen J. Turnbull wrote:
> > that they're stable. Unfortunately, the email and web
> > environments are not, and dealing with changes in them is
> > often quite impractical given the Debian release cycle.
>
>
Mihai Moldovan writes:
> The imported messages, do have a Message-ID-Hash, but the
> Archived-At and List-Archive headers are empty (literally <>).
[...]
> What are the proper header values for this module?
Empty or omitted. See site-packages/mailman/archiving/prototype.py.
If they're produc
Michael Richardson writes:
> My upgrade was in part a response to the HTTP based attacks that used the
> signup
> form on mailman2 to attack people via SMTP with DOS. I know the IETF
> mailman2 install {now gone} had some kind of delay implemented in the web
> form before you could submit.
Michael Richardson writes:
> My problem, on lists.sandelman.ca aka lists.tcpdump.org, is
> messages that appear to have been processed by my MTA (according to
> postfix logs), but which are never delivered, nor held. Lost
> somewhere in mailman3 queue. Sometimes they show up after a host
>
Odhiambo Washington via Mailman-users writes:
> Curiously: If you DKIM sign your emails, does your ISP also co-sign
> them? Is your ISP relay server published in your domain's SPF
> records as an allowed sender for your domain?
These are both good points. AWS SES actually prohibts DYI DKIM-
Philip Bondi writes:
> [E]mails from banks, government, ecommerce or other important
> providers are distributed to multiple family members.
This an interesting application, but very likely to have delivery
issues because most financial institutions participate in the DMARC
protocol to control
Mihai Moldovan writes:
> Providing such wrappers as part of venv or the upstream repository
> is hence not possible.
We do provide them as Python scripts, which the wheels install in
"some reasonable place" such as $VENV/bin. I imagine this works fine
if you install to site-packages for the sy
Mihai Moldovan writes:
> But, all this said, mailman-web is typically already a wrapper
> calling su -s /bin/bash -c "python3 .../path/to/manage.py $*" www-data, so
> why should it be
> wrapped in another wrapper with a different user? The list user is typically
> used by the mailman-wrapp
Mihai Moldovan writes:
> # mailman-wrapper shell
> Welcome to the GNU Mailman shell
>
> >>> from mailman.testing.documentation import dump_json
> >>> from mailman.interfaces.mailinglist import IMailingList
> >>> from zope.component import getUtility
> >>> list_manager = getUtility(ILis
Mark Sapiro writes:
> On 4/7/25 17:45, MegaBrutal via Mailman-users wrote:
> > So it's even weirder – however, I'm really not sure if this is
> > the address HyperKitty is checking for, as I have 3 attached to
> > my account! How may I know which one it's trying to use?
>
> If you go to ht
Philip Bondi writes:
> [818] # journalctl -n 3000|grep postfi|grep "Apr 07 14:13"
> Apr 07 14:13:27 shackleton12 postfix/qmgr[3240968]: 88A222D6E:
> from=, size=2009, nrcpt=1 (queue active)
> Apr 07 14:13:27 shackleton12 postfix/qmgr[3240968]: warning: connect to
> transport private/lmtp: C
Prasanth Nair writes:
> Our Mailman3 server crashes with OOM and high CPU usage. As soon as we
> start the mailmanweb service (uwsgi process), the system crashes. It was
> working fine, but this issue started recently. We haven't changed any
> recently.
>
> Any idea how to fix this?
You're
Markus Grandpré writes:
> However, while using the many variables that can be sent with a
> template, I noticed that the resolution of the variable
> $hyperkitty_url is not working, even though i am using a private
> archive in this list and a URL to this archive exists.
That variable is docu
Michael, if you're going to "correct" people in public, you really
should try for a higher degree of accuracy.
Michael Bayer writes:
> support for different databases is the responsibility of GNU
> Mailman,
Not so. First, "responsibility" is something we explicitly disclaim
("no warrantee", "
via Mailman-users writes:
> I have a mailing list that, due to specific circumstances, has a
> requirement to allow messages from a user that sends messages with
> no subject.
Do you mean "any user who sends a message with no subject", or are
there specific users who do this? If there is one
Chandrakant Pandey via Mailman-users writes:
> Whether mailman 3.3.10 is compatible with mariadb 11.4 LTS
It should be. For details, you should ask the SQLAlchemy channels, as
Mailman delegates its communication with backend SQL databases to
SQLAlchemy.
Steve
__
Chandrakant Pandey via Mailman-users writes:
> I want to know whether we can setup nested mailing lists in
> mailman 3 which we used to do in mailman 2. like
> ep2...@iitb.ac.in,ep2...@iitb.ac.in,ep2...@iitb.ac.in mailing lists
> exist and we add all this mailing lists as member in
> e...
Chandrakant Pandey via Mailman-users writes:
> I want to know whether we can setup nested mailing lists in
> mailman 3 which we used to do in mailman 2. like
> ep2...@iitb.ac.in,ep2...@iitb.ac.in,ep2...@iitb.ac.in mailing lists
> exist and we add all this mailing lists as member in
> e...
Odhiambo Washington via Mailman-users writes:
> > connect to Unix domain socket */run/mailman3-web/uwsgi.sock*
>
> ^^
> uwsgi running outside virtualenv??
I don't think that's a problem, unless also running in a chroot, which
would
jko...@luc.edu writes:
> Looking at the queues, I see 27 .pck files under shunt from Nov
> 14th. Could that be the issue why moderators are not getting their
> e-mails right away?
No. That is way too old to be the cause of the current moderation
issue.
Presumably that occurred either at time
Philip Bondi writes:
> Again. We're almost there with ssl apache configs.
You're done with the Apache configuration for Mailman suite, it's
working. That's what the error message "Service Unavailable
The server is temporarily unable to service your request due to
maintenance downtime or capaci
Lance A. Brown writes:
> Does Mailman need interpolation active in its ConfigParser? Does
> it make sense to disable interpolation in the ConfigParser so other
> users don't run into the same issue? Apparently this was a change
> from python 2 to python 3. A la,
> https://stackoverflow.co
jko...@luc.edu writes:
> -Mailman was installed using the virtual environment.
> -Mailman info:
> -I use systemd to stop and start the services.
OK, this is all about as close to the environment most of the Mailman
devs run as you can get. On the one hand, it's easiest for us to
understand, b
Philip Bondi writes:
> I've never used the REST api before. I don't think it's working,
> yet, for me.
It pretty clearly is running and basically working.
> So I don't know how to dump my queues.
"Queues" in Mailman usually refers to email messages being processed.
As the name suggests, the
Joe,
It may help to have more information about what your system is like.
Specifically:
1. Did you install Mailman from our source distribution, from PyPI,
or from some other source?
2. Did you install Mailman in its own virtual environment?
3. When you run 'mailman info', does the output
Julian Kippels writes:
> I would like to configure Postorious in a way to disable the
> functionality to delete a list. Is there a way to do this?
You would have to patch the code. There are four levels to this:
1. You can hide the delete button on the list owner's view of the list
page.
za...@mta.ca writes:
> Ive had a look at historical posts and I think this might be
> related to this issue:
> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/IFX2YQDRKZJXI4J4DE54UGK7PV3KTDU4/#YXEDKCIZRCPE75L7S2ILSQOMJCC5NM2W
Pretty sure that is NOT the issue. This
Ulf R. writes:
> >>> msg.defects
> [CloseBoundaryNotFoundDefect()]
This means that the message declares a MIME multipart Content-Type,
and some part had a "start" boundary line but no "end" boundary line.
> Is there a quick fix for this available?
No. If the sending software isn't quite bro
Johan Alsina via Mailman-users writes:
> Hi, i installed mailman3 with virtualenv, all is working fine, the
> admin site works fine, the mailman(postorious) site works fine, but
> when im in hyperkitty the site shows without the css style.. in my
> web browser dev tool it shows like they loade
Andreas Vetter writes:
> it would be real great if owners that own several lists, but are
> not superusers, can see all users of all *their* lists and manage
> them. A down-"selected" version of the superusers view.
> Would that be possible?
Possible, yes. I don't know how to do it well eno
Andreas Vetter writes:
> A list of all addresses subscribed to all lists owned by the logged
> in person.
This is starting to take a better form. It's still very specialized,
so I'm starting to wonder if trying to add it to Postorius is a great
idea. Of course if people are coming in over the
Kyle Lahnakoski writes:
> I am setting up an email list for my local community (just myself
> right now). Being a nerd, I am using Amazon SES to send and
> receive emails.
Outgoing SES is full of unpleasant surprises. In particular, they
restrict use of certain headers (DKIM-Signature is the
Arte Chambers via Mailman-users writes:
> I am using an SMTP relay on my server. The relay provider is Brevo
> formally Send In Blue. I am wondering how I can verify weather message id
> or in-reply-to headers are being modified.
Most mail clients provide a "raw" or "original" or "source" mess
Arte Chambers via Mailman-users writes:
> Hello, my Hyperkitty is creating a new post for each reply in a
> thread. I would expect that new posts to a list would show up in
> the archive and once you click on that thread you would see all
> replies.
This is the default behavior if I understan
Markus Grandpré writes:
> When migrating the lists and archives from Mailman 2.1 to Mailman
> 3, the e-mail templates were obviously not migrated.
Which templates? Headers and footers are in the database, and they
should be migrated. The standard templates for autoreplies, moderator
notificat
Arpad Horvath via Mailman-users writes:
> I moved from mailman to mailman3 in 2021. I hadn't have the time to
> fix the archiving. I can see the emails older then that in
> Hyperkitty, but none of the once still there is mailman3. What can
> be the problem?
I don't understand "none of the onc
Eric Broens writes:
> Thank you for your reply.
> I have finally found what caused the problem after encountering the "HTTP
> Error 409: Subscription request already pending".
> Thanks to the archives of the mailman-users mailing list, I found out that
> there was a long list of pending confi
Torge Riedel via Mailman-users writes:
> I just experienced, that saving the settings of a list's non-member
> does not work with Postorius 1.3.13
You would need to look into the Postorius code that handles
preferences. I'd start here: postorius/src/postorius/views.py,
because it's not obvious
Odhiambo Washington via Mailman-users writes:
> You can read this thread:
> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/65PMB3J6SIHPI66HHKIKCGDFQMC677CU/
Good call, Odhiambo!
Also, the Django documents are voluminous. I think they're quite good
but YMMV on that.
Kim Sunggun via Mailman-users writes:
> Have you set any of those to other than default in your Django
> settings?
> everything is default.
What we're doing is not relevant because we're not trying to connect
to your MTA. Some of us do because our MTAs expect authentication or
are running on
Peter Knowles via Mailman-users writes:
> I'm referring to Postfix specific records, not Mailman records
> which are not the topic of conversation here.
I'm referring to a setup that works in practice on two sites (so far)
managing about 25,000 lists. No hash:postfix_* database files, no
recor
Peter Knowles via Mailman-users writes:
> In particular, with regards to Mailman 3 Core generated content. So
> instead of referencing a postmap generated file which MM3 presently
> generates, but have MM3 add and/or remove those records to/from a
> MariaDB table.
All that is already in the '
t.mai...@fz-juelich.de writes:
> > The trick to zero delivery downtime is that you can configure
> > your MTA to route to Mailman 3 if the list exists there, if not
> > route to Mailman 2 if the list exists there, and if not continue
> > to any lower priority routes. It worked as designed (mo
Johannes Rohr writes:
> Sorry, I should have looked into the script more closely. I simply had
> to set the variable CFG_PATH to the correct value.
Don't worry about it, we've all been through the experience of having
cockroaches in our systems. Just get your system sorted, and
everybody happ
via Mailman-users writes:
> Thank you for the reply. Ultimately, I ended up digging deeper
> into the allauth docs, per your suggestion, and I went a little bit
> further with the "SOCIALACCOUNT_ONLY" option. It turns out that
> the errors I were seeing were related to the sign up button
>
Jeremy Stanley writes:
> In our case, "as long as needed" is approximately forever, [...]
> since we'd rather not break random links elsewhere on the Web,
> e.g. in news articles that link to list discussions.
Yeah, that's a MAJOR consideration for MANY use cases. Be aware, folks!
It's a pr
Stephen J. Turnbull writes:
> This doesn't make any sense. That appears to be the listarchiver
> table. As far as I can tell in a quick grep, the only place that is
> mutated is in mailman/models/mailinglist.py:643 (line number is
> current HEAD), which happens whenever th
Tobias Diekershoff writes:
> On 22.11.24 07:59, Tobias Diekershoff wrote:
> > so far we could not find the reason behind the performance
> > problem.
Since you're already running two allegedly identical systems, have you
tried hitting the experimental one with the "do what the developers
recom
1 - 100 of 137 matches
Mail list logo
