Re: [Mailman-Users] Best way to slow down all the spam to my lists?

On 12/13/19 9:02 PM, Mark Sapiro wrote: As postgrey learns, it will remember triplets (sender, sending IP, recipient) and not delay them and in addition will whitelist domains that retry successfully more than a few times. The bigger senders are doing things now (more than ever) that they

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

"Stephen J. Turnbull" writes: > Chromatest J. Pantsmaker writes: > > > I had sent some test email from gmail and several hours later those > > test messages didn't pass. Maybe I goofed something along the way. > > If the GMail address used to send is the same as the address > subscribed to

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

Chromatest J. Pantsmaker writes: > I had sent some test email from gmail and several hours later those > test messages didn't pass. Maybe I goofed something along the way. If the GMail address used to send is the same as the address subscribed to the test list, you won't see it because GMail

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

I had sent some test email from gmail and several hours later those test messages didn't pass. Maybe I goofed something along the way. On Fri, Dec 13, 2019 at 9:04 PM Mark Sapiro wrote: > On 12/13/19 7:23 PM, Chromatest J. Pantsmaker wrote: > > I think I'll look into this next. It seems that

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

On 12/13/19 7:23 PM, Chromatest J. Pantsmaker wrote: > I think I'll look into this next. It seems that the postgrey > implementation that I followed from a previous email has stopped the spam, > but it's also stopped all other mail also! doh! If postgrey is working as it should, it will

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

I think I'll look into this next. It seems that the postgrey implementation that I followed from a previous email has stopped the spam, but it's also stopped all other mail also! doh! On Fri, Dec 13, 2019 at 6:40 PM Gary R. Schmidt wrote: > On 12/12/19 12:46 PM, Chromatest J. Pantsmaker

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

On 12/12/19 12:46 PM, Chromatest J. Pantsmaker wrote: > I'm the system admin (though I'm not great at it). I have a problem with > spam. Hundreds of spam messages are posted to my lists each week. They're > non-subscribers so they don't go to the lists, but they *do* go to me, the > list

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

On Fri, Dec 13, 2019 at 11:16 AM Chromatest J. Pantsmaker < chromat...@chromatest.net> wrote: > I'm the system admin (though I'm not great at it). I have a problem with > spam. Hundreds of spam messages are posted to my lists each week. They're > non-subscribers so they don't go to the lists,

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

Yeah, I wanted to avoid that because non-subscribers often email the list trying to contact the list admins or organization representatives instead. I've tried the first link above up through step 4. Step 5 is adding an additional filter to Spam Assassin and doesn't appear to be directly

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

On 12/13/2019 10:17 AM, Richard Damon wrote: To discard so you don't get the messages (don't set it to reject or you will be backscattering). It does say that you won't see messages that should go to the list but the send used the wrong account. That's another good/final option, drop

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

On 12/12/19 12:46 PM, Chromatest J. Pantsmaker wrote: > I'm the system admin (though I'm not great at it). I have a problem with > spam. Hundreds of spam messages are posted to my lists each week. They're > non-subscribers so they don't go to the lists, but they *do* go to me, the > list owner

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

Thanks for the responses Carl and Bruce, I've been getting about 20 per day. Some days more. The noise is way higher than the signal level here. It's a low-used email list. I'll try out filtering at the MTA level and see how it goes. On Fri, Dec 13, 2019 at 10:34 AM Carl Zwanzig wrote: >

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

On 12/12/2019 9:46 AM, Chromatest J. Pantsmaker wrote: I'm the system admin (though I'm not great at it). I have a problem with spam. Hundreds of spam messages are posted to my lists each week. (What's a acceptable level? I wouldn't spend many hours just to eliminate 3 spams a day.) Is

Re: [Mailman-Users] Delete list while leaving archives available?

On 12/12/19 11:21 AM, Kevin Bowen wrote: > Hello, > Is there any way to delete a list (mailman 2.1.9) but leave its archives > available? I know that rmlist by default doesn't delete list archives, but > with the list no longer in existence, they're no longer viewable via the > web interface. Is

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

