hm?! it was in the mail.XXX log.
Anyhow, as written: solved
THX again 4 ur time.
J
*via www.LinuxMint.com 16:Petra*
Am 17.07.2014 22:12, schrieb Wietse Venema:
> XYZFounder:
>>> 6549.948631801:7f1e801ec700: pipe (3) write error 11: Resource
>>> temporarily unavailab
17.07.2014 21:36, schrieb Wietse Venema:
> XYZFounder:
>> Hi Wietse Venema:
>>
>> I get output in the logs but nothing (no error) why it is held (still)
>> in the queue. BTW Could one somehow bad email holt up the entire queue?!
> You have too much noise in the mail.l
ocessing
> batch[1] via 'builtin-file'
> 6549.952646815:7f1e801ec700: Called action(Batch), logging to builtin-file
> 6549.952783805:7f1e801ec700: X: tryDoAction 0x7677e0, pnElem 2,
> nElem 2
*via www.LinuxMint.com 16:Petra*
Am 17.07.2014 21:36, schrieb Wietse Venema:
&
21:14 0:00 virtual
-t unix
could it be that an OLD virtual instance is messing things up?!
*via www.LinuxMint.com 16:Petra*
Am 17.07.2014 21:22, schrieb XYZFounder:
> Hi Wietse Venema:
>
> I get output in the logs but nothing (no error) why it is held (still)
> in the queue. BTW
, schrieb Wietse Venema:
> XYZFounder:
>>> postfix 30554 0.0 0.0 44248 2548 ?S20:00 0:00 smtp
>>> -t unix -u -c -vv
> Configured in this way. the SMTP client runs in a chroot jail. Turn
:Petra*
Am 17.07.2014 21:01, schrieb Wietse Venema:
> XYZFounder:
>>> postfix 30554 0.0 0.0 44248 2548 ?S20:00 0:00 smtp
>>> -t unix -u -c -vv
> Configured in this way. the SMTP client runs in a chroot
here:
> root@gFort:/etc/postfix# postqueue -f
> root@gFort:/etc/postfix# ps aux | grep virtual
> root 9240 0.0 0.0 12232 936 pts/3S+ 20:48 0:00 grep
> virtual
> postfix 20024 0.0 0.0 59372 2232 ?TJul14 0:00
> virtual -t unix
> postfix 30550 0.0 0.1 59372 3
I am soon leaving this great list again. If anybody has a clue and is
willing to share, drop me a note directly..
J
*via www.LinuxMint.com 16:Petra*
Am 17.07.2014 07:19, schrieb XYZFounder:
>
> logging works as said b4:
>
> https://workaround.org/ispmail/wheezy/connecting-postfix-to-
014 05:18, schrieb Viktor Dukhovni:
> On Thu, Jul 17, 2014 at 05:06:02AM +0200, XYZFounder wrote:
>
>> [long list of anecdotal problems]
> Fix logging first. If Postfix services are chrooted, make sure
> there is a log socket in the chroot jail or disable chroot. Once
> logging
Hi,
I am running a debian 7 server. All good. I guess after an recent
generel server update (may not be linked) rsyslog and postfix stop to
really be working.
rsyslog could not be started and was fixed with rsyslogd -c5 so that log
functionality returned.
But with postfix all inbound messages
10 matches
Mail list logo
