<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>Can you set up postfix to capture ALL outbound mail sent to ukkoknowles@usfamily.net<br>and redirect to a local account or /dev/null. Got another 15 last night. But the new ones are all originating within 3 minutes of the first one so it may still just be fall out.<br><br>It looks like the first 5 complaints are for a single email. Identical time stamp, smtp id, and esmtp id. The next four are also identical but from an email sent about 40 seconds later. Each in this batch have the same ids.<br><br>The new batch has the same sending time stamp so far, 20220711224723 but different smtp and esmtp ids.<br><br><div class="gmail_quote">On July 12, 2022 7:55:47 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">Thanks Derek,<br>
<br>
I've made the changes & tested to confirm that the
ale-request & ale-subscribe addresses no longer work.<br>
<br>
-Robert<br>
</font></font><br>
<div class="moz-cite-prefix">On 7/12/22 22:08, Derek Atkins wrote:<br>
</div>
<blockquote type="cite" cite="mid:181f550b888.27f4.ee0929d4f8247208f860e07266211506@ihtfp.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div dir="auto">I know it won't break core functionality. </div>
<div dir="auto">You could send the - request email to a person. </div>
<div dir="auto">I think you need to deal with it in postfix. </div>
<div dir="auto"><br>
</div>
<div id="aqm-signature" dir="auto" style="color: black;">
<div dir="auto">-derek</div>
<div dir="auto">Sent using my mobile device. Please excuse any
typos.</div>
</div>
<div dir="auto"><br>
</div>
<div id="aqm-original" style="color: black;">
<!-- body start -->
<div class="aqm-original-body">
<div style="color: black;">
<p style="color: black; font-size: 10pt; font-family:
sans-serif; margin: 8pt 0;">On July 12, 2022 9:11:13 PM
Robert Tweedy <a class="moz-txt-link-rfc2396E" href="mailto:robert@robert-tweedy.com"><robert@robert-tweedy.com></a> wrote:</p>
<blockquote type="cite" class="gmail_quote" style="margin:
0 0 0 0.75ex; border-left: 1px solid #808080;
padding-left: 0.75ex;"> <span style="font-size: 10pt;"><span style="font-family: 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 </span></span><span style="font-size:
10pt;"><span style="font-family: Arial;"><span style="font-size: 10pt;"><span style="font-family:
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" moz-do-not-send="true">"ale-request@ale.org"</a>
stopped working)?</span></span><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>
</span></span><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 moz-txt-link-freetext" href="mailto:Ale@ale.org" moz-do-not-send="true">Ale@ale.org</a>
<a class="moz-txt-link-freetext" href="https://mail.ale.org/mailman/listinfo/ale" moz-do-not-send="true">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" moz-do-not-send="true">http://mail.ale.org/mailman/listinfo</a>
</pre>
</blockquote>
</blockquote>
<br>
</blockquote>
</div>
</div>
<!-- body end -->
</div>
<div dir="auto"><br>
</div>
</div>
</blockquote>
<br>
</blockquote></div><br>-- <br>Computers amplify human error<br>Super computers are really cool</body></html>