<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>I say disable the addresses in postfix. It is an easily automated way to bring the server to it's knees and rack up bad vibes for ale and potentially fines from the hosting provider. If someone actually complains, we can add them manually or refer them to the web form. <br><br><br><br><div class="gmail_quote">On July 12, 2022 6:10:58 PM MST, Robert Tweedy <robert@robert-tweedy.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<font size="2"><font face="Arial">I feel like disabling the Mailman
"-request" and "-subscribe" addresses would have unintended side
effects, but it's technically a possibility; does anyone more
familiar with GNU Mailman know if this is: <br>
<br>
1. A bad idea/will severely break core Mailman functions </font></font><font size="2"><font face="Arial"><font size="2"><font face="Arial">(alternatively,
how many people will start sending in complaints that their
emails to <a class="moz-txt-link-rfc2396E" href="mailto:ale-request@ale.org">"ale-request@ale.org"</a> stopped working)?</font></font><br>
2. An option that's available through Mailman's configuration
files? Or would I need to modify the Postfix aliases to achieve
this?<br>
<br>
-Robert<br>
</font></font><br>
<div class="moz-cite-prefix">On 7/12/22 20:40, Derek Atkins wrote:<br>
</div>
<blockquote type="cite" cite="mid:dcd67ee292d82c34dfba7569e9bacd89.squirrel@mail2.ihtfp.org">
<pre class="moz-quote-pre" wrap="">Another option is to turn off handling of email-based subscription
requests and require going through the web interface?
-derek
On Tue, July 12, 2022 8:17 pm, Robert Tweedy via Ale wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I've gotten a basic Captcha configured now on Mailman's main sign-up
pages (which is likely where the issue's coming from), so this will
hopefully lessen the problem. I'm definitely open to any suggestions for
improvement as well as donations of time to implement a better
spam-filtering mechanism to prevent the server from responding to every
incoming message it receives (ie. Mailman either needs to be smarter
about what messages it replies to & what messages it just
ignores/discards without a reply, or we need our spam filter to also
work internally & keep Mailman from sending out spam on its own when
someone/something abuses forms on the site that could generate an email).
On 7/12/22 18:01, Jim Kinney via Ale wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Started getting these notices/complaints today and each one is a $5
charge from my hosting provider. We're up to $35 so far today.
I'm on work out of state and didn't travel with any personal gear and
Robert is also slammed. Can someone gently talk with the recipient and
ask if they can simply delete/block instead of complain.
We are open to ideas. That email is already blocked.
<snip>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Ale mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ale@ale.org">Ale@ale.org</a>
<a class="moz-txt-link-freetext" href="https://mail.ale.org/mailman/listinfo/ale">https://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<br>
</blockquote></div><br>-- <br>Computers amplify human error<br>Super computers are really cool</body></html>