Phill Macey:
> On 10 August 2010 21:35, Wietse Venema wrote:
>
> > When you have a many-recipient "all" alias, you need to set up an
> > "owner-all" alias in the alias database (with the right-hand side
> > being the adminstrator of the "all" list). Besides changing the
> > way errors are reporte
On 10 August 2010 21:35, Wietse Venema wrote:
> When you have a many-recipient "all" alias, you need to set up an
> "owner-all" alias in the alias database (with the right-hand side
> being the adminstrator of the "all" list). Besides changing the
> way errors are reported, this also triggers a d
Hello Wietse,
have not been aware of the difference. Added the owner-alias and will
keep an eye on the list.
Thanks a lot
Dominik
> Dominik Storck:
>> Hello Wietse,
>>
>> I have been looking for these error messages over and over before I
>> started digging deeper. There are none of the error,
Dominik Storck:
> Hello Wietse,
>
> I have been looking for these error messages over and over before I
> started digging deeper. There are none of the error,fatal,warning or
> panic messages before. The first error log entry to occur is the unknown
> mail transport error, really.
Looking at t
Hello Wietse,
I have been looking for these error messages over and over before I
started digging deeper. There are none of the error,fatal,warning or
panic messages before. The first error log entry to occur is the unknown
mail transport error, really.
Dominik
Am 10.08.2010 00:07, schrieb
Dominik Storck:
> Hello Wietse,
>
> I have been tracking down to "Automatically tracing a Postfix daemon
> process" from the DEBUG_README. This is how I got the log snippet.
>
> Can't reproduce the error now after deleting unnecessary .forward files.
Please do not waste your time with verbose lo
Hello Wietse,
I have been tracking down to "Automatically tracing a Postfix daemon
process" from the DEBUG_README. This is how I got the log snippet.
Can't reproduce the error now after deleting unnecessary .forward files.
Hope things will stay this way.
Thank you
Dominik
Am 09.08.2010 22:1
In case you wonder, I wrote Postfix.
Perhaps you can follow instructions in
http://www.postfix.org/.DEBUG_README.html#logging
TURN OFF -v logging before you do this.
Wietse
Hello Andrzej,
thanks for your suggestion. However, increasing ulimit -n did not help
in the first place .
Debugging info by adding -v in master.cf came up with lots of debugging
info yet not leading to success.
After attaching strace to the local daemon, I observed a kind of a loop
when it came
On Wed, Aug 4, 2010 at 10:39, Dominik Storck wrote:
>
> This has been working perfectly for years. Now the number of recipients
> for some of
> these lists have increased to more than 200.
>
> When a mail is sent to these recipients mail delivery starts as expected
> but stops
> short before end o
See http://www.postfix.org/DEBUG_README.html#logging
When Postfix does not receive or deliver mail, the first order of business is
to look for errors that prevent Postfix from working properly:
% egrep '(warning|error|fatal|panic):' /some/log/file | more
Note: the most important message is
Hello,
I have a problem here with mailing lists.
I've configured these as entries in the /etc/aliases like
group-x: :include:/etc/group-x.list
and corresponding files /etc/group-x.list with one line per (local)
recipient
This has been working perfectly for years. Now the number of recipie
12 matches
Mail list logo