Allan Hansen writes: > [ABH] The “From:” should contain the author address, but if we want to > keep our Yahoo/AOL subscribers… Exactly. This is what we economists call the Theorem of the Second Best: When it's already broken, sometimes the best you can do is to break it harder. > [ABH]

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

On Dec 10, 2019, at 10:27 , Stephen J. Turnbull wrote: > > Allan Hansen writes: > >> But Apple Mail puts the mangled address To: into the ‘Previous >> Recipients’ list to help with auto-completion later. > > I assume by "To" you mean "From”. [ABH] Yes, sorry. It takes the “From:” address

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

Allan Hansen writes: > But Apple Mail puts the mangled address To: into the ‘Previous > Recipients’ list to help with auto-completion later. I assume by "To" you mean "From". We don't munge "To" in this situation (there is a personalized list configuration where To is changed from the list to

Re: [Mailman-Users] Apache ScriptAlias and POST

Mark, Thanks very much for your pointer, the addition of a DEFAULT_URL_PATTERN as per the article you linked to solved my problem immediately. Regards, Geoff On Mon, 9 Dec 2019 at 21:25, Geoff Campbell wrote: > > Mark, > > > It is due to redirection losing POST data, but the culprit is

Re: [Mailman-Users] Apache ScriptAlias and POST

Mark, > It is due to redirection losing POST data, but the culprit is not > ScriptAlias. It is whatever you have in your Apache config that > redirects http to https. Ah, interesting. > I don't know why you couldn't find the answer in the archives. Well, I think the answer there is that there

Re: [Mailman-Users] Apache ScriptAlias and POST

On 12/9/19 3:42 AM, Geoff Campbell wrote: > > Reading through this list, I see that this is apparently due to the > ScriptAlias redirection just silently dumping the data content of HTTP > POST requests. Which seems a bit odd to me, but what do I know? It is due to redirection losing POST

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

This is exactly the problem I mentioned a few weeks earlier that did not elicit much of a response. I asked for some way to change the "via" string and there wasn't one. I have to remind people periodically to remove any "via" entries from their address books. AOL/Yahoo/Verizon cause other

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

Hi Stephen, Thank you a bunch for looking into this. I was trying to say that ReplyTo: works fine, for just the reasons you mention. No problem there. At first. ;-) But Apple Mail puts the mangled address To: into the ‘Previous Recipients’ list to help with auto-completion later. Here are the

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

Mark Sapiro writes: > Actually, that's still not quite correct. Ours looks like > > "xxx via list" Thank you for the correction. I wonder whether users would behave differently if we used "list on behalf of xxx" instead of "xxx via list"? > I suspect this latter is due to what Allan

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

On 12/8/19 8:17 PM, Stephen J. Turnbull wrote: > > That's not our mangling, it's your client's. Ours would look like > this: > > "Allan Hansen (han...@rc.org) via list" Actually, that's still not quite correct. Ours looks like "xxx via list" where xxx is if original From contains a

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

Allan Hansen writes: > I have set the ReplyTo: as the author, it’s not the immediate > replying as such that is an issue, and the mangled string is > factually correct. The issue comes when Apple Mail does > auto-completion and hides the email address. > > A mangled From: address like

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

Stephen et al., You’re right that using links instead of a Reply function is unattractive and not how email is supposed to work. On the other hand, the same surely goes for the To: mangling: I have set the ReplyTo: as the author, it’s not the immediate replying as such that is an issue, and

Re: [Mailman-Users] Avoiding mangling in Mailman 3?

Hi Allan, I have successfully installed Mailman 3 on 4 servers now. Please contact me off list if you are interested in my installation service. Thanks, Brian Carpenter > On Dec 7, 2019, at 12:17 AM, Allan Hansen wrote: > > All, > > One of my main gripes is the From: mangling that we had

Re: [Mailman-Users] Achiving not working, no .mbox file is being created

On 12/5/19 1:25 PM, Bruce Johnson wrote: > > Thanks, that was it, it was set to -1. If I set it to anything else this only > affects lists that have archiving turned on? Correct. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense

Re: [Mailman-Users] Achiving not working, no .mbox file is being created

