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

[MM3-users] Re: Mysterious Bounces Being Logged

by Mark Sapiro

On 3/26/21 8:51 PM, Brian Carpenter wrote: > On 3/26/21 6:13 PM, Mark Sapiro wrote: >> Absolutely. At first MM3 wasn't processing bounces at all. A GSOC >> student did the bulk of the current implementation and we were happy >> to get that even though this piece was missing. We know we need it. If >> you don't think we're working fast enough, you can submit a merge >> request or dock our pay. > > I don't understand the sarcasm here at all. I am just trying to figure > out what the PRIORITIES are from the Mailman 3 developers. That's all. > BTW, I still haven't figured it out. OK, the "dock our pay" remark was uncalled for, but I was only trying to point out that for the most part, all of this work is being done by or in some cases mentored by Abhilash and me, and we are both volunteers with other responsibilities. This is a known issue <https://gitlab.com/mailman/mailman/-/issues/737> posted by me 8 months ago. There are no offers to help work on it, nor are there any comments to the effect that this should be higher priority than any of the 307 other open Mailman core issues in the tracker. I can't speak for Abhilash, but my priorities are fix things that are trivial to fix as they arise and work on the harder stuff as time and interest allow. I realize that doesn't help you much, but I'm a volunteer. This is (one of) my hobbies. If it's not fun or at least satisfying, I won't do it. > It still doesn't explain why Postfix is not recording the delivery > issues which I assume has nothing to do with Mailman 3. I see successful > deliveries with Postfix and bounces with Mailman 3 core. I never seen > that with Mailman 2 and Exim. They always matched. If you can help me to > understand that with out the petty sarcasms then that would be great. If > not, then ok. I don't know why you never saw this with MM 2.1 and Exim. Possibly because MM 2.1 sent you the DSN with the admin notification, you never looked. I told you in my initial reply in this thread "They are being bounced by a downstream MTA." To elaborate on that, Mailman's MTA be it Postfix, Exim or whatever, attempts to deliver the mail to the MX of the recipient domain. Sometimes this results in a 5xx status which is logged and reported as a bounce to the sender, i.e. the LIST-bounces address. Sometimes it results in a 4xx status which will cause the delivery to be retried at intervals until it is either accepted or exceeds a configured lifetime and is reported as a permanent failure. The rest of the time, the delivery succeeds, but that is only delivery to the MX for the domain. It may be that for that recipient, that MX is a relay to another MX in the delivery chain, and sometimes, either quickly or after some delay due to retries downstream eventually timing out, the ultimate delivery fails and a DSN is returned to the original envelope sender which is the LIST-bounces address. If you look in the Postfix logs around the time that Mailman recorded the bounce, you should see an incoming message from=<> (DSNs always have a null envelope sender) and to=<LIST-bounces(a)list.domain> or if you are VERPing to=<LIST-bounces+recip=recip.domain(a)list.domain> which is the DSN being returned by the downstream MTA. -- 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: Installing mailman 3

by Rafael Mora

Is this the problem?????: # When DEBUG is True, don't actually send emails to the SMTP server, just store # them in a directory. This way you won't accidentally spam your mailing-lists # while you're fiddling with the code. if DEBUG == True: EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') Shouldn't DEBUG be FALSE?? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 10 months

[MM3-users] Re: Mailman 3 Web Application Startup Time or Availability - 502 Bad Gateway and Postorius

by Mark Sapiro

