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

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Friday, November 3, 2017 12:26:06 PM EDT Mark Sapiro wrote: > The partucular "@daily mailman digests --send" would have to go in the > user crontab for the Mailman user. If this is not 'mailman' it is what > ever user "owns" Mailman. Further it would require that the path to > Mailman's bin/mailman command be in that users $PATH. There's nothing in http://docs.mailman3.org/en/latest/config-core.html or http://docs.mailman3.org/en/latest/prodsetup.html about adding a Mailman user. This should be a system user, right? Should it have a home directory? Could you add that to the documentation? Pierre -- I believe in Yellow when I'm in Sweden and in Black when I'm in Wales.

7 years, 6 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Thanks for the reply Mark, Στις 2019-09-21 16:19, Mark Sapiro έγραψε: > It's a stretch, but I suggest you examine the list membership and > remove > any invalid local addresses. There aren't any local addresses. > Also, look in the mail server's logs to see if you can see anything > about incoming connections being established and then dropped. Unfortunately no. Listening on all interfaces with tcpdump and there are no packets when mailman starts and the "Cannot connect to SMTP" log appears. It looks like there is no connection at all. Can I use a debugger to see exactly what happens in the runner?

5 years, 8 months

[MM3-users] Re: Problem migrating from Ubuntu packaged Mailman to Virtualenv, including Hyperkitty

by Tim Cutts

Thanks Mark. The migration seems to have done the trick for the archive - thanks for the pointer. Given that I have mailman-web running as www-data in Debian-style, I had to use: sudo -u www-data /opt/mailman/venv/bin/mailman-web migrate But that did the trick, and my archives have reappeared, so thank you. > On 7 Jul 2022, at 19:35, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/7/22 8:12 AM, tim(a)thecutts.org wrote: >> Hi everyone, >> As we all know, mailman3 got dropped from Ubuntu 22. So I updated the operating system anyway, and decided to switch to a virtualenv setup, keeping the old Debian/Ubuntu database and log locations etc. >> With some lumps and bumps, this has gone OK; the web interface appears to be working, and I can use the mailman CLI to manipulate the lists. So far so good. >> However, there do seem to be two problems, which might be linked: >> 1. If I send a message to my test list, it does not get sent on to any members. I can see the lmtp delivery to mailman. But nothing comes out again. I can see the two test messages in the “shunt” directory > > > Look in mailman.log. There will be exceptions and tracebacks associated with the shunted messages. What are these? Right, thanks for the pointer (there are so many separate log files, I’d been looking in the wrong one!) Jul 07 17:17:44 2022 (117110) SHUNTING: 1657210664.44771+e859f37833c541df3582ea334ab4b7b016557f77 Jul 07 17:23:39 2022 (117110) Uncaught runner exception: no nameservers Jul 07 17:23:39 2022 (117110) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 176, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 269, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/chains.py", line 57, in process if link.rule.check(mlist, msg, msgdata): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 316, in check if maybe_mitigate(mlist, address): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 288, in maybe_mitigate answer = is_reject_or_quarantine( File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 177, in is_reject_or_quarantine resolver = dns.resolver.Resolver() File "/opt/mailman/venv/lib/python3.10/site-packages/dns/resolver.py", line 758, in __init__ self.read_resolv_conf(filename) File "/opt/mailman/venv/lib/python3.10/site-packages/dns/resolver.py", line 850, in read_resolv_conf raise NoResolverConfiguration('no nameservers') dns.resolver.NoResolverConfiguration: no nameservers Jul 07 17:23:39 2022 (117110) SHUNTING: 1657211019.9355967+2e5a440ca577e112e092e03072660a4314f012eb Purging the resolvconf package and configuring resolv.conf manually fixed that little issue. Thanks again for the help Tim > >> Are these issues likely to be related, or do I have two things going on here? > > > The shunted messages are not related to the Django migration issues. > > -- > 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/

2 years, 10 months

[MM3-users] Re: mailman-web: ResponseNotReady

by Dmitry Makovey

