On 06/08/2013 03:10 PM, Tanstaafl wrote:
>
> I read them all, and I don't think it is relevant (this is the same
> kernel and same versions of postfix dovecot and mailman for some time
> now), but, I changed the default limit to 10 and reloaded postfix, with
> the same error when sending to my 'Al
On 2013-06-08 5:44 PM, Mark Sapiro wrote:
On 06/08/2013 02:21 PM, Tanstaafl wrote:
It also seems to be something to do with how many recipients are
involved. One or two appear to be ok, but more than that and it gets
iffy...
I think that's a coincidence. The biggest problem is with delivery
On 06/08/2013 02:21 PM, Tanstaafl wrote:
>
> It also seems to be something to do with how many recipients are
> involved. One or two appear to be ok, but more than that and it gets
> iffy...
I think that's a coincidence. The biggest problem is with delivery from
Postfix to Mailman, at which poin
On 2013-06-08 1:58 PM, Mark Sapiro wrote:
Actually, private/local and private/retry refer to the sockets used for
communication between the Postfix master and the various daemons. If you
do 'netstat -l' you should see these and many others 'LISTENING', Do you?
Yep, they're all there. And local
I'd suggest trying "ps -auxww|grep mailman" to seem if any mailman
processes are running, this assumes mailman runs as its own user id.
Some installs use the username list or lists instead of mailman.
If nothing show up then I'd check:
1) /etc/postfix/*.cf and /etc/postfix/transport and diff
On 06/08/2013 10:20 AM, Mark Sapiro wrote:
>
> Postfix has received the message and is trying to deliver it via the
> local transport which is good.
>
>
>> 2013-06-08T06:31:12-04:00 myhost postfix/qmgr[3126]: warning: connect to
>> transport private/local: Resource temporarily unavailable
>
>
On 06/08/2013 03:43 AM, Tanstaafl wrote:
>
> I'm getting the following error when trying to send an email to one of
> the lists:
>
> 2013-06-08T06:30:47-04:00 myhost postfix/postsuper[29691]: Requeued: 1
> message
> 2013-06-08T06:31:12-04:00 myhost postfix/pickup[3124]: D55D7B7D175:
> uid=207 fro
On 06/08/2013 08:33 AM, Larry Kuenning wrote:
> On 6/8/2013 8:52 AM, Tanstaafl wrote:
>>
>> Not blank - but what does the question mark mean?
>>
>> # ps -A | grep mailmanctl
>> 2600 ?00:00:00 mailmanctl
>
> Leaving out the "grep" to get the header ("ps -C mailmanctl" would have
> been be
On 06/08/2013 05:10 AM, Larry Kuenning wrote:
>
> (This was the solution for me when I had a similar problem a month and a
> half ago. I would like to know where to plug this in so it happens
> automatically on reboot. That should be an elementary question but I'm
> still not familiar with all t
On 6/8/2013 8:52 AM, Tanstaafl wrote:
On 2013-06-08 8:10 AM, Larry Kuenning wrote:
Is mailman possibly not running? Try this:
ps -A | grep mailmanctl
If that gives blank output, try this:
/usr/lib/mailman/bin/mailmanctl start
Not blank - but what does the question mark mean?
# ps -A | grep
On 2013-06-08 8:10 AM, Larry Kuenning wrote:
Is mailman possibly not running? Try this:
ps -A | grep mailmanctl
If that gives blank output, try this:
/usr/lib/mailman/bin/mailmanctl start
Not blank - but what does the question mark mean?
# ps -A | grep mailmanctl
2600 ?00:00:00 mai
On 6/8/2013 6:43 AM, Tanstaafl wrote:
Ok, we had a power failure, and apparently my UPS thought it had more
time left than it did, as the UPS shut down before it shut down the system.
Everything is back up and running, and postfix is running fine for all
other mail, except list/mailman mail.
Hello,
Ok, we had a power failure, and apparently my UPS thought it had more
time left than it did, as the UPS shut down before it shut down the system.
Everything is back up and running, and postfix is running fine for all
other mail, except list/mailman mail.
I'm getting the following err
13 matches
Mail list logo
