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

[MM3-users] Re: Archive import fails: "IndexError: list index out of range"

by Mark Sapiro

On 1/4/24 9:42 PM, Stephen J. Turnbull wrote: > Dan Caballero writes: > > > I've got a message that keeps getting re-queued to the > > /hyperkitty/spool/ folder. > [...] > > "During handling of the above exception (expected atom at a start > > of dot-atom-text but found > > '[1db292f04b54496ab40544b0989a2122-JFBVALKQOJXWILKNK4YVA7CPNZSVMZLUPRCW2YLJNRKGK43UPRCXQ32TNV2HA===(a)microsoft.com]>')" > > This is arguably a HyperKitty bug. The email package is correctly > refusing to parse that as a Message-ID (it's been illegal syntax since > RFC 822 if I remember correctly), but something, presumably > HyperKitty, should catch the error and do something to sanitize it to > message-id syntax. On the other hand, I never heard of a message > trigger that exception before a couple months ago, so maybe it's the > responsibility of spam filters. This is <https://gitlab.com/mailman/mailman/-/issues/1065> fixed in Mailman 3.3.9 by <https://gitlab.com/mailman/mailman/-/merge_requests/1099>. > In a later post you say that message came back, but I suspect it isn't > the same message, but a new one likely from the same source. I agree. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Newbie Wants To Know About Multiple Lists

by Mark Sapiro

On 12/16/18 11:20 PM, Christopher Garwood wrote: > Howdy, > I am new to Mailman and there are so many things I would like to know. Before I try to find out how to install and configure the software, I need to know if, how and what is required for us to set up this software to deal with more than one email list. There's lots of documentation. Start here <http://docs.list.org/en/latest/>. > I am working with a plan to setup a CentOS VPS on which Mailman will be hosted. The objective is to host and administrate mailing list for the 3 entities that I am directly involved with. These lists must function completely unrelated to each other including the email addresses from which the emails & news letters are sent from. If this is possible can I be given information or a link to how it can be done and what is required? A single Mailman installation can support multiple lists, each with different membership, owners and moderators. For example, see <https://mail.python.org/mailman3/>. The lists can all be in the same domain or in different domains if the server supports multiple domains. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Using MySQL via unix socket

by Mark Sapiro

On 2/2/19 5:31 AM, Torge Riedel wrote: > > A call to > > mysql -umailman -p > > successfully uses the socket on the machine and logs in. Yet you haven't specified -S or --socket > I tried > > mysql+pymysql://mailman:mailmanpass@127.0.0.1/mailman3?charset=utf8&use_unicode=1&unix_socket=/var/run/mysqld/mysqld.sock > > > as the connection string but it says that mysql server is not available. > Which is the same if remove the "unix_socket" parameter. I have found > this parameter when searching the net, but I'm not sure if it is supported. I think it should be, but the actual connection is via the the sqlalchemy create_engine() function. It appears this should be passed to the pymysql Connection() function per <https://docs.sqlalchemy.org/en/rel_1_2/core/engines.html#custom-dbapi-args> What happens if in a Python 3 session, you do from pymysql import connect conn = connect('127.0.0.1', user='mailman', password='mailmanpass', database='mailman3', charset='utf8', use_unicode=1, unix_socket='/var/run/mysqld/mysqld.sock') As I understand it, that's what sqlalchemy should be doing with your database url. In my testing, the above works with or without the unix_socket= argument, so I suspect something else is wrong in your case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Mark Sapiro

On 4/23/20 2:48 AM, Gelpi Andrea wrote: > > I saw the change in the file. > > As I'm not a programmer How can I test your fix? > > My system was installed via Debian 10 stable repository. > > I upgrade with testing repository postorius, django and mailmanclinet > > Postorius V 1.3.2 > Django V. 2.2.12 > Django filters V 2.1.0 > Djanog mailman V 1.3.2 > mailmanclient V 3.3.0 I don't know where the Debian package puts things, but you have to find the location of postorius/views/list.py. Something like locate views/list.py should find it. Then you need to download <https://gitlab.com/mailman/postorius/-/merge_requests/500.diff> and edit it to remove the first 15 lines so the first remaining line is the diff --git a/src/postorius/views/list.py b/src/postorius/views/list.py line. Then make a backup copy of postorius/views/list.py and run the command patch postorius/views/list.py path/to/500.diff where postorius/views/list.py is actually the full path to postorius/views/list.py and 500.diff is the edited file you downloaded. Then restart uWSGI. If anything goes wrong, restore your backup copy of postorius/views/list.py and restart uWSGI. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Mark Sapiro

On 11/23/20 8:00 PM, Joel Lord wrote: > > I've done the same thing, but Yahoo is pretty good at sanitizing their > report to make it difficult to impossible to tell who actually needs to > get ejected. I added "Sent to %(user_name)s at %(user_address)s" to the > footer and while they'd generally get the user_address wiped out, the > user_name would generally survive. For this reason, Mailman 2.1 has this feature. > # If the following is set to a non-empty string, that string is the name of a > # header that will be added to personalized and VERPed deliveries with value > # equal to the base64 encoding of the recipient's email address. This is > # intended to enable identification of the recipient otherwise redacted from > # "spam report" feedback loop messages. For example, if > # RCPT_BASE64_HEADER_NAME = 'X-Mailman-R-Data' > # a header like > # X-Mailman-R-Data: dXNlckBleGFtcGxlLmNvbQo= > # will be added to messages sent to user@@example.com. > RCPT_BASE64_HEADER_NAME = '' This hasn't been implemented for Mailman 3 but could be if there's demand. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Failed first login

