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

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Mark Sapiro

On 2/6/26 08:14, Ibiam Chihurumnaya via Mailman-users wrote: > Mark Sapiro wrote: >>> The lmtp_port setting determines what port mailman listens on and what >> port is in the lmtp: entries in postfix_lmtp. Id should absolutely NOT >> be the same port dovecot listens on and the default 8024 is a good value. > > Yes, I commented the setting out and it now defaults to 8024. I'm not sure what all you did, but you may need to run mailman aliases to regenerate the var/data/postfix* files, specifically postfix_lmtp. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Setting configuration variables on all lists from command line

by Mark Sapiro

On 10/26/2017 11:20 AM, Mark Sapiro wrote: > > $ bin/mailman shell > Welcome to the GNU Mailman shell > >>>> from zope.component import getUtility >>>> from mailman.interfaces.listmanager import IListManager Actually, at least in the latest Mailman shell, the above two lines are not deeded as getUtility and the various interfaces are all in the initial namespace. This should be enough >>> listmanager = getUtility(IListManager) >>> for mlist in listmanager.mailing_lists: ... print(mlist.list_name) ... mlist.send_welcome_message = False ... mlist.send_goodbye_message = False ... commit() ... >>> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: Which crontab?

by Mark Sapiro

On 11/05/2017 03:43 AM, Pierre Abbat wrote: > On Friday, November 3, 2017 2:27:03 PM EST Mark Sapiro wrote: >> How about "user that installed Mailman" or "user that Mailman's runners >> run as"? > > I installed it as root. When you run mailman info it will report among other things the location of 'config file:'. The user who owns this file is the user that should run the mailman digests --send command. I.e., it should be in that user's crontab or in something like '/etc/cron.d/mailman' with that user specified. Also see <https://gitlab.com/mailman/mailman/issues/436>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: Cannot see the cron jobs for Mailman 3 Installed

by Mark Sapiro

On 1/23/20 11:29 PM, Shashikanth Komandoor wrote: > Thank you Mark Sapiro. > > As per your suggestion, I have gone through the mentioned URLs and > understood that the command "mailman notify" is responsible to send the > periodic notifications to the owners of the list which of course should be > as part of the cron job list (but it is not in my case). > > FYI, I am using mailman 3.2.3. There was no `mailman notify` command, and thus no way to get these periodic notifications, prior to Mailman 3.3.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

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

by Mark Sapiro

On October 24, 2023 3:47:10 PM PDT, Thomas Ward via Mailman-users <mailman-users(a)mailman3.org> wrote: >On 10/24/23 18:29, Mark Sapiro wrote: >> >> What if you try this with `mailman-web shell`? >> >Doesn't error on load, but can't access configs in order to see if my custom handler is present. Which Abhilash said has to be done in the mailman shell - as does the documentation. Mailman can't even start with this added. Which is a problem. I was confused. I should have said ` mailman shell`, not `mailman-web shell`. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

2 years, 9 months

[MM3-users] Re: Header Filter madness

by Mark Sapiro

On 1/12/21 9:57 PM, Mark Sapiro wrote: > On 1/11/21 6:14 PM, Brian Carpenter wrote: >> >> On 1/11/21 8:48 PM, Mark Sapiro wrote: >>> On January 11, 2021 5:50:04 PM MST, Brian Carpenter >>> <brian_carpenter(a)emwd.com> wrote: >>>> I have a client whose header filters seemed to have stop working. No >>>> matter what I try, it seems none of their header filters are being >>>> applied. Other lists on the same server that use header filters, are >>>> working fine. This particular header is the subject header. I can >>>> duplicate their problem but only with their list. If I create the exact >>>> same header on a test list using the exact same subject line, the >>>> header >>>> filter does its job (moderate). Just not with this one list. > > > What's in the X-Mailman-Rule-* headers of the post that should be but > isn't held? > > Are there other header filter rules besides the one that doesn't work? Also, on your test list, did you copy/paste the regexp or retype it. If the latter, there is possibly trailing whitespace that breaks it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/22/19 8:05 AM, Ralph Seichter wrote: > * Mark Sapiro: > >> If you post an issue at <https://gitlab.com/mailman/mailman/issues>, >> one of our GSOC aspirants may pick it up. > > Done, although I wonder if any GSOC participant would want to write > documentation instead of code... ;-) As part of the application process they need to contribute at least one non-trivial Merge Request and have that accepted. This may qualify. In any case, the need is now documented in a more visible way than just a post on this list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: localhost[::1] said: 550 Requested action not, taken: mailbox unavailable

by Mark Sapiro

On 10/27/2017 07:32 AM, Mark Sapiro wrote: > On 10/26/2017 11:30 PM, Bjoern Franke wrote: >> >> Oct 27 08:24:58 srv20 postfix/lmtp[2981]: 8798E40979: >> to=<admin(a)lists.ffnw.de>, relay=localhost[127.0.0.1]:8024, delay=0.51, >> delays=0.43/0.02/0.02/0.03, dsn=5.0.0, status=bounced (host >> localhost[127.0.0.1] said: 550 Requested action not taken: mailbox >> unavailable (in reply to end of DATA command)) > > > This may be a Mailman bug. I'll look further when I have time. This is definitely a bug. See the issue I just created at <https://gitlab.com/mailman/mailman/issues/433> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

Putting back on the list. On 10/23/21 1:37 PM, David Bremner wrote: > Mark Sapiro <mark(a)msapiro.net> writes: >> >> If you send me the complete bounce message off list, I can see if it >> should be added to the recognition at >> https://gitlab.com/warsaw/flufl.bounce/. > > Please find attached. Thank you. I tested that DSN with current flufl.bounce and it is recognized as a temp failure for the reported address and that in turn should just be ignored by Mailman's bounce runner and not reported as unrecognized. What version of Mailman core is this and what version of flufl.bounce? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: statistics monitoring for Mailman3

by Mark Sapiro

On 3/15/21 2:38 PM, Mark Sapiro wrote: > On 3/15/21 2:01 PM, Mark Sapiro wrote: >> >> This has nothing to do with outlook.com per se. It only has to do with >> the length of the log message. Further, I do not think there are >> actually newlines in these log messages. I think that is just an >> artifact of how you are viewing the log. > > > Actually, I'm wrong again. It does have to do with outlook.com. It is > because the Message-ID: header in the original message is folded as in > > Message-ID: <crlf> > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> Sorry for the premature send. I'm having a bad time with this thread. :-( I meant to say It does have to do with outlook.com. It is because the Message-ID: header in the original message is folded as in > Message-ID: <crlf> > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> and the added <crlf><space> actually gets included in the log message. Anyway I have updated the script at <https://www.msapiro.net/scripts/smtp_report>. My update is much simpler than the one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, but I have tested it, and it works. -- 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

Search results for query "sapiro"