It worked!! Many thanks!
- Scott
On Fri, Dec 27, 2024 at 4:52 PM Mark Sapiro wrote:
> On 12/27/24 07:20, Scott Neader wrote:
> > Hello all! Somehow, one of our Mailman2 lists has a member with a bad
> > email address, in the format of user@@example.com (i.e. two @ symbols).
> > This is break
On 12/27/24 14:50, Mark Sapiro wrote:
Then run
```
bin/config_list -i path_to_the_above_file
```
Ooops. That should be
```
bin/config_list -i path_to_the_above_file LISTNAME
```
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B
On 12/27/24 07:20, Scott Neader wrote:
Hello all! Somehow, one of our Mailman2 lists has a member with a bad
email address, in the format of user@@example.com (i.e. two @ symbols).
This is breaking at least one cron (disabled)
I've tried removing the address via the backend admin, as well as c
On Fri, Dec 27, 2024 at 09:20:46AM -0600, Scott Neader wrote:
> Hello all! Somehow, one of our Mailman2 lists has a member with a bad
> email address, in the format of user@@example.com (i.e. two @ symbols).
> This is breaking at least one cron (disabled)
>
> I've tried removing the address via
On Fri, Dec 27, 2024 at 09:55:26PM +, Alain D D Williams wrote:
> On Fri, Dec 27, 2024 at 09:20:46AM -0600, Scott Neader wrote:
> > Hello all! Somehow, one of our Mailman2 lists has a member with a bad
Whoops - just noticed mailman2 rather than mailman3; sorry.
--
Alain Williams
Linux/GNU C
Hello all! Somehow, one of our Mailman2 lists has a member with a bad
email address, in the format of user@@example.com (i.e. two @ symbols).
This is breaking at least one cron (disabled)
I've tried removing the address via the backend admin, as well as command
line, but it's not working.
Any o
