> I consider the netmask to be always primary - any bits set to the right of
Indeed, otherwise 192.168.0.0 would imply a /19
Stefan
> Beyond Viktor's recommendation to NOT chroot Postfix, another option is to
> run Postfix on demand, since you appear to only be running it
> in a client-only mode. I'm not sure how you'd do that on Debian, but the
> general idea is to run 'master -e 60' whenever a file appears in the
> maildrop
> Don't chroot the Postfix smtp delivery agent. It will then notice
> changes in /etc/resolv.conf, rather than using a stale copy in
> the chroot jail. Better don't use chroot at all, unless it is
> very carefully and robustly built.
Ha!
# find /var -name resolv.conf
Ping?
Doesn't anyone have some vague hint of where the problem may be?
Is it really normal for "postqueue -f" to complain about DNS errors, whereas
"/etc/init.d/postfix restart; postqueue -f" works just fine?
Stefan
>>>>> "Stefan" == Ste
For the last few weeks, one of my machines (running Debian stable, with
Postfix 2.11.3) gets constantly stuck with things like:
% mailq
-Queue ID- --Size-- Arrival Time -Sender/Recipient---
CDC7364F79 972 Wed Nov 16 08:12:48 monn...@iro.umontreal.ca
(Host or
[ Fourth try to send this message. Hopefully this one will get through
and hopefully the other ones won't. ]
[ BTW, the policy of silently discard email from non-subscribed
addressesof postfix-users is really obnoxious. ]
I'm using Postfix to send email (via a relayhost) from my laptop
I understand it can't send it anywhere (at least in my case, if the
relayhost rejects the message, there's nowhere to send the message
and/or the bounce), but can't it save the email in some local file,
at least?
Especially when the email originated locally (i.e. was not received via
SMTP