On Dec 5, 2019, at 2:04 PM, Mark Sapiro mailto:m...@msapiro.net>> wrote: On 12/5/19 10:03 AM, Bruce Johnson wrote: I’ve reproduced the issue for a test list; the archive directories are created, but no .mbox file is being created when messages are sent. I’ve run check-perm -f to fix any

Re: [Mailman-Users] Achiving not working, no .mbox file is being created

On 12/5/19 10:03 AM, Bruce Johnson wrote: > > I’ve reproduced the issue for a test list; the archive directories are > created, but no .mbox file is being created when messages are sent. > > I’ve run check-perm -f to fix any permissions issues, but that did not fix it. > > we’re sending email

Re: [Mailman-Users] Check message size before moderation status?

On 12/5/19 8:57 AM, David Gibbs via Mailman-Users wrote: > Folks: > > I want to adjust my MM install so that it will check the message size > before a subscribers moderation status. > > Would this be the appropriate change to mm_cfg.py? > > GLOBAL_PIPELINE.remove('Moderate') >

Re: [Mailman-Users] Installing Mailman on a Debian system with Apache 2.4.2, CGI error!

On 05/06/2018 08:37 PM, Jayson Smith wrote: It seems that by default, Debian's Apache install doesn't enable the CGI module. Somehow, it sort of works better if you enable CGI. It works better if you plug it in. Head…desk. I'd spent hours trying to troubleshoot this! Sometimes the most obvious

Re: [Mailman-Users] removing s/mime parts before distributing mail to list-members required?

On 12/2/19 12:44 AM, Stefan Bauer via Mailman-Users wrote: > > More and more mails contain s/mime signatures. How to deal with that? We do > not want to send out "broken" mails. What is best practice? This reply is signed. I don't think the sig will be broken. > Removing the s/mime part seems

Re: [Mailman-Users] Mailman 3 Ready?

Hi all, Thank you for your responses, Stephen. Much appreciated. I have forwarded them to my friend. I don’t know if he is on this list, but I have recommended that he be, so we can get over whatever hump is getting in the way. I used the instructions on the Mailman 3 site on my own attempt.

Re: [Mailman-Users] Mailman 3 Ready?

At Mon, 25 Nov 2019 13:47:16 -0500 Jim Popovitch wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, 2019-11-25 at 11:06 -0500, Jim Popovitch via Mailman-Users > wrote: > > On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote: > > > Am Mo., 25. Nov. 2019 um 16:47 Uhr

Re: [Mailman-Users] Mailman 3 Ready?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-11-25 at 11:06 -0500, Jim Popovitch via Mailman-Users wrote: > On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote: > > Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users > > : > > > On Mon, 2019-11-25 at

Re: [Mailman-Users] Mailman 3 Ready?

On 11/25/19 7:17 AM, Matthew Pounsett wrote: > On Mon, 25 Nov 2019 at 05:04, Johannes Rohr wrote: > >> The obvious big showstopper is that there is no supported upgrade path >> from Mailman 2.* yet, according to >> >>

Re: [Mailman-Users] Mailman 3 Ready?

On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote: > > Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users > : > > On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote: > > > Is there a timeline for that? Mailman 2.x requires python 2.x, which is > > > EOL in

Re: [Mailman-Users] Mailman 3 Ready?

Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users < mailman-users@python.org>: > On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote: > > Is there a timeline for that? Mailman 2.x requires python 2.x, which is > > EOL in about 40 days. > > I keep saying this a

Re: [Mailman-Users] Mailman 3 Ready?

On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote: > Is there a timeline for that? Mailman 2.x requires python 2.x, which is > EOL in about 40 days. I keep saying this a lot... the EOL you are referring to is Python's declared date that the Python team will no longer maintain Python2.

Re: [Mailman-Users] Mailman 3 Ready?

On Mon, 25 Nov 2019 at 05:04, Johannes Rohr wrote: > The obvious big showstopper is that there is no supported upgrade path > from Mailman 2.* yet, according to > > http://www.mailman3.org/en/latest/pre-installation-guide.html#how-can-i-upgrade-from-mailman-2-1-x > and so you certainly don't