On 5/3/21 3:27 PM, summersan(a)nclack.k12.or.us wrote: > Hi Mark, > > Thank you for your quick response! > > When setting up Mailman 3, I went through much of this "how to" guide here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10. Which uses gunicorn as the wsgi server for Django. > As far as I can tell, my current setup appears to be proxying from Nginx to Gunicorn, according to the related Nginx and mailman3-project-specific Gunicorn config files. Specifically, I checked the local address:port being used in the Nginx file and compared that to the mailman3-project-specific Gunicorn bind address. It looks like I might have "separated out" the REST API to a different server block in the Nginx config file, so I think I'm looking at the correct server block with this conclusion. Nginx has nothing to do with the REST API. The REST API is accessed by Postorius and HyperKitty via mailmanclient and django-mailmane which are installed by pip as dependencies of Postorius and Hyperkitty. > For what it's worth, I don't recall this type of "slow first visit startup" issue happening in the past when using web applications with uwsgi, and I've had the opportunity to use uwsgi with a variety of programs. I think Gunicorn is fairly new to me. I do, however, remember that something like this might have happened in the past when using Passenger (https://www.phusionpassenger.com/) a long time ago, but that might have been setting related on my part. > > Okay, thanks for the encouragement about the potential solution to periodically accessing the related "example.mailman.site/mailman3/lists/" type location (from my earlier email). Wanted to check on that and was also hoping that there might be some setting I'm missing in the overall Mailman 3 project setup related to the "slow first visit startup" issue. I'm not aware of anything you missed. I think this has to be a gunicorn issue or possibly related to Django, but I'm not specifically aware of any issues. There might be something you can set in gunicorn, but I don't know what. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Mark Sapiro

On 5/31/23 06:17, justfixit(a)marilynstrother.com wrote: > Very interestng! Upon restarting the system (down momentarily for taking a snapshot) and starting Mailman again, all of these missing [List] messages emerged from their timewarp and were delivered to the members / subscribers. Just before shutting down the system I discovered that the apache2 webserver had been off the air due to a module not being enabled yet. > As of yet, I was unaware of any requirement for a web server to be online (beyond possibly gunicorn) in order for Mailman to run its lists. Does that speculation have a factual basis? Or do I risk starting a vicious rumor amongst the impatient readers who are not still here once we deduce this pair of observations were merely correlated in time, with no cause-and-effect relationship? > Before this situation healed itself, the thought had crossed my mind to peek and see if anything was stuck in the queues: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > While that could have provided peace of mind that email messages were merely delayed instead of vanished, even in hindsight I do not see how that would have led to repairing the situation. I suspect if you had looked, you would have found the messages in Mailman's `pipeline` queue, and they were not being processed because the `pipeline` runner wasn't running, although it is possible that the issue was with the `in` runner/queue. It wasn't the `out` runner/queue if welcome messages were being delivered. The fact that the web server wasn't running is just a coincidence. It has nothing to do with Mailman core's processing of messages with the one exception that Mailman core needs to communicate with HyperKitty's API via mailman_hyperkitty, but this only affects archiving to HyperKitty and the addition of an Archived-At: header to messages. > In the absence of a hypothetical command: > mailman status --verbose > about which diagnostic tools or clues should I learn? Logs are possibly the most useful. You might find something in mailman.log about the death of whatever runner had died. Looking at queues is also useful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Phantom Email Address in Nonmember List

by Mark Sapiro

On 9/9/24 15:12, Steve Brown via Mailman-users wrote: > > Looking at the headers of emails sent from steve(a)stevebrown.us to the list and boomeranged back to me, I see a line “X-MailFrom: bounce+66273f.99dcd9c-radg=lists.radg.us(a)stevebrown.xn--us-02t. I gather that it is designating the return path where a message would be sent if there was a delivery problem. From its position in the header, I suspect it is added as they pass through Mailgun, maybe related to DKIM. Without seeing the full headers in sequence I can't say much, but some MTA in the delivery chain (likely your MX, mx1.tmdhosting.com) is setting the envelope sender of the message to bounce+66273f.99dcd9c-radg=lists.radg.us(a)stevebrown.us so that it can receive DSNs at that address. Mailman's lmtp runner is adding the X-MailFrom: header as information. Then Mailman's incoming runner ensures that all of the messages senders are known to mailman by creating, if necessary, address records for all of them. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/incomi…>. The senders are defined as addresses in the headers listed in the configuration setting `sender_headers`, default = from, from_ meaning envelope sender, reply-to and sender. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> > I am hoping you might know why that bounce address is recognized by Mailman 3 as a real address for my emails, but not for others, even from my wife’s computer traversing the same path from our home to the Mailman 3 server. The Mailman installation does get and process the post, but also puts the “bounce+,,,” address in its list of nonmembers. Mailmanlists.net hasn’t figured out the behavior. I can provide full header information if that would help. My understanding of how headers work is very limited. Are you saying that the `bounce+...` address ends up as a nonmember of the list you are sending to. I don't think that should happen. Mailman will add the `sender` address as a nonmember of the list if it is not a member, but the `sender` is the first non-empty value in `senders` which normally would be the From: address unless the installation has changed the `sender_headers` setting -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I did not run the createsuperuser command, have to do that. What about this: Don’t leave the console email backend configured and running once you get to the point where you want to send real emails, though! How do I change the setting to send the emails instead of printing them on the console???? On Fri, Jul 21, 2017, 21:16 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/21/2017 06:59 PM, Rafael Mora wrote: > > Is there a ´default´ admin account?? > > > It's the user you create with > > python manage.py createsuperuser > > See > < > http://docs.list.org/en/latest/devsetup.html#run-the-mailman-suite-combined… > >. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 11 months

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Mark Sapiro

On 2/26/26 13:20, Ibiam Chihurumnaya via Mailman-users wrote: > > I'm doing it in `mailman shell`, list_name is a List object, and it seems to have a `settings` > attribute as `list_name.settings` returns > > {'acceptable_aliases': [], ...} I would really like to know what Mailman version this is, and how it was installed? In my case with Mailman core from the head of the GitLab branch: ``` $ mailman shell -l list.example.com 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 list.example.com mailing list >>> m.settings Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'MailingList' object has no attribute 'settings' >>> m.settings['accept_these_nonmembers'] Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'MailingList' object has no attribute 'settings' >>> ``` Presumably in your case, you could do ``` list_name.settings['accept_these_nonmembers'].append('user(a)example.com') or list_name.settings['accept_these_nonmembers'].extend(['user1(a)example.com', 'user2(a)example.com', 'user3(a)example.com']) ``` but as I've said previously, `accept_these_nonmembers` is not the preferred way to do this. Something like ``` $ mailman addmembers --delivery disabled FILE LIST ``` where FILE contains the addresses to add, one per line and LIST is the list name would add the addresses as members with delivery disabled. To add them as nonmembers with moderation_action Defer: ``` $ mailman shell -l list.example.com 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 list.example.com mailing list >>> from mailman.app.membership import add_member >>> addresses = ('user1(a)example.com', 'user2(a)example.com', ... 'user3(a)example.com') >>> for addr in addresses: ... rr = RequestRecord(addr) ... nm = add_member(m, rr, role=MemberRole.nonmember) ... nm.moderation_action = Action.defer ... >>>commit() ``` Of course, all of this can be done, perhaps more easily, using the Postorius web UI. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

Thank you, Mike. I will see how to get this across to my users. :-) With love, Allan > On Feb 12, 2021, at 11:55 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/12/21 10:27 AM, Allan Hansen wrote: >> They need to resubscribe to each list they want the new address to be used for. >> Subscriptions involves permissions from the moderators. It’s not a >> simple process, especially if you are on many lists. > > > Not true if they have a Django account. See my reply at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. > > > -- > 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/