by Mark Sapiro

On 8/31/20 6:59 AM, Massimo Zappalà wrote: > Hi everyone, > i installed mailman3-full on debian 10. > During installation, it asks me to enter the admin user credentials. > After configuration, I restart mailman3 and mailman3-web. > When I try to log in for the first time by entering the admin credentials, a message warns me that the credentials are incorrect. > I looked at the mailman logs, but I find nothing. > It seems that it is a django authentication problem, because even in the django admin panel I can't log in. > Looking at the mailman3web db, in the auth_user table, I see the admin user. > How can I see why it does not accept the credentials? > Thank you in advance I have no idea what the Debian package is doing, but you can see the superuser(s) with the database query select * from auth_user where is_superuser; and you can change the user's password with the django admin changepassword command and/or create a superuser with the django admin createsuperuser command. Give the commands with a --help option for more info. Since you can see the user in the auth_user table, try the django admin changepassword command to change the password. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/6/22 6:28 PM, Stephen J. Turnbull wrote: > Michael Heseltine writes: > > > > Do you have all of these apache modules enabled, proxy.conf, > > > proxy_http.load and proxy.load, in particular proxy_http.load? > > > > Well, mostly: > > > > > # a2enmod proxy_http.load > > > Considering dependency proxy for proxy_http: > > > Module proxy already enabled > > > Module proxy_http already enabled > > > # a2enmod proxy.load > > > Module proxy already enabled > > > # a2enmod proxy.conf > > > ERROR: Module proxy.conf does not exist! > > In my Debian configuration that module is needed because it contains > the necessary directives to enable proxying. Actually though, I think that's enabled as part of proxy. > The bottom line, though, is that that error message has to do with the > internal configuration of Apache, and as far as I can see it has > nothing to do with Mailman itself. However, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I now suspect the real issue is there's no wsgi server listening on port 8000. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Help understanding why some users don't receive emails

by Mark Sapiro

On 9/21/22 14:06, Stephen Daniel wrote: > > Looking at one user in particular, I see in /var/log/syslog that postfix is > sending the email. There is nothing in bounce.log. And does the postfix log indicate the mail is accepted by the users MX? I.e. a log message with `status=sent`. > They are the only user who uses that particular email domain (embarqmail.com > ). > > Is there anything I can do to debug why they do not get the emails? Or is > this up to them and their email provider? Assuming the message is accepted by the user's MX, the user can check a spam/bulk/junk folder and if the messages aren't there, complain to their ISP about messages being silently discarded. Your log entries showing the message successfully delivered to the MX can provide evidence. Other than that, you need to ensure that your outgoing messages are DKIM signed, and that your outgoing MTA server has full circle DNS <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. It can also possibly help for the server's domain to publish a DMARC policy even if that is `p=none` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: List users from different domains getting blocked.

by Mark Sapiro

On 12/14/23 14:19, bob B via Mailman-users wrote: > I am running MM3 and have a list that has users from different organizations and email domains. > > So let's say I am orga.com and hosting mailman > Bill is borg.com > Cindy is mew.com > > When Bill sends a message to my MM3 list it gets sent out, However, cindy's email system rejects it cause it sees the message is sent from Bill(a)borg.com but it came from my MM3 server which is under orga.com, so it rejects it. You need to apply DMARC mitigations. Normally mitigations are only applied if the From: domain publishes DMARC p=reject or p=quarantine, but recently this has become problematic. For example, gmail.com pubpishes DMARC p=none yet google servers effectively apply p=reject to mail From: gmail.com. Mailman >= 3.3.9 and Postorius >= 1.3.9 allow setting dmarc_addresses to a list of email addresses and regexps matching addresses and domains to which DMARC mitigatations will be applied regardless of puublished policy. For older releases and for cases where domains are not known in advance one can always set dmarc_mitigate_unconditionally True to apply mitigations to all mail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/5/24 07:04, Odhiambo Washington via Mailman-users wrote: > I am having an ugly-looking https://mm3-lists.kictanet.or.ke/archives/ page > because of cached content: > > ``` > 2024/08/05 17:00:31 [error] 694#694: *9562 open() > "/opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No > such file or directory), client: 172.70.111.39, server: > mm3-lists.kictanet.or.ke, request: "GET > /static/CACHE/css/output.6dab123e4897.css HTTP/2.0", host: " > mm3-lists.kictanet.or.ke", referrer: " > https://mm3-lists.kictanet.or.ke/archives/" > 2024/08/05 17:00:31 [error] 694#694: *9564 open() ... > That IP address appearing there is not my actual IP, but Cloudflare's, > which is acting as proxy for the site. I **think** you may have something like location /static/ { alias /opt/mailman/web/static/; } in nginx on cloudflare, but since cloudflare is not the Mailman server, /opt/mailman/web/static/ doesn't exist there. I can't be sure on how to configure this without knowing the details of how requests get from cloudflare to mm3-lists.kictanet.or.ke and from there to the wsgi server. However, if cloudflare just proxies the request for /static/ to the Mailman server and nginx on that server has the above `location` directive, that may do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Search results for query "sapiro"