Re: [Mailman-Users] Mailman 3 Ready?

Am 25.11.19 um 07:15 schrieb Stephen J. Turnbull: [...] > The obvious "turn-key" installation is to use the Docker containers, > which Abhilash keeps fairly up-to-date. But see comment below about > universal working solutions. [...] Great suggestion. Is it easy to integrate it with the

Re: [Mailman-Users] Edit automated responses

On 11/23/19 8:45 AM, Christian F Buser via Mailman-Users wrote: > > In what cases will the "User notice of held post" be used by the system > (or, asked differently: in what cases will messages be held)? > > I believe this is only if a non-member wants to send something or when > the message is

Re: [Mailman-Users] Edit automated responses

Thank you, Mark Sapiro and Brian Carpenter, for the responses. In what cases will the "User notice of held post" be used by the system (or, asked differently: in what cases will messages be held)? I believe this is only if a non-member wants to send something or when the message is too big.

Re: [Mailman-Users] Edit automated responses

On 11/22/19 3:55 AM, Christian F Buser via Mailman-Users wrote: > > When a user sends a message which exceeds the limit, he receives a message > that his contribution will either need approval of a moderator or be deleted. > > Can this message be edited so that the user is informed that his

Re: [Mailman-Users] Edit automated responses

On 11/22/19 6:55 AM, Christian F Buser via Mailman-Users wrote: Hi all I have a list which uses Mailman 2.1.27 running on cPanel 78.0.44. The list has a size limit for the contributions (max_message_size). When a user sends a message which exceeds the limit, he receives a message that his

Re: [Mailman-Users] Massive amounts of bounces after setting munge_from for dmarc compliance

Mark Sapiro writes: > > I also found this post where this guy says you need to remove the > > DKIM headers: > > https://blog.dogan.ch/2016/11/24/making-mailman-dmarc-compatible/ > It says that, but gives no reason or rationale for doing so. I know several mail admins (small-scale, not any of

Re: [Mailman-Users] Massive amounts of bounces after setting munge_from for dmarc compliance

On 11/19/19 8:39 AM, Andy Cravens wrote: > Mailman 2.1.26. I modified all our lists that did not have munge_from set > for DMARC compliance. I ran a few tests and was able to send and receive > email from my test list. Now I’m getting reports that large numbers of > emails are bouncing and

Re: [Mailman-Users] Massive amounts of bounces after setting munge_from for dmarc compliance

Hi, On 2019/11/20 2:27, Andy Cravens wrote: I meant to say our default setting for all lists is to set from_is_list to munge_from. I also realized that some list managers (who’s domain uses DKIM) have added footers to their mailing list so I’ll have to strip the DKIM headers no matter

Re: [Mailman-Users] Massive amounts of bounces after setting munge_from for dmarc compliance

On 11/19/19 9:27 AM, Andy Cravens wrote: > > I meant to say our default setting for all lists is to set from_is_list to > munge_from. I also realized that some list managers (who’s domain uses DKIM) > have added footers to their mailing list so I’ll have to strip the DKIM > headers no matter

Re: [Mailman-Users] Massive amounts of bounces after setting munge_from for dmarc compliance

On Nov 19, 2019, at 9:39 AM, Andy Cravens wrote: Mailman 2.1.26. I modified all our lists that did not have munge_from set for DMARC compliance. I ran a few tests and was able to send and receive email from my test list. Now I’m getting reports that large numbers of emails are bouncing

Re: [Mailman-Users] OutgoingRunner processes hanging

On 11/15/19 11:34 AM, Kevin Bowen wrote: >> If you don't remove the .bak file, it will be recovered and reprocessed > when the runner is restarted. In this case, any recipients that were > delivered previously will get duplicates. > > Question: say there's a transaction in progress delivering a

Re: [Mailman-Users] [EXTERNAL] Re: LDAP routing

On 11/15/19 11:12 AM, Zinski, Steve wrote: > We're actually migrating to Proofpoint (no more sendmail). Proofpoint will > use our LDAP server for routing mail, so I'm trying to determine the best way > to represent our mailman aliases in LDAP. I know nothing about Proofpoint and not much about

