On Sat, 2022-02-19 at 12:03 -0800, Mark Sapiro wrote:
On 2/19/22 08:33, William Oliver wrote:
So... I run a small mailinglist using mailman3 that has been workiing great for a couple of months. Last week, all my users from gmail got kicked off because gmail decided that the list messages were "unsolicited email". I didn't find out about it until the users hit their mailman3 bounce limit. I *thought* would be seeing all the bounce messages, but apparently not. I didn't see any config settings for "see all the bounce messages" so i thought to myself, "Self, well maybe that's because my mailinglist username doesn't have a mailbox in /home/listname".
Assuming your Mailman core version is 3.3.5 and Postorius is 1.3.6, you will see settings like
Notify owner on bounce increment,Notify owner on disableandNotify owner on removalunderBounce Processing. Presumable you did get the notification of removal, so delivery to the owner works. Are the increment and disable (or maybe just disable if your versions are older) notices set to Yes?
Found it. Thanks.
So, I decided to try that. I created /home/listname/Maildir/* and logged in as fplist to see if it would put mail there. In order to log in as listname, I gave the user listname a password.
Can't you just reverse those steps. I.e. remove /home/listname/ and remove the listname user?
Well, that was my inclination, but I didn't know if I needed to have a user by the name of listname. I was afraid that if I just deleted the user "listname" it would cause even more problems.
I had created that user back when I was using another mailinglist package -- a Joomla plugin (that doesn't work nearly as well as mailman3). I was afraid to just type in "userdel -r" in case mailman3 needed a "real" user...
So, I can just kill the listname user altogether?
billo