Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: SPF check fails for lists subdomain

by Odhiambo Washington

On Thu, Jan 5, 2023 at 10:56 AM Jan Eden via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2023-01-04 15:07, Mark Sapiro wrote: > > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > > Although I could specify the IP address in my SPF records directly (as > > > you suggested), I do hope that my understanding of DNS records laid out > > > above is not entirely misguided. My current setup does work as expected > > > for eden.one, after all. > > > > As I said at < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > I was misreading your DNS and now I am as puzzled as you about the > failure. > > It gets even more mysterious. I tried sending messages from both > lists.eden.one and janeden.net (my other domain) to a gmail account and > to another mail provider. Both messages passed the SPF checks on both > services (s. the relevant headers quoted below). Now because I send > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > check operates (and succeeds) on e.g. > > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > (and not on somethingsomething(a)lists.eden.one or > somethingsomething(a)janeden.net) Could this be the reason for the failed > SPF checks in Yahoo's and Google's DMARC reports? > > - Jan > Might you be willing to use proven tools instead of trying so hard to understand the myth? I use https://easydmarc.com/tools#spf-tools It allows me to generate, lookup, test SPF, DKIM, DMARC, etc. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by David Newman

On 1/11/22 12:39 PM, gordon(a)dickens.com wrote: > 2) Install mailman3 using the venv and web instructions as suggested in this thread. I plan to use mysql (mariadb) since my database was originally implemented with mysql. I too use MariaDB. Here are the MariaDB-specific variations from the venv and web docs: 1. Before going through the venv docs I installed these packages: libmariadb3 libmariadb-dev default-libmysqlclient-dev 2. When installing mailman in venv, I did this: (venv)$ pip install --upgrade pip (venv)$ pip install wheel mailman pymysql mysqlclient 3. In /etc/mailman.cfg, the database config looks like this: .. [database] class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8mb4&use_unicode=1 .. The url is all one line (it's wrapping in my mail client). 4. The [Unit] section of /etc/systemd/system/mailman3.service looks like this: [Unit] Description=GNU Mailing List Manager After=syslog.target network.target mariadb.service .. Note that this is on a Debian 11 system. On Debian 10 and previous, it'd be mysql.service instead of mariadb.service. 5. The settings.py file includes this section: .. # MySQL database setup. DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailmanweb', 'USER': 'mailman', 'PASSWORD': '<password>', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': {'charset': 'utf8mb4'} # Enable utf8 4-byte encodings. } } .. Note that your NAME, USER, PASSWORD, and possibly HOST may differ. 6. The [Unit] section of /etc/systemd/system/mailmanweb.service looks like this: [Unit] Description=GNU Mailman Web UI After=syslog.target network.target mariadb.service mailman3.service .. Same caveat as with step 4 that this is for Debian 11, and you'd use mysql.service instead on Debian 10 and previous. I think that's all the changes, but if I've omitted something I hope Mark Sapiro or someone else can step in. dn

3 years, 5 months

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by nate

On 2022-01-26 9:37, Mark Sapiro wrote: > Posts to this list from non-members are discarded without notice. OK good to know, thanks. Didn't want one of my main email addresses to be leaked to the list (I have ~550 email addresses normally have one per purpose). > Your initial post was held because all new members are moderated by > default. This is an anti-spam measure. If you post on topic, we clear > your moderation. Can I suggest the messaging to new users be improved to communicate this situation as it is not clear. The automated message I got said this was the reason my message was held: The message comes from a moderated member. Which makes sense if I REALLY think about it(I was a moderated member at first), but then the next question is why was I moderated. Your explanation makes sense. It would be nice if it had more info along the lines of what you said, or even better adjust the messaging for the "Welcome" email to indicate your first message(s) will be held for moderation(I checked both emails I got back from the list just now to verify this info is not there). I was confused for a while(again 21 year veteran of mailman) thinking I sent my message using the wrong email address, after confirming I sent with the right one I just decided to wait to see what would happen. If you can adjust the messaging it would be good I think to make it really clear all CAPS, or putting **** message here **** in the email so it really stands out to the new users what the situation is. > And yes, Mailman 3 doesn't (yet?) have a way for ordinary users to > delete their own held posts. good to know too, thanks! nate

3 years, 5 months

[MM3-users] Re: Things I miss about mailman2

by Quanah Gibson-Mount

Hi Mark, --On Tuesday, March 17, 2020 1:43 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > The message comes from Mailman core. Mailman core does not know what > web management UI you are using or the URI to access it. You need to > change the template for the message to include the URL. Ok great, thank you!. >> b) When a post is made to a moderated list in mailman2, when I went to >> the page to approve/deny/discard, there was additionally an option to >> remove the moderated flag from the user for all future emails. This >> option no longer exists. This was EXTREMELY useful, as we force all new >> members of the list to be moderated for a time while we evaluate the >> quality of their postings. Now I have to go manually track down the >> user and their settings. Unnecessary extra hoops to jump through > > > Click on the subject in the held messages list. At the bottom of the > dialog that opens, there is a drop down to set the user's moderation. > Normally, you would set it to 'default processing'. I do not see any such option. After clicking on the header the only options available at the bottom are: Accept, Reject, Discard, Show Source, Show Header There are zero drop downs anywhere. > This was not "removed". It just hasn't been implemented in MM 3 yet. So in terms of available functionality that was present in MM2, it was removed. It may need to be re-implemented, but this was a core feature that was present in the prior version that is no longer available. --Quasnah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 3 months