Re: [Mailman-Users] OutgoingRunner processes hanging

>If you don't remove the .bak file, it will be recovered and reprocessed when the runner is restarted. In this case, any recipients that were delivered previously will get duplicates. Question: say there's a transaction in progress delivering a mail with 10,000 recipients, and you have

Re: [Mailman-Users] [EXTERNAL] Re: LDAP routing

We're actually migrating to Proofpoint (no more sendmail). Proofpoint will use our LDAP server for routing mail, so I'm trying to determine the best way to represent our mailman aliases in LDAP. On 11/15/19, 2:03 PM, "Mailman-Users on behalf of Grant Taylor via Mailman-Users" wrote: On

Re: [Mailman-Users] LDAP routing

On 11/14/19 11:31 AM, Zinski, Steve wrote: We are migrating from sendmail (virtuser) mail routing to LDAP routing. Setting up routing for users is pretty straightforward using the inetLocalMailRecipient class and the mail/mailLocalAddress/mailRoutingAddress attributes. But I was wondering

Re: [Mailman-Users] Munge-from "From:" addresses and address auto-complete

On 11/14/19 3:36 PM, Dan Halbert wrote: > > Is there some configuration I can set up that can alter these "From:" > addresses to avoid putting the person's name first, but still including > it? Or is there some other way to ameliorate this problem? We could > choose something other than

Re: [Mailman-Users] OutgoingRunner processes hanging

On 11/14/19 5:51 PM, Kevin Bowen wrote: > >> If the process is still actually delivering to the outgoing MTA, but > slowly, this is an issue between Mailman and the MTA. > Sometimes the process appears to still be delivering, but VERY slowly, > other times it still has an open TCP connection but

Re: [Mailman-Users] OutgoingRunner processes hanging

>One thing you can do is set up a separate port in the MTA for delivery Unfortunately we nowadays use a hosted MTA solution, so I'm not in control of it. >If the process is still actually delivering to the outgoing MTA, but slowly, this is an issue between Mailman and the MTA. Sometimes the

Re: [Mailman-Users] OutgoingRunner processes hanging

On 11/14/19 4:05 PM, Kevin Bowen wrote: > Hello, > Occasionally my mailman instance (2.1.9) gets into a weird state where one > or more of its OutgoingRunner processes appears to hang (usually on a large > email with a large number of recipients), causing a backlog of all other > mail on that

Re: [Mailman-Users] Regexp matching failing for accept_these_nonmembers

On 11/8/19 12:01 PM, Gretchen M Beck wrote: > Hi Mark, > > > In "def process" > > dn, addr = parseaddr(msg.get('from')) > > syslog('debug','parseaddr - from is %s' % addr,) FYI, the above could be syslog('debug','parseaddr - from is %s', addr) i.e. syslog will do the

Re: [Mailman-Users] Regexp matching failing for accept_these_nonmembers

ere either. USE_ENVELOPE_SENDER is false (no). --Gretchen From: Mailman-Users on behalf of Mark Sapiro Sent: Friday, November 8, 2019 1:57 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] Regexp matching failing for accept_these_nonmembers On 11/8/

Re: [Mailman-Users] Regexp matching failing for accept_these_nonmembers

On 11/8/19 9:47 AM, Gretchen M Beck wrote: > > I'm on mailman 2.1.18-1, and this week I've received several complaints about > messages held for moderation. Specifically, users whose addresses are in the > "accept_these_nonmembers" list, or whose addresses match a regexp that is on > the list

Re: [Mailman-Users] Mailman 2.1.12 confirm.py works fine with http but does not work with https

On 11/5/19 8:02 AM, jimw...@attglobal.net wrote: > > To make my website more secure, my website is configured to only work > with https and not with http. > > Please let me know how I can use confirm.py with https. > > confirm.py works fine with http, but not with https. As I said in a prior

Re: [Mailman-Users] Mailman Python Apache CGI issue

On 11/3/19 11:08 AM, jimw...@attglobal.net wrote: > > Confirming the subscription using the email method works fine, but the > web page confirmation is having problems. > > For a user named "dot" joining the Skipper group, the URL is: > >

