On 02/20/2016 02:42 PM, Mark Sapiro wrote:
> On 2/20/16 6:06 AM, Fernando Gont wrote:
>>
>> Meta answer: quite to my surprise, the problem was that mailman wasn't
>> running. Apparently the reason was that, when the system was rebooted,
>> mailman failed to start because there was no mailman@ list.
On 02/23/2016 12:53 PM, Fernando Gont wrote:
> On 02/20/2016 02:42 PM, Mark Sapiro wrote:
>>
>> Yes, it is needed. It is the sender of various notices including monthly
>> password reminders an the recipient of bounces thereof.
>
> Why do yu actually need a *list* for sending such info?
You don
On 2/20/16 6:06 AM, Fernando Gont wrote:
>
> Meta answer: quite to my surprise, the problem was that mailman wasn't
> running. Apparently the reason was that, when the system was rebooted,
> mailman failed to start because there was no mailman@ list. Once I
> created it, the problem was solved. (i
Hello, Mark,
Thanks so much for your kind help.
Meta answer: quite to my surprise, the problem was that mailman wasn't
running. Apparently the reason was that, when the system was rebooted,
mailman failed to start because there was no mailman@ list. Once I
created it, the problem was solved. (is
On 02/16/2016 10:14 PM, Fernando Gont wrote:
> Essentially, any emails that I send to the mail-robot aliases (e.g.
> listname-requ...@mydomain.com) are kind of blackholed: I don't get a
> response from mailman, but I also don't get any sort of "user unknown
> message" either.
>
> Similarly, if I
Folks,
I'm running a Ubuntu with Postfix and Mailman. Everything was up and
running, and somehow mailman started to fail (we migrated the virtual
machine to a different container, but I'd expect this to be orthogonal..
so.. not sure what happened).
Essentially, any emails that I send to the mail-