5 years, 4 months

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/9/25 11:19, dap1--- via Mailman-users wrote: > I created the superuser (used default, mailman). > > When I try to login I get a 403 error. No errors are in the apache2 log. What's in /opt/mailman/mm/var/logs/error.log? Do you get the 403 when going to the login page or when submitting the login form? is it a generic 403 error page or a styled page that says user or password is incorrect? Are you sure you are using the correct password. You can use mailman-web changepassword to be sure? > No, I am not logged in. I am an admin on mailman2 so I thought it would import credentials. But I am unable to log in as anyone (password problem). Mailman 3 is completely different from Mailman 2.1 in this respect. In mailman 2.1 an address listed as owner only meant that address was sent admin notices. Being able to manage a list meant knowing the list admin password whether or not you were listed as an owner, and similarly for moderator. In Mailman 3 the authentication is being logged in as a person who is a superuser or who has an address matching that of an owner or moderator. And the login's are managed by django-allauth. There are multiple reasons why import21 won't create those logins, not the least of which is that Mailman 2.1 authentication is per list and Mailman 3 authentication is per user. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/8-mil… and perhaps also https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/archi… > I see 3 options on the archive page, recent, active and popular. None of which show any threads. Since the list has been dormant for quite a while there are no 'recent' posts nor 'active' posts. I don't know what makes a thread 'popular'. I guess the only way to know what is going on at this point is to be able to login as superuser. 'favorites' are posts you've marked as a favorite and 'popular' are posts with some number of up votes. None of these will exist in an imported archive as those are HyperKitty things with no pipermail equivalent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

[MM3-users] Re: Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error'))

by Mark Sapiro

On 11/28/23 18:01, Mark Labeste wrote: > Hi Admin, Any idea on this error? It happen when you wrote a tread it send the mail but not save on the archive. > > Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8406) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Could not archive the message with id <168853565119.17959.11384406081068301715(a)email1.example.com> > Nov 28 20:34:51 2023 (8400) archiving failed, re-queuing (mailing-list testmaillist.example.com, message <168853565119.17959.11384406081068301715(a)email1.example.com>) > Nov 28 20:34:51 2023 (8400) Exception in the HyperKitty archiver: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 710, in urlopen > chunked=chunked, > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 386, in _make_request > self._validate_conn(conn) > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn > conn.connect() > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connection.py", line 429, in connect > tls_in_tls=tls_in_tls, > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 450, in ssl_wrap_socket > sock, context, tls_in_tls, server_hostname=server_hostname > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl > return ssl_context.wrap_socket(sock, server_hostname=server_hostname) > File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket > _context=self, _session=session) > File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ > self.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake > self._sslobj.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake > self._sslobj.do_handshake() > OSError: [Errno 0] Error mailman_hyperkitty is unable to connect to HYPERKITTY. Check your setting for base_url in mailman_hyperkitty.cfg. See <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#connec…> The messages that haven't been archived are queued in Mailman's var/archives/hyperkitty/spool/ directory and will be archived when you fix this issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Search results for query "sapiro"