Re: [Mailman-Users] List DMARC compliance reconfiguration

On 11/4/19 7:42 AM, Andy Cravens wrote: > Using mailman 2.1.26. I’m auditing the lists on my server for DMARC > compliance I’ve found several list configs that do not have the DMARC action > set to “munge_from.” It appears I need to edit all those list and fix that > setting. I’ve also

Re: [Mailman-Users] Mailman with Interworx server administration

On 11/4/19 5:24 PM, Christian F Buser via Mailman-Users wrote: Hi all Our hosting provider writes that he wants to change from cPanel to Interworx. At present, we have our virtual server on cPanel version 78.0.41, which includes Mailman version 2.1.27. I found a comparison of the two

Re: [Mailman-Users] user unsubscribe

On 3 Nov 2019 at 8:10, Brian Carpenter wrote: > Did you check to see if notifications were enabled on your bounce > processing page? You can contact your hosting provider to have them look > into their mail logs to see why those email addresses are bouncing list > messages. Yup -- I have it set

Re: [Mailman-Users] user unsubscribe

On 11/3/19 7:08 AM, Richard Damon wrote: On 11/3/19 6:05 AM, Bernie Cosell wrote: On 2 Nov 2019 at 21:23, Mark Sapiro wrote: On 11/2/19 5:03 PM, Bernie Cosell wrote: ... Here's the message i got.. no reason why: Subject: NPL-Folk unsubscribe notification From:

Re: [Mailman-Users] user unsubscribe

On 11/3/19 3:05 AM, Bernie Cosell wrote: > > Nope. I have no access to that and I just got another "has been removed" > message this morning. Is there any way for a non-privileged mailman admin > to > figure out why? I didn't get any "bounce score incremented" messages for > either >

Re: [Mailman-Users] user unsubscribe

On 11/3/19 6:05 AM, Bernie Cosell wrote: > On 2 Nov 2019 at 21:23, Mark Sapiro wrote: > >> On 11/2/19 5:03 PM, Bernie Cosell wrote: >>> ... Here's the >>> message i got.. no reason why: >>> >>> Subject: NPL-Folk unsubscribe notification >>> From: mailman-boun...@lists.puzzlers.org >>> To:

Re: [Mailman-Users] user unsubscribe

On 2 Nov 2019 at 21:23, Mark Sapiro wrote: > On 11/2/19 5:03 PM, Bernie Cosell wrote: > > ... Here's the > > message i got.. no reason why: > > > > Subject: NPL-Folk unsubscribe notification > > From: mailman-boun...@lists.puzzlers.org > > To: npl-folk-ow...@lists.puzzlers.org > > Date: Mon,

Re: [Mailman-Users] Subscriber password override?

On Sat, 2019-11-02 at 17:10 -0700, Mark Sapiro wrote: > A site admin can find the users password via bin/dumpdb of the lists > config.pck or can find the password and change it via bin/withlist. This sounds promising. > Assuming you are not a site admin, you can ask her to forward the list >

Re: [Mailman-Users] Subscriber password override?

On 11/2/19 4:30 PM, Lindsay Haisley wrote: > I have signed a neighbor up to a mailing list I administer. She's > borderline computer literate and hates passwords, so I said I'd assign > her a simple password. It seems that Mailman 2 doesn't allow the list > administrator to assign passwords and I

Re: [Mailman-Users] user unsubscribe

On 11/2/19 4:46 PM, Bernie Cosell wrote: > i received a notification that one of the users on my list was unsubscribed. > I'm > surprise because the configuration for the list specified that unsubscribes > have to > be approved, and this wasn't. How could that happen? The list's

Re: [Mailman-Users] user unsubscribe