[MM3-users] Re: Change digest frequency and default threshold

by Henrik Rasmussen

Thanks for the hints. It looks to be a file permission problem. I am not sure what the right persommions should be inside he container. Is there a command for checking file permissions, like the Mailman 2's command check_perms? I couldn't file one. Mark Sapiro wrote: > Something is going wrong in this process in DigestRunner. Is > DigestRunner running? Yes: 43 mailman 2:05 /usr/local/bin/python /usr/local/bin/runner -C /etc/mailman.cfg --runner=digest:0:1 > Is there anything in Mailman's digest or shunt > queues? As of /opt/mailman/core/var/queue/digest/ and /opt/mailman/core/var/queue/shunt/ no, but there is three files in /opt/mailman/core/var/queue/bad/ -rw-rw---- 1 root root 398 Oct 10 14:42 1539175326.8246331+4b7e80db0d22f01c2d4363e323320fcd34560657.psv -rw-rw---- 1 root root 398 Oct 11 12:11 1539252672.3947155+ae2631d9f6514d74c77a38f09f821ee71515f9d9.psv -rw-rw---- 1 root root 398 Oct 11 12:24 1539253469.5928977+15b0842462ddd3abcac8d688e5bbb195b07409bc.psv They seems to be binary, buy strings reveal: mailman.email.message Message policy email._policybase Compat32 _headers _unixfrom _payload _charset preamble epilogue defects _default_type text/plain listid test.lists.example.com digest_path =/opt/mailman/var/lists/test.lists.example.com/digest.1.9.mmdf volume digest_number version _parsemsg If that reveals anything. > Is there anything logged in Mailman's 'mailman' log? It seem to say PermissionError: [Errno 13] Permission denied, but inside the container, the directoried in /opt/mailman/var/queue is drwxrwx--- 2 mailman root 4096 Mar 14 2018 archive drwxrwx--- 2 mailman root 4096 Oct 12 10:14 bad drwxrwx--- 2 mailman root 4096 Mar 14 2018 bounces drwxrwx--- 2 mailman root 4096 Mar 14 2018 command drwxrwx--- 2 mailman root 4096 Oct 11 10:24 digest drwxrwx--- 2 mailman root 4096 Oct 12 10:07 in drwxrwx--- 2 mailman root 4096 Mar 14 2018 nntp drwxrwx--- 2 mailman root 4096 Oct 12 10:07 out drwxrwx--- 2 mailman root 4096 Oct 12 10:07 pipeline drwxrwx--- 2 mailman root 4096 Mar 26 2018 retry drwxrwx--- 2 mailman root 4096 Mar 14 2018 shunt drwxrwx--- 2 mailman root 4096 Oct 10 12:32 virgin Henrik Rasmussen

6 years, 8 months

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Shashikanth Komandoor

