On Sat, Dec 28, 2024 at 5:48 PM Mark Sapiro wrote:
> To clean this completely put the following in a file
> ```
> for attribute in (
> mlist.admin_responses,
> mlist.bounce_info,
> mlist.delivery_status,
> mlist.hold_and_cmd_autoresponses,
> mlist.language,
> mlist.o
On 12/28/24 15:13, Scott Neader wrote:
After successfully removing the problematic user (with the two @ in their
email address), I am still seeing a problem with the 'disabled' cron,
pointing to this user that was already removed (thanks to your help).
Here's the cron output (with the offending e
After successfully removing the problematic user (with the two @ in their
email address), I am still seeing a problem with the 'disabled' cron,
pointing to this user that was already removed (thanks to your help).
Here's the cron output (with the offending email address redacted)
# /usr/bin/python