Hi, If the notification was sent at 9:00 AM server time, it probably means the subscriber was bouncing Email (changed their Email address and didn't update their list subscription, their mail server thinks your messages are spam, etc.) and didn't respond to multiple "Your mail is bouncing,

Re: [Mailman-Users] bug

On 10/27/19 9:24 PM, Stephen J. Turnbull wrote: > > It appears this process is running as www-data. Does > /var/lib/mailman/locks exist? Is it a directory? Is it readable and > writable as a directory by www-data or www-data's group? Is it on a > local disk, or some kind of network file

Re: [Mailman-Users] List first created

Thanks very much. Works perfectly. Regards SI Sent from Mail for Windows 10 From: Mark Sapiro Sent: Wednesday, October 23, 2019 3:50 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] List first created On 10/23/19 11:56 AM, Peter Fraser wrote: > Hi All > I was won

Re: [Mailman-Users] List first created

On 10/23/19 11:56 AM, Peter Fraser wrote: > Hi All > I was wondering, is there a way to tell when a mailing list was first > created? Both Mailman 2.1 and Mailman 3 lists have a created_at attribute. In Mailman 2.1 this is a floating point number of seconds since the epoch. There is a withlist

Re: [Mailman-Users] [ext] Re: mailman not functional

the 1800 mail queue disappeared so fast I didnt have time to see it go. Thanks all. regards Steven From: Mailman-Users on behalf of Ralf Hildebrandt Sent: Friday, 18 October 2019 8:42 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] [ext] Re: mailman

Re: [Mailman-Users] zero-length config.pck file

On 10/18/19 3:46 PM, David Newman wrote: > > I've restored the config.pck file from a backup and things seem to be OK > now. If there was a config.pck.tmp.hhh.ppp with (hhh is the host name and ppp is the PID of the process doing the updating) or a config.pck.last with appropriate size and time

Re: [Mailman-Users] [ext] Re: mailman not functional

On 10/18/2019 12:42 AM, Ralf Hildebrandt wrote: I am sort of suspecting postfix as /var/log/maillog is not being written to. That's bad. So try stopping and starting postfix (after stopping check with "ps auxwww|fgrep post" to see if there's anything left!!!) and have a look at

Re: [Mailman-Users] How to stop auto discarding when whitelisted and automatic discarding set to 0?

Yes, I get the auto discard message with the pdf attached. Thank you! via http://listhelper.nongnu.org/mailmanconf.html I found where generic_nonmember_action was and discovered that the email address was in the List of non-member addresses whose postings will be automatically discarded. Crikey.

Re: [Mailman-Users] [ext] Re: mailman not functional

* Steven Jones : > thanks > > I am sort of suspecting postfix as /var/log/maillog is not being written to. That's bad. So try stopping and starting postfix (after stopping check with "ps auxwww|fgrep post" to see if there's anything left!!!) and have a look at /var/log/maillog while doing this.

Re: [Mailman-Users] mailman not functional

On 17 Oct 2019, at 16:41, Steven Jones wrote: ssh takes a long time to login but there is no load to cause this. The first thing to suspect when logins take a long time with no tangible loading issues (i/o, memory, and CPU all good) is DNS. If your resolver is trying to query a

Re: [Mailman-Users] mailman not functional

On 10/17/19 3:59 PM, Steven Jones wrote: > thanks > > I am sort of suspecting postfix as /var/log/maillog is not being written to. > > meanwhile, > > /var/log/mailman/smtp has something odd. The time to send email varies > between 0.017 and 180 seconds plus, and its getting worse, > >

Re: [Mailman-Users] mailman not functional

Runner, slice: 1/1) [root@vuwunicomailmn1 mailman]# = and its now 11:50am Ok to assume the above in the qrunner log is normal? regards Steven From: Mailman-Users on behalf of Mark Sapiro Sent: Friday, 18 October 2019 10:29 AM To: mailman-users@python.org Subject: Re: [Mailman

Re: [Mailman-Users] mailman not functional

On 10/17/19 1:41 PM, Steven Jones wrote: > Hi, > > Yesterday we had a major network outage that lasted 2 hours+ This morning I > find that the mailman server has "stopped working" I have restarted mailman > and now the server but mailman is not processing any emails. The load in top > is

Re: [Mailman-Users] confirm_delay_cleared = yes vs. Mailman bounce management