Hi Mark, Thank you for your response. And sorry for not giving you complete information as I am not sue what to share with you. I am using Postgresql-11.7 as my backend database. The below is the structure of the address table in* mailman *database: mailman=# \d address; Table "public.address" Column | Type | Collation | Nullable | Default ----------------+-----------------------------+-----------+----------+------------------------------------- id | integer | | not null | nextval('address_id_seq'::regclass) email | character varying | | | _original | character varying | | | display_name | character varying | | | verified_on | timestamp without time zone | | | registered_on | timestamp without time zone | | | user_id | integer | | | preferences_id | integer | | | Indexes: "address_pkey" PRIMARY KEY, btree (id) "ix_address_email" UNIQUE, btree (email) "ix_address_preferences_id" btree (preferences_id) "ix_address_user_id" btree (user_id) Foreign-key constraints: "address_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES preferences(id) "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) Referenced by: TABLE ""user"" CONSTRAINT "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL TABLE "autoresponserecord" CONSTRAINT "autoresponserecord_address_id_fkey" FOREIGN KEY (address_id) REFERENCES address(id) TABLE "member" CONSTRAINT "member_address_id_fkey" FOREIGN KEY (address_id) REFERENCES address(id) TABLE "onelastdigest" CONSTRAINT "onelastdigest_address_id_fkey" FOREIGN KEY (address_id) REFERENCES address(id) The below is the structure of *user* table: mailman=# \d user; Table "public.user" Column | Type | Collation | Nullable | Default -----------------------+-----------------------------+-----------+----------+---------------------------------- id | integer | | not null | nextval('user_id_seq'::regclass) display_name | character varying | | | password | character varying | | | _user_id | uuid | | | _created_on | timestamp without time zone | | | is_server_owner | boolean | | | _preferred_address_id | integer | | | preferences_id | integer | | | Indexes: "user_pkey" PRIMARY KEY, btree (id) "ix_user__user_id" btree (_user_id) "ix_user_preferences_id" btree (preferences_id) Foreign-key constraints: "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL "user_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES preferences(id) Referenced by: TABLE "address" CONSTRAINT "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) TABLE "domain_owner" CONSTRAINT "domain_owner_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) TABLE "member" CONSTRAINT "member_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) mailman=# \dn List of schemas Name | Owner --------+---------- public | postgres (1 row) mailman=# select * from user; user ---------- postgres (1 row) *The above command output is not showing any fields. But if use the table as public.user (schema.tablename) with select command, it is showing the data. But without schema name this table is not showing those fields. Not sure if this the expected behavior or not.* I have not done any changes. Few days back I made DR machine up as I am taking primary into maintenance. The entire database was running streaming replication and I even kept the /var/lib/mailman directory in sync where all the components are installed. Please let me know if any more things I need to share. On Mon, Jul 27, 2020 at 7:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 10:56 AM, Shashikanth Komandoor wrote: > > 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. > > > > From the past few days, I found my server is responding to the users > > very slowly and throwing the Server Error page (of course getting the > > required page after multiple refreshes) for almost every click on the > > postorius pages (not yet observed on hyperkitty front end which in fact > is > > not so important for me as of now). > > > > During that time, I observed in the mailman.log an error message > saying > > "Could not locate column in row for column 'user.id'". The complete > > traceback log is attached with the mail. The error message is generated > for > > almost all the lists and all the clicks. > > > I don't understand what's going on. I suspect some kind of database > corruption, but I don't know what. > > The traceback indicates Mailman is getting the Members of a list and in > this process is trying to get the display_name for a member. The > member's subscriber attribute doesn't have a display_name so it is > trying to get is from the member's user attribute so it is trying to get > the user record for the member's email address via > IUserManager.get_user(). This in turn gets the Address record for the > email address and returns it's user attribute. > > This leads to the > > sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for > column 'user.id'" > > error which I don't understand. There is no table with a 'user.id' > column. user.id refers to the id column in the user table which comes > from the user_id column in the address table which should be a reference > to the id column in the user table, not a reference to ay 'user.id' > column. > > What is your backend database and what is the structure of the address > table in that database. Have you done any kind of direct database query > that might have affected this? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 11 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

Running into some nasty issues. I have a structure like this, installed as a package in the workspace once installed by pip in the venv: mailman_customizations/ __init__.py hooks.py <-- plugin definition in here as MailmanCustomizations for class name handlers/ __init__.py handlers.py <-- custom handler in here pipelines/ __init__.py pipelines.py <-- custom pipelines which implement the handlers here. However, whenever I specify this in config with this clause: [plugin.MailmanCustomizations] class: mailman_customizations.hooks.MailmanCustomizations enabled: no ... I get a hard load error on "ModuleNotFoundError: No module named 'MailmanCustomizations'" To confirm this is a Python module/class, I did a pure python shell with `from mailman_customizations.hooks import MailmanCustomizations` and it properly imports that class, so I'm not sure where to go from here in debugging. Thomas On 10/24/23 11:55, Thomas Ward via Mailman-users wrote: > Perfect, that should make things easier for me to install. > > Thank you kindly for all your support everyone! > > > Thomas > > > On 10/24/23 11:54, Mark Sapiro wrote: >> On 10/24/23 8:20 AM, Thomas Ward via Mailman-users wrote: >>> >>> This means I can install the code to anywhere on `sys.path` that the >>> system can detect and it does not need to be in the Mailman3 >>> library/directory space in the venv? >> >> Yes, as long as Mailman can import the class defined for the plugin >> in mailman.cfg, it will work. >> > _______________________________________________ > 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 teward(a)thomas-ward.net

1 year, 8 months

[MM3-users] Re: OS upgrade - anything to take care of?

by Ruth Ivimey-Cook

