Hi
I have very strong machine with load average: 2,22, 2,32, 2,19
and today i get
Jan 14 12:34:25 thebe postfix/master[4925]: warning:
master_wakeup_timer_event: service qmgr(public/qmgr): Resource
temporarily unavailable
Jan 14 12:39:25 thebe postfix/master[4925]: warning:
master_wakeup_timer_ev
On Fri, Jan 14, 2022 at 12:48:10PM +0100, natan wrote:
> Jan 14 12:34:25 thebe postfix/master[4925]: warning:
> master_wakeup_timer_event: service qmgr(public/qmgr): Resource
> temporarily unavailable
> Jan 14 12:39:25 thebe postfix/master[4925]: warning:
> master_wakeup_timer_event: service qmgr(
natan:
> Hi
> I have very strong machine with load average: 2,22, 2,32, 2,19
>
> and today i get
>
> Jan 14 12:34:25 thebe postfix/master[4925]: warning:
> master_wakeup_timer_event: service qmgr(public/qmgr): Resource
> temporarily unavailable
> Jan 14 12:39:25 thebe postfix/master[4925]: warnin
raf:
> If the distribution itself is working, and the list of
> members doesn't change often, and it's only SPF that's
> getting in the way, perhaps the least disruptive
> solution is to add SRS to Postfix. The problem being
> that someone who sends to the list has SPF on their
> domain and a serve
W dniu 14.01.2022 o 14:54, Wietse Venema pisze:
> natan:
>> Hi
>> I have very strong machine with load average: 2,22, 2,32, 2,19
>>
>> and today i get
>>
>> Jan 14 12:34:25 thebe postfix/master[4925]: warning:
>> master_wakeup_timer_event: service qmgr(public/qmgr): Resource
>> temporarily unavaila
natan:
> W dniu 14.01.2022 o?14:54, Wietse Venema pisze:
> > natan:
> >> Hi
> >> I have very strong machine with load average: 2,22, 2,32, 2,19
> >>
> >> and today i get
> >>
> >> Jan 14 12:34:25 thebe postfix/master[4925]: warning:
> >> master_wakeup_timer_event: service qmgr(public/qmgr): Resourc
> On 2022-01-13 at 20:26:53 UTC-0500 (Thu, 13 Jan 2022 20:26:53 -0500)
> Joe Acquisto-j4
> is rumored to have said:
>
> [...]
>> Would it be valid to presume that an SMTP server that can be connected
>> to,
>> securely, via Outlook, Thunderbird and the other common clients, can
>> be
>> connect
Wietse Venema:
> natan:
> > W dniu 14.01.2022 o?14:54, Wietse Venema pisze:
> > > natan:
> > >> Hi
> > >> I have very strong machine with load average: 2,22, 2,32, 2,19
> > >>
> > >> and today i get
> > >>
> > >> Jan 14 12:34:25 thebe postfix/master[4925]: warning:
> > >> master_wakeup_timer_event:
W dniu 14.01.2022 o 18:11, Wietse Venema pisze:
> Wietse Venema:
>> natan:
>>> W dniu 14.01.2022 o?14:54, Wietse Venema pisze:
natan:
> Hi
> I have very strong machine with load average: 2,22, 2,32, 2,19
>
> and today i get
>
> Jan 14 12:34:25 thebe postfix/master[4925]
On 2022-01-14 at 12:10:23 UTC-0500 (Fri, 14 Jan 2022 12:10:23 -0500)
Joe Acquisto-j4
is rumored to have said:
[...]
> I guess this is going a bit astray, for some viewers anyway, but after
> repeated authentication failures, resorted to (or availed myself of)
> SWAKS and still get authentication f
One addition:
The swaks command line you'll need to test properly will be something like this:
swaks -tls -t tar...@example.com --auth-user joea --server mail.example.com:587
On 2022-01-14 at 12:33:18 UTC-0500 (Fri, 14 Jan 2022 12:33:18 -0500)
Bill Cole
is rumored to have said:
> On 2022-0
> One addition:
>
> The swaks command line you'll need to test properly will be something like
> this:
>
> swaks -tls -t tar...@example.com --auth-user joea --server
> mail.example.com:587
>
Thanks, that got me over that hump. Test email went through,
Now to translate this effort into fixin
Does anyone have a good way of reporting on this?
I see a great deal in the maillog with either an incorrect format (no @ symbol)
or just completely blank ( message-id=<>).
We would like to be able to do the following:
Have a WARN message written to the log so we can report and investigate.
I ha
Gomes, Rich:
> Does anyone have a good way of reporting on this?
> I see a great deal in the maillog with either an incorrect format (no @
> symbol) or just completely blank ( message-id=<>).
According to RFC,the Message-ID header is optional, and therefore,
email without Message-ID MUST NOT BE
natan:
Wietse:
> Do you know if the problem is a kernel limit or a per-process limit?
> Does master have 4096 open files (including network sockets: ip,
> unix-domain, etc.).
Wietse:
> BTW that last one was a trick question: you need a huge number of
> services in master.cf to exceed the 4096 limi
>> One addition:
>>
>> The swaks command line you'll need to test properly will be something like
>> this:
>>
>> swaks -tls -t tar...@example.com --auth-user joea --server
>> mail.example.com:587
>>
>
> Thanks, that got me over that hump. Test email went through,
>
> Now to translate this
On Fri, Jan 14, 2022 at 08:57:31AM -0500, Wietse Venema
wrote:
> raf:
> > If the distribution itself is working, and the list of
> > members doesn't change often, and it's only SPF that's
> > getting in the way, perhaps the least disruptive
> > solution is to add SRS to Postfix. The problem bein
raf:
> If the distribution itself is working, and the list of
> members doesn't change often, and it's only SPF that's
> getting in the way, perhaps the least disruptive
> solution is to add SRS to Postfix. The problem being
> that someone who sends to the list has SPF on their
> domain and a serve
18 matches
Mail list logo