On 10/17/19 2:48 AM, Ralf Hildebrandt wrote: > > This was due to my non-default setting: > > confirm_delay_cleared = yes > > After sending a "your message is delayed" notification, inform the > sender when the delay clears up. This can result in a sudden burst of > notifications at the

Re: [Mailman-Users] How to stop auto discarding when whitelisted and automatic discarding set to 0?

On 10/17/19 2:38 AM, Tom Corcoran wrote: > All my stuff is typically default and not set unless ye told me here. I > double-checked and no rules in there How do you know when a message is discarded? Do you get a message from Mailman with Subject: Auto-discard notification with the message

Re: [Mailman-Users] How to stop auto discarding when whitelisted and automatic discarding set to 0?

All my stuff is typically default and not set unless ye told me here. I double-checked and no rules in there On Wed, 16 Oct 2019 at 18:01, Mark Sapiro wrote: > On October 16, 2019 9:16:14 AM PDT, Tom Corcoran > wrote: > >thanks, Mark, > > > >Content-Type: multipart/mixed; > >

Re: [Mailman-Users] How to stop auto discarding when whitelisted and automatic discarding set to 0?

On October 16, 2019 9:16:14 AM PDT, Tom Corcoran wrote: >thanks, Mark, > >Content-Type: multipart/mixed; > boundary="=_NextPart_000_0029_01D583FA.47355D80" >Content-Type: text/plain; charset="us-ascii" >Content-Type: message/rfc822 >Content-Type: multipart/alternative; >

Re: [Mailman-Users] How to stop auto discarding when whitelisted and automatic discarding set to 0?

thanks, Mark, Content-Type: multipart/mixed; boundary="=_NextPart_000_0029_01D583FA.47355D80" Content-Type: text/plain; charset="us-ascii" Content-Type: message/rfc822 Content-Type: multipart/alternative; boundary="=_NextPart_001_002A_01D583FA.47355D80" Content-Type:

Re: [Mailman-Users] How to stop auto discarding when whitelisted and automatic discarding set to 0?

On 10/16/19 1:30 AM, Tom Corcoran wrote: > Thanks, Mark. > > Having sent my test email with pdf attached I thought all was fine, but an > email from a club with pdf was auto discarded this morning :-( > > My pass_mime_types is now: > > multipart > message/rfc822 > application/pgp-signature >

Re: [Mailman-Users] How to stop auto discarding when whitelisted and automatic discarding set to 0?

Thanks, Mark. Having sent my test email with pdf attached I thought all was fine, but an email from a club with pdf was auto discarded this morning :-( My pass_mime_types is now: multipart message/rfc822 application/pgp-signature text/plain text/html application/pdf Looking at the header of

Re: [Mailman-Users] Intendation of threads in archive too high

On 10/15/19 1:55 PM, Peter Wetz wrote: > > However, see that the thread in the archive of my list is indented at level > 3. The thread should be at the very left of the screen (where the bullet > points typically start), but this is not the case as can be seen on the > screenshot:

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

Tom Corcoran writes: > Wow! Thanks, Steve! > > My mention of pdf here, crossed over with my other post and > confused, sorry. Not a problem. I'm still a little worried about your settings, though. The question is, "Do you want to receive those PDFs?" If "application/pdf" is not in

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

On 10/14/19 3:43 AM, Tom Corcoran wrote: > > 1. I looked at "Scrub attachments of the regular delivery message? > (Details for scrub_nondigest)" which opens in a new window it's set to no > already!2. In content filtering, I turned it on and changed nothing else. If scrub_nondigest is No,

Re: [Mailman-Users] How to stop auto discarding when whitelisted and automatic discarding set to 0?

On 10/14/19 3:27 AM, Tom Corcoran wrote: > > The faq mentioned is unreadable for a non-expert. In order to solve this issue, you need to understand why the messages are being discarded. The FAQ at lists the various list settings that can cause this. I will try

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

Wow! Thanks, Steve! My mention of pdf here, crossed over with my other post and confused, sorry. With content_filtering turned on now hopefully no more attachments accumulate., collapse_alternatives convert_html_to_plaintext defaulted to Yes, so I turned them off. Done and tested :-)

<    1   2   3   4   5   6   7   8   9   10   >