Mark, While the venv will to a degree isolate you, my experience of the upgrade from 18 to 20 was that python3.6 was uninstalled and 3.8 installed. In this scenario, the mailman3 installation is subsequently broken because there is no python to run. It *is* possible to reinstall python3.6 after the dist upgrade is complete, and I would presume that after doing so mailman3 would probably resume ok. In my case I decided to continue using 3.8, which meant, in essence, rebuilding my mailman3 install -- not fun given my state of knowledge. I would therefore appreciate some guidance on performing the upgrade from 3.6 to 3.8 with the minimum of fuss. [I am not sure, but it could be possible to install python3.8 while using Ubuntu 18, so that the dist upgrade never breaks anything. Worth exploring.] Ruth On 13/05/2021 19:02, Mark Sapiro wrote: > On 5/13/21 7:25 AM, Torge Riedel wrote: >> today I upgraded one of two servers from Ubuntu 18.04 to 20.04 and - >> besides some minor config updates - postfix & dovecot worked well >> afterwards. >> >> So I am very optimistic that the upgrade of the second server from 18.04 >> to 20.04 will also work fine. But the second server is running MM3 >> (installed in venv) and I saw that on upgrade Python 3.8 is installed. >> >> Is there anything I have to take care of? Anything to do / change in venv? > The venv will still run whatever Python it was built with. That's what > virtualenvs are for - to isolate the software therein from external changes. > > You shouldn't need to do anything in the venv for Mailman to continue. > > -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 1 month

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Danil Smirnov

Yes, confirmed, and it seems that the page at https://mailman.server/accounts/password/reset/done/ is also missing styling due to this bug. On Tue, Nov 21, 2023 at 9:41 PM Jered Floyd <jered(a)convivian.com> wrote: > > I believe this is correct, and will need to be fixed on the Mailman side. > The practical effects seem to be -- for me at least -- that any of the > pages for social logins fail to receive any template styling. > > --Jered > > ----- On Nov 8, 2023, at 10:01 AM, Jeremy Stanley fungi(a)yuggoth.org wrote: > > > On 2023-11-07 19:46:01 -0800 (-0800), Mark Sapiro wrote: > > [...] > >> I don't think this is fatal, but I have reported it at > >> https://github.com/pennersr/django-allauth/issues/3513 > > > > We've been seeing the same thing in our deployment, I just hadn't > > found the time to look into it yet. Looks like upstream won't-fixed > > it, so I guess it was an intentionally backward-incompatible change > > and the template files will need some minor reworking? > > -- > > Jeremy Stanley > > > > _______________________________________________ > > 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 jered(a)convivian.com > _______________________________________________ > 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 danil(a)smirnov.la >

1 year, 7 months

[MM3-users] Re: Cannot show archives

by qiuhong su

Mark Sapiro wrote: > On 9/26/19 5:48 PM, Qiuhong.Su 蘇秋紅 wrote: > > Hi all, > > After I setup mailman3 and run mailman-suite, I can do: > > > > > > Register user > > > > Login > > > > Create new Domain > > > > Create new List > > > > Subscribe to the list > > When I try to send email to the list by run command: echo “test email” | mail –s “test > > email” test(a)example.com > > User test can receive this email, but I cannot find it on Archives, and other members > > cannot receive this email too. > > > > > > You say "User test can receive this email". Is test(a)example.com a user > or the list's posting address? > If you are saying that test(a)example.com should be the list's posting > address, but the mail is instead delivered to the user test(a)example.com, > you have not set up your MTA to properly deliver list mail to Mailman. > See https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html. After check MTA settings, still cannot resolve this issue. I create a new list "list1", and after subscribe it, send an email to list1(a)example.com And then check ./var/archives/hyperkitty/spool/, ./var/messages Both are empty. Click "Archives" it will access http://example.com/hyperkitty/, and show "No archived list yet." Could you help me? Here is my mailman.cfg: ------------------------------------------------------------------ [mta] verp_configurations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 lmtp_host: example.com lmtp_port: 8024 smtp_host: example.com smtp_port: 25 [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [archiver.prototype] enable: yes -------------------------------------------------------------------------------- My mailman-hyperkitty.cfg, example.com can be resolved to 10.0.0.120 -------------------------------------------------------------------------------- [general] base_url: http://10.0.0.120/hyperkitty api_key: SecretArchiverAPIKey -------------------------------------------------------------------------------- In mailman-suite settings.py, already add '10.0.0.120' to MAILMAN_ARCHIVER_FROM MAILMAN_ARCHIVER_FROM = ( '127.0.0.1', '::1', '10.0.0.120' )

5 years, 9 months

Search results for query "sapiro"