On 10/18/2017 12:28 PM, Mark Sapiro wrote: > On 10/18/2017 09:00 AM, Dmitry Makovey wrote: >> >> It seems like mailman-core is still operating properly, but for some >> reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? > > > I'm not very well versed in the docker images, but I think mailman-web > uses uWsgi and sending the uwsgi process a SIGHUP should do it. I think I didn't express myself clearly - I want to reset any saved state for mailman-web - not just in-memory stuff. I've restarted my setup several times with mailman-web having exact same problem every time. -- Sr System and DevOps Engineer SoM IRT

7 years, 7 months

[MM3-users] Re: Templates location on the file system

by Odhiambo Washington

On Mon, Feb 13, 2023 at 11:06 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/13/23 08:06, Odhiambo Washington wrote: > > I am reading this: > > https://gitlab.com/mailman/mailman/-/issues/901#note_578684415 > > > > However, I cannot make heads or tails on what is meant by <LC>. > > > Language code. E.g. en for English. See > http://www.lingoes.net/en/translator/langcode.htm for a long list and > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > for those supported by Mailman core. > Thanks for this. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 months

[MM3-users] Re: mm3 installation question

by Stephen J. Turnbull

Mark Sapiro writes: > On 3/6/24 12:56 PM, Odhiambo Washington wrote: > > > Is it possible that an Apache directive like below will fix everything > > (albeit discreetly with sysadmins driving blindly)? > > > > ProxyPass "/" "http://127.0.0.1:8000/" > > That only works if Apache serves only Django and no other URLs. It's reasonable for a few other paths under root, as well. For example, if you have Shibboleth provide SSO capability, it needs access to some path like /Shibboleth/shibboleth_is_here. Then you can place something like ProxyPass "/Shibboleth" "!" # check Apache dox before the ProxyPass "!", which disables the ProxyPass for paths starting with "/Shibboleth". Not scalable or dynamic, obviously.

1 year, 2 months

[MM3-users] Re: LTMP to Postfix problem

by Mark Dadgar

On Jun 18, 2020, at 10:23 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > The grizz.org domain was recently migrated from from a larger server in > a colo that supported multiple domains to a DigitalOcean droplet which > initially had only 4 GB RAM, but that seemed marginally enough at best, > so I upgraded it to 8 GB. My 4GB DO droplet runs a couple of mm3 lists, including one that does ~4000 posts/month times ~400 recipients, running postgres, with no signs of the OOM killer. In fact, the only time I’ve ever seen it is when I was using the mailman3 shell to search for bad characters in the archives the other day. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 11 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > 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. > <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` The embarqmail.com domain publishes p=reject. This doesn't affect mail going *to* that domain, but it suggests they're aggressive about "fighting spam". It might help if the mailing list host were to participate in the ARC protocol. Steve

2 years, 8 months

[MM3-users] Re: Can't remove footer(s)

by Henrik Rasmussen

Mark Sapiro wrote: > The templates named list_member_digest_footer.txt and > list_member_regular_footer.txt (with underscores) were created by > import21 and set as the URIs for those templates. Had you just copied > /dev/null (or otherwise made empty) those files and done nothing else, > that would have done what you wanted, but since you deleted the template > URIs for the list, the template names are now the default How do I make these not default? > list:member:digest:footer.txt and list:member:regular:footer.txt names > (with colons) and those are the empty files you need to create. Or when I upgrade to V3.2.2 will I be able to just empty the templates in /postorius/lists/LISTNAME/templates? Henrik

6 years, 7 months

[MM3-users] Re: General question mailman3: message sender acceptance "always"

by Wikinaut

Mark Sapiro wrote: > On 10/23/23 05:41, Wikinaut wrote: > > I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). > > In the Postorius held messages view, click on the message's subject to > open a dialog showing the messages content Dear Mark, sorry: How should I know this? I'd rather prefer to have these both changes: i) relabel the existing one od three buttons from "accept" to "accept once" ; and ii) add a fourth button "accept all messages from this sender (i.e. add to white list)"

1 year, 7 months

Search results for query "sapiro"