Search results for "Postorius" - Mailman-users

Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: > On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> Since I made all the mailman3 enviroment wide server open (not using >> venv) I already executed the migration doing a >> >> su -m mailman3 -c "python3 manage.py collectstatic" >> su -m mailman3 -c "python3 manage.py migrate" >> >> Being mailman3 the user who runs all of mailman3 related stuff >> >> I had problems doing the migrate part, showing an error of lacking >> perms. I solved it running the migration under root (I know it could >> be trouble after, but...) > > It would be much better to identify the problem files/directories and > adjust their ownership. It is possible that running stuff as root in > the past left things owned by root causing the issue. The problem was in the intent of execute one of the migrate parts and showed about python files. I'm pretty sure that I've been very carefull not running things as root before as I know it can mess all up. But this time it was an dead end and I needed to go through. In a few days I will upgrade another server. I will document the error if I find it again. > >> >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS > I will try to trace it and comment what I find. Thaks a lot for your support. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 7 months

Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Guillermo Hernandez (Oldno7)

El 4/4/23 a las 3:31, Mark Sapiro escribió: > Guillermo Hernandez (Oldno7) wrote: > >> I thought I said it: I reboot this server everyday at 06:40 CEST time. >> That's why I'm sure it's not an undetected problem for weeks. The lists >> in this last upgraded server are with daily traffic. I'm suscribed to all. > > I've looked at this a bit further. Prior to Mailman core 3.3.4 we required aiosmtpd>=1.1. In 3.3.4 we required aiosmtpd>=1.4.1 and now we require aiosmtpd>=1.4.3. The code in aiosmtpd that triggers the issue in the socket module was added in aiosmtpd==1.3.1. So it is likely that your prior Mailman core version was <3.3.4 and your aiosmtpd dependency was <1.3.1, so the Mailman upgrade would also have upgraded aiosmtpd to a version which triggered the socket issue. I think tou are completely right about the aiosmtpd changes. But I had mailman 3.3.5 installed since end of september of '21, mailman 3.3.6 since end of october '22, and mailman 3.3.7 since the beginning of december of last year. You can search the list and find my messages about that upgrades and problems I had with them. Just to make it clear: It happened upgrading from 3.3.7 to 3.3.8 The upgrade procedure I did all the times is pip install --upgrade django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi and if I see some trouble I did it with a --force-reinstall parameter (not that I remember it happened last times that I upgraded) (and then the collectstatic, etc.) If I missed something, I don't know. > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at:https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/mess… > > This message sent toguillermo(a)querysoft.es > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 2 months

Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/9/24 12:32 AM, adam.heathcote(a)utas.edu.au wrote: > Hey there, > > We have a Mailman3 server with quite a few lists all running with no issues. > Recently I imported a list from our old Mailman 2 server which went fine. > > I attempted to remove the current owner and add myself but now when clicking on the list, Postorius shows: An error occurred while processing your request. > > The output of /opt/mailman/web/logs/mailmanweb.log is here: > > ERROR 2024-07-09 17:11:33,371 2795 django.request Internal Server Error: /mailman3/lists/net-ops.list.utas.edu.au/ > Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner > response = get_response(request) ... > TypeError: sequence item 1: expected str instance, NoneType found Was there more in the log? I.e., a line like The above exception was the direct cause of the following exception: followed by another traceback. If so, what was that? Is there anything in Mailman core's mailman.log? > I've tried removing it and reimporting it to no avail. Is there anything I can besides manually creating it and adding the members and owners from the old server? What do you get from Mailman's ``` mailman members -R owner your_list(a)your.domain ``` If this doesn't list you, try something like this: ``` $ mailman shell -l your_list(a)your.domain Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the your_list(a)your.domain mailing list >>> from mailman.app.membership import add_member >>> um = getUtility(IUserManager) >>> usr = um.get_user('adam.heathcote(a)utas.edu.au') >>> rr = RequestRecord(usr.preferred_address.email, usr.display_name, None) >>> add_member(m, rr, MemberRole.owner) >>> commit() >>> exit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: Is there an easy way to set Reply-To to a lists owner?

by Mark Sapiro

On 12/4/22 01:50, Martin Lorenz wrote: > > Now the admin of theses lists (who happens to be my wife) asked me, if it was possible to change the settings such that all replys to one of these lists can only be sent to herself (i.e. the owner address) instead of being held for moderation. > > I thought of setting Reply-To to something like <list-owner> by "simply" entering a Variable into this field, instead of using the admins/owners literal email-address. First of all, you can't really control where replies will go. This is dependent on the user's MUA and what the user does. However, you can set things so that replies will likely go where you want. Here are various options for the Postorius -> Alter Messages `Explicit reply-to address` and `Reply goes to list` settings. If the sender of all the posts to the list is the list owner, just set `Reply goes to list` to `No Munging` and a `reply` will go to the sender, but `reply-all` will go to the sender and the list, and if the user's MUA offers it, `reply-list` will go to only the list. To avoid the `reply-list` issue, set `Include the list post header` to `No` and to avoid the `reply-all` issue, set `Message Acceptance -> Require Explicit Destination` to `No` and post with the list address in Bcc:. If the sender is someone else, set `Explicit reply-to address` to `LISTNAME-owner(a)LIST.DOMAIN` and set `Reply goes to list` to `Explicit Reply-to set; no Cc added`. Also set `Include the list post header` to `No` and consider setting `Message Acceptance -> Require Explicit Destination` to `No` and posting with the list address in Bcc: as above. Note that `LISTNAME-owner(a)LIST.DOMAIN` is the list posting address with `-owner` added to the local part. This address forwards to the list's owners and moderators. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: Approve an email

by Lars Bjørndal

[Eggert] > Not sure about Fedora, but there seem to be some issues with distribution > specific packages. Many users have got good results with the virtualenv > installation described here: > > https://docs.mailman3.org/en/latest/install/virtualenv.html Thank you! I gave it a try. I installed postgresql and postgresql-server, created the databases according to the guide and tried to start mailman. I get this error: ===== Traceback (most recent call last): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3361, in _wrap_pool_connect return fn() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 325, in connect return _ConnectionFairy._checkout(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 888, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 491, in checkout rec = pool._do_get() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/impl.py", line 145, in _do_get with util.safe_reraise(): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/impl.py", line 143, in _do_get return self._create_connection() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 271, in _create_connection return _ConnectionRecord(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 386, in __init__ self.__connect() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 684, in __connect with util.safe_reraise(): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 680, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/create.py", line 578, in connect return dialect.connect(*cargs, **cparams) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/default.py", line 598, in connect return self.dbapi.connect(*cargs, **cparams) File "/opt/mailman3/venv/lib64/python3.10/site-packages/psycopg2/__init__.py", line 127, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication failed for user "mailman" The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman3/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.7', 'console_scripts', 'mailman')()) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 1054, in main with self.make_context(prog_name, args, **extra) as ctx: File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 920, in make_context self.parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 1613, in parse_args rest = super().parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 1378, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 2360, in handle_parse_result value = self.process_value(ctx, value) File "/opt/mailman3/venv/lib64/python3.10/site-packages/click/core.py", line 2322, in process_value value = self.callback(ctx, self, value) File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/bin/mailman.py", line 95, in initialize_config initialize(value) File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/core/initialize.py", line 229, in initialize initialize_2(propagate_logs=propagate_logs) File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/core/initialize.py", line 187, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/database/factory.py", line 58, in create SchemaManager(database).setup_database() File "/opt/mailman3/venv/lib64/python3.10/site-packages/mailman/database/factory.py", line 86, in setup_database context = MigrationContext.configure(self._database.store.connection()) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/orm/session.py", line 1542, in connection return self._connection_for_bind( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/orm/session.py", line 1552, in _connection_for_bind return self._transaction._connection_for_bind( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/orm/session.py", line 747, in _connection_for_bind conn = bind.connect() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/future/engine.py", line 406, in connect return super(Engine, self).connect() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3315, in connect return self._connection_cls(self, close_with_result=close_with_result) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 96, in __init__ else engine.raw_connection() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3394, in raw_connection return self._wrap_pool_connect(self.pool.connect, _connection) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3364, in _wrap_pool_connect Connection._handle_dbapi_exception_noconnection( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 2198, in _handle_dbapi_exception_noconnection util.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 3361, in _wrap_pool_connect return fn() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 325, in connect return _ConnectionFairy._checkout(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 888, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 491, in checkout rec = pool._do_get() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/impl.py", line 145, in _do_get with util.safe_reraise(): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/impl.py", line 143, in _do_get return self._create_connection() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 271, in _create_connection return _ConnectionRecord(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 386, in __init__ self.__connect() File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 684, in __connect with util.safe_reraise(): File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/pool/base.py", line 680, in __connect self.dbapi_connection = connection = pool._invoke_creator(self) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/create.py", line 578, in connect return dialect.connect(*cargs, **cparams) File "/opt/mailman3/venv/lib64/python3.10/site-packages/sqlalchemy/engine/default.py", line 598, in connect return self.dbapi.connect(*cargs, **cparams) File "/opt/mailman3/venv/lib64/python3.10/site-packages/psycopg2/__init__.py", line 127, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication failed for user "mailman" (Background on this error at: https://sqlalche.me/e/14/e3q8) ===== And here I'm stucked. I have very litle experience with databases, so I don't know how to debug. Any hint? Thank you Lars > Am Montag, 26. Dezember 2022, 21:08:46 CET schrieb Lars Bjørndal: > > Hi, list! > > > > I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and > > postorius-1.3.6-2.fc36.noarch installed. with the command > > > > sudo -u mailman mailman3 create <listname> > > > > I was able to create a list. > > > > I'm not able to find out how to setup and configure the postorius > > package. There's no mailman-web command. > > > > Hyperkitty will not installed du to a dependency conflict, but I dont > > need archiving for the list. > > > > Here comes my quesitons: > > > > - What's the easiest way to approve an email sent to the list? > > > > - How can I configure the list to accept messages also from non members? > > > > - How can I setup postorius to work on Fedora? I have django-admin, but > > I'm not sure where to go. > > > > Thanks in advance, Lars > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > Archived at: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message > > /ZDUDQA57QRLF7QD4KPFIZBC6ZIF2FAVP/ > > > > This message sent to eggert(a)eehmke.de > > > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

3 years, 5 months

Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS While I'm tracing the problem out, this is the configuration I had working and the error it shows after upgrade: <------- snip of settings.py> # COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) # On a production setup, setting COMPRESS_OFFLINE to True will bring a # significant performance improvement, as CSS files will not need to be # recompiled on each requests. It means running an additional "compress" # management command after each code upgrade. # http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression #### activo compresion 18/12/20 COMPRESS_OFFLINE = True ###COMPRESS_OFFLINE = False <---------- end snip> And below is the error it shows: /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" Traceback (most recent call last): File "/usr/local/mailman3/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 279, in fetch_command klass = load_command_class(app_name, subcommand) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 49, in load_command_class return module.Command() File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 274, in __init__ raise TypeError("requires_system_checks must be a list or tuple.") TypeError: requires_system_checks must be a list or tuple. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 7 months

Re: CPU usage when idle

by Stephen J. Turnbull

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 exclusively for the use of the MTA, an httpd, an RDBMS, and the Mailman suite on at least consumer-grade hardware (at that time one-core CPU, 4GB RAM, 25+GB HDD). Sooo ... By default Mailman core will be running about 15 processes, Postorius about 3, HyperKitty up to about 8 I think, the webserver will be running a bunch, if your MTA is Postfix that will be running a bunch of daemons and firing up worker processes whenever there's something to dov, you'll probably be running a bunch of ancillary daemons for mail (opendkim, Spamassassin, clamav, Amavis) and your RDBMS will be running a couple. Mailman's queue runners (about half of its processes) all wake up frequently and check for work. Janitorial processes like crond and logrotate will have more to do (even if all they do is check that there's nothing to do). You'll be responding to the Internet on multiple ports (most likely all of 22, 25, 80, 443, and 587, maybe a couple more) which will attract the usual conglomeration of Internet busybodies and felons unless you're more diligent than I am about "iptables -A -s x.y.z.w -j DROP" for miscreant x.y.z.w :-). Somebody posted a couple months back that they were working on a fork of Mailman 3 that would use threads rather than processes as much as possible, but that sounds quite hard (so we're unlikely to do it ourselves) and I haven't heard anything since. And although that would definitely help get LOADAVG down, it wouldn't help that much with %CPU since it doesn't do anything to deal with the busybodies and miscreants pounding on your open ports. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year

Re: Change the default value for the General Archive Policy

by Mark Sapiro

On 6/23/25 08:03, Markus Grandpré wrote: > Dear list, > > currently, when I create a new mailing list with MM3 the value for > "Archive policy" is always set to "Public archives". I'd like to change > the default value for "Archive policy" to "Do not archive this list". > How can I do this? In Debian 12 I find in > </usr/lib/python3/dist-packages/postorius/forms/list_forms.py>: ... > but have no idea how to change the settings here. Your help is very > appreciated. Are you creating the list in Postorius. If so, you have a choice for list style. Currently those choices are: ``` Announce only mailing list style. Ordinary discussion mailing list style. Discussion mailing list style with private archives. ``` There is currently no style for a list without archives, but you can implement one. See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… for hints on how to do this with a plugin. Alternatively, you can do it with a patch like: ``` --- a/src/mailman/styles/default.py +++ b/src/mailman/styles/default.py @@ -18,6 +18,7 @@ """Application of list styles to new and existing lists.""" from mailman.core.i18n import _ +from mailman.interfaces.archiver import ArchivePolicy from mailman.interfaces.styles import IStyle from mailman.styles.base import ( Announcement, @@ -91,3 +92,25 @@ class PrivateDefaultStyle( Private.apply(self, mailing_list) Discussion.apply(self, mailing_list) Moderation.apply(self, mailing_list) + + +@public +@implementer(IStyle) +class PublicNoArchiveStyle( + + Identity, BasicOperation, Bounces, Public, Discussion, Moderation): + + """The legacy default style with no archives.""" + + name = 'legacy-default-no-archive' + description = _('Ordinary discussion mailing list style with no archive.') + + def apply(self, mailing_list): + """See `IStyle`.""" + Identity.apply(self, mailing_list) + BasicOperation.apply(self, mailing_list) + Bounces.apply(self, mailing_list) + Public.apply(self, mailing_list) + Discussion.apply(self, mailing_list) + Moderation.apply(self, mailing_list) + mailing_list.archive_policy = ArchivePolicy.never ``` If you are creating lists from the command line `mailman create`, there is a --style-name option to specify the style. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 4 weeks

Re: MM3 Postfix FROM header issue

by eboltz＠lhtservices.com

Mark, Here is my postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases always_add_missing_headers = yes append_dot_mydomain = no biff = no compatibility_level = 2 default_destination_concurrency_limit = 15 default_destination_recipient_limit = 30 header_checks = regexp:/etc/postfix/header_checks header_size_limit = 409600 inet_interfaces = all inet_protocols = ipv4 local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp mailbox_size_limit = 0 mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain myhostname = lists.example.com mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname readme_directory = no recipient_delimiter = + relay_domains = hash:/var/lib/mailman3/data/postfix_domains relayhost = [mail.smtp2go.com]:587 smtp_always_send_ehlo = yes smtp_sasl_security_options = noanonymous smtp_tls_CApath = /etc/postfix/o365_smtp_cert.pem smtp_tls_security_level = may smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtp_use_tls = yes smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_security_level = may transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp unknown_local_recipient_reject_code = 550 virtual_alias_maps = hash:/var/lib/mailman3/data/postfix_vmap I think that I may try to start from scratch with postfix, as it doesn't seem to do what I want. This is what I'm trying to do based off the clients existing MM2 setup, which I'm building MM3 from scratch on an entire new system. I wasn't involved with their old MM2 setup from years ago, so not quite sure how it was fully setup to route emails from the mailman.example.org (virtual domain) Current client setup: - MM2 is hosted on a separate system, then relays emails through an on-prem SMTP relay (physical server) - example.org (their email domain) but routes through mailman.example.org - They have contacts configured in their existing example.org email system, which route on a 1:1 to their matching mailman.example.org counterparts New client setup: - MM2 is hosted on a separate system, but relays emails through either SMTP2GO or O365 (whichever is easiest) - example.org (their email domain) but will use lists.example.org for the MM3 lists What would I have to do to ensure that MM3 and postfix (same new server) use the newly created lists.example.org domain, which only exists within Postfix when setting up the Postorius domain and lists? I want to have it so that whatever the list name is, for example 'Staff(a)lists.example.org' will route through Postfix correctly.

2 years, 6 months

Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/29 16:52, Odhiambo Washington wrote: > > On Mon, Jul 29, 2024 at 5:26 PM Roland Giesler via Mailman-users > <mailman-users(a)mailman3.org> wrote: > > > I added the following to my mailman3-web.py: > > EMAIL_USE_SSL = True > EMAIL_HOST = 'box2.gtahardware.co.za <http://box2.gtahardware.co.za>' > EMAIL_PORT = '465' > EMAIL_HOST_USER = 'roland(a)giesler.za.net' > EMAIL_HOST_PASSWORD = '<redacted>' > > and fixed the "DEFAULT_FROM_EMAIL" and the signup email gets sent > successfully! > > > Can you please share what was logged by mailman3-web during the > email-sending process? [pid: 10018|app: 0|req: 3/3] 192.168.131.150 () {48 vars in 966 bytes} [Mon Jul 29 15:25:33 2024] GET /accounts/confirm-email/ => generated 6638 bytes in 55 msecs (HTTP/1.1 200) 7 headers in 223 bytes (1 switches on core 0) [pid: 10018|app: 0|req: 4/4] 192.168.131.150 () {44 vars in 812 bytes} [Mon Jul 29 15:27:01 2024] GET / => generated 0 bytes in 3 msecs (HTTP/1.1 301) 8 headers in 264 bytes (1 switches on core 1) [pid: 10018|app: 0|req: 5/5] 192.168.131.150 () {44 vars in 844 bytes} [Mon Jul 29 15:27:01 2024] GET /postorius/lists/ => generated 4140 bytes in 343 msecs (HTTP/1.1 200) 7 headers in 223 bytes (1 switches on core 0) [pid: 10018|app: 0|req: 6/6] 192.168.131.150 () {46 vars in 942 bytes} [Mon Jul 29 15:28:55 2024] GET /accounts/login/?next=/postorius/lists/ => generated 8947 bytes in 42 msecs (HTTP/1.1 200) 8 headers in 391 bytes (1 switches on core 1) [pid: 10018|app: 0|req: 7/7] 192.168.131.150 () {54 vars in 1104 bytes} [Mon Jul 29 15:29:07 2024] POST /accounts/login/ => generated 0 bytes in 1067 msecs (HTTP/1.1 302) 10 headers in 559 bytes (1 switches on core 0) [pid: 10018|app: 0|req: 8/8] 192.168.131.150 () {48 vars in 1132 bytes} [Mon Jul 29 15:29:08 2024] GET /accounts/confirm-email/ => generated 7190 bytes in 7 msecs (HTTP/1.1 200) 8 headers in 321 bytes (1 switches on core 1) > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > In an Internet failure case, the #1 suspect is a constant: DNS. > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

Mailman-users search results for query "Postorius"