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

[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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 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.

2 years, 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

5 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

3 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

7 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)"

2 years, 7 months

[MM3-users] Re: OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?

by Bill Oliver

On Wed, 2024-10-16 at 12:19 -0700, Mark Sapiro wrote: > On 10/16/24 10:26, Bill Oliver wrote: > > > > > Does the forensicpath.us domain have an alias_domain configured in > mailman causing mailman to create > /opt/mailman/mm/var/data/postfix_vmap > and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. > Thanks for your reply. My wife has fallen ill, so I am taking a break from working on this to take care of her. I'll reply substantively in a week or so, I hope. billo

1 year, 7 months

[MM3-users] Rejection based on total message size including attachments

by leith＠khimaira.com

As a web hosting provider I have searched and searched for a way to limit the total size of messages posted to all lists. We have moderators who just can't get it through their heads to limit the size of attachments. One list today distributed a 6 mb pdf to over 700 recipients. I have found information on creating a custom handler and some old and brief logic on limiting max_message_size from Mr. Sapiro. Would anyone who has developed a custom handler to reject messages based on total size, mind sharing the full file? If so, could you also state where the handler was positioned in the chain of handlers. Thank you for your time.

7 years, 8 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-30 06:52, Mark Sapiro wrote: > On 11/30/22 05:32, Jan Eden via Mailman-users wrote: > > > > I tried setting permissions on /opt/mailman/fulltext_index to 777 > > temporarily, but the issue remained (as expected). > > Are you running some security manager (SELinux, apparmor, ???) > > I suspect that's the issue. apparmor is disabled, and the error is only triggered when the directory does not exist: > # Make sure the index is there. > if self.use_file_storage and not os.path.exists(self.path): > os.makedirs(self.path) > new_index = True /opt/mailman/fulltext_index exists (and is populated), so I must assume that the Whoosh backend uses some other (non-writeable) path at this point. - Jan

3 years, 5 months

[MM3-users] Re: Getting original message headers

by Peter Chubb

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 1/5/26 01:32, Peter Chubb via Mailman-users wrote: >> >> We've been seeing some particularly pernicious spammers >> recently. They're using gmail accounts; I'd like to report them to >> Google. Mark> Only minimal information from headers is in the hyperkitty Mark> archive, but the headers should be in the delivered email and in Mark> the message archived by the prototype archiver if enabled Mark> (Mailman's var/archives/prototype/<list_address>/new/) I think they must have been posting via hyperkitty. The first received: line is localhost then the mailman server. Is there a way to turn that ability off? Peter C

4 months, 3 weeks

Search results for query "sapiro"