ahan wrote:
> >
> > Jan 21 12:20:41 ns postfix/smtpd[31736]: NOQUEUE: reject: RCPT from
> mta2.email.famousfootwear.com[136.147.183.86]: 450 4.1.1 :
> Recipient address rejected: unverified address: unknown mail transport
> error; from=<
> bounce-299_html-404541337-2436561-722288
Patrick Mahan:
> FreeBSD 11.2, Postfix 3.3.2, Dovecot 2.3.4
>
> Random user verification failures are occurring and I am not sure why.
>
> Here's an example -
>
> >From /var/log/maillog:
>
> Failure:
>
> Jan 21 12:20:41 ns postfix/smtpd[31736]: NOQUEUE: reject: RCPT from
> mta2.email.famousfoo
> On Jan 21, 2019, at 3:44 PM, Patrick Mahan wrote:
>
> Jan 21 12:20:41 ns postfix/smtpd[31736]: NOQUEUE: reject: RCPT from
> mta2.email.famousfootwear.com[136.147.183.86]: 450 4.1.1 :
> Recipient address rejected: unverified address: unknown mail transport error;
> from=
50 4.1.1 :
Recipient address rejected: unverified address: unknown mail transport
error; from=<
bounce-299_html-404541337-2436561-7222883-9...@bounce.email.famousfootwear.com>
to= proto=ESMTP helo=
Jan 21 12:20:41 ns dovecot: lmtp(31763): Connect from local
Jan 21 12:20:41 ns dovec
Am 25.06.2015 um 19:57 schrieb Wietse Venema:
J. Echter:
Am 22.06.2015 um 21:16 schrieb Wietse Venema:
J. Echter:
Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
Wietse:
It was unable to query the services(5) database via the mechanism
specified in nsswitch.conf.
J
J. Echter:
> Am 22.06.2015 um 21:16 schrieb Wietse Venema:
> > J. Echter:
> >> Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
> > Wietse:
> >> It was unable to query the services(5) database via the mechanism
> >> specified in nsswitch.conf.
> > J. Echter:
> >> nsswitch.c
Am 22.06.2015 um 21:16 schrieb Wietse Venema:
J. Echter:
Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
Wietse:
It was unable to query the services(5) database via the mechanism
specified in nsswitch.conf.
J. Echter:
nsswitch.conf says:
services: files
This mean
Am 22.06.2015 um 21:16 schrieb Wietse Venema:
J. Echter:
Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
Wietse:
It was unable to query the services(5) database via the mechanism
specified in nsswitch.conf.
J. Echter:
nsswitch.conf says:
services: files
This mean
Am 22.06.2015 um 21:16 schrieb Wietse Venema:
J. Echter:
Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
Wietse:
It was unable to query the services(5) database via the mechanism
specified in nsswitch.conf.
J. Echter:
nsswitch.conf says:
services: files
This mean
J. Echter:
> Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
Wietse:
> It was unable to query the services(5) database via the mechanism
> specified in nsswitch.conf.
J. Echter:
> nsswitch.conf says:
> services: files
This means the nsswitch system library cannot open
Am 22.06.2015 um 16:38 schrieb Wietse Venema:
J. Echter:
Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
It was unable to query the services(5) database via the mechanism
specified in nsswitch.conf.
Wietse
nsswitch.conf says:
services: files
any 'files' o
, delays=202410/1/0/0.01,
dsn=4.3.0, status=deferred (unknown mail transport error)
Jun 22 20:20:55 mule postfix/qmgr[28173]: warning: private/smtp socket:
malformed response
Jun 22 20:20:55 mule postfix/qmgr[28173]: warning: transport smtp
failure -- see a previous warning/fatal/panic logfile
Am 22.06.2015 um 14:47 schrieb Ralf Hildebrandt:
* J. Echter :
Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
postfix check
is reporting what?
'postfix check' has no output
greets
juergen
J. Echter:
> Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
It was unable to query the services(5) database via the mechanism
specified in nsswitch.conf.
Wietse
* J. Echter :
> Jun 22 10:26:38 mule postfix/smtp[6901]: fatal: unknown service: smtp/tcp
postfix check
is reporting what?
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patric
Am 22.06.2015 um 12:43 schrieb Wietse Venema:
J. Echter:
Hi,
my harddisk run out of space and now i have a few messages in queue with
that error:
status=deferred (unknown mail transport error)
When Postfix does not receive or deliver mail, the first order of business is
to look for errors
J. Echter:
> Hi,
>
> my harddisk run out of space and now i have a few messages in queue with
> that error:
>
> status=deferred (unknown mail transport error)
When Postfix does not receive or deliver mail, the first order of business is
to look for errors that prevent Po
Hi,
my harddisk run out of space and now i have a few messages in queue with
that error:
status=deferred (unknown mail transport error)
How to handle these messages?
I tried to redirect them to another recipient address, but they are
still listed in queue.
Any advice would be helpful
On 4/8/2012 4:58 μμ, Morten Stevens wrote:
Do you have an IPv6 address in your /etc/resolv.conf?
Thanks Morten for the feedback,
Yes, I had IPv6 address(es) in /etc/resolv.conf !
Things are clearer now!
I had:
Jul 13 12:10:30 Updated: glibc-2.12-1.80.el6.x86_64
Jul 13 12:11:43 Updated: glib
On 04.08.2012 15:50, Nikolaos Milas wrote:
On 4/8/2012 11:11 πμ, Nikolaos Milas wrote:
I guess something might have been broken in this system.
In /var/log/messages I found large number of errors like:
Aug 3 14:41:13 dc kernel: smtp[13853]: segfault at 1 ip
7f9522e38596 sp 7fff633a5
On 4/8/2012 11:11 πμ, Nikolaos Milas wrote:
I guess something might have been broken in this system.
In /var/log/messages I found large number of errors like:
Aug 3 14:41:13 dc kernel: smtp[13853]: segfault at 1 ip
7f9522e38596 sp 7fff633a5fc0 error 6 in
libresolv-2.12.so[7f9522e2c
On 4/8/2012 1:25 πμ, Morten Stevens wrote:
If you want to try it:
http://download.imt-systems.com/postfix/2.9.4/
Thanks Morten,
I tried it and initially it did not work (same problem). I guess
something might have been broken in this system.
I then did a system upgrade and after that I re
On 03.08.2012 23:59, Nikolaos Milas wrote:
On 3/8/2012 4:49 μμ, Wietse Venema wrote:
Has the program worked after it was installed? Then find out what
has changed recently. One of those changes broke Postfix.
Searching in logs, I found it was working correctly until Jul 13,
when I upgraded t
Nikolaos Milas:
> On 3/8/2012 4:49 ??, Wietse Venema wrote:
>
> > Has the program worked after it was installed? Then find out what
> > has changed recently. One of those changes broke Postfix.
> >
>
> Searching in logs, I found it was working correctly until Jul 13, when I
> upgraded to CentOS
On 3/8/2012 4:49 μμ, Wietse Venema wrote:
Has the program worked after it was installed? Then find out what
has changed recently. One of those changes broke Postfix.
Searching in logs, I found it was working correctly until Jul 13, when I
upgraded to CentOS 6.3.
I now upgraded to Postfix 2
On 03.08.2012 15:41, Nikolaos Milas wrote:
Basically, I've installed (and I am using):
[root@dc postfix]# rpm -qa | grep ltb
openldap-ltb-2.4.31-1.el6.x86_64
berkeleydb-ltb-4.6.21.NC-4.el6.patch4.x86_64
openldap-ltb-debuginfo-2.4.31-1.el6.x86_64
There also exist:
db4-4.7.25-17.el6.x86_64
db4-u
Nikolaos Milas:
> Any ideas?
Has the program worked after it was installed? Then find out what
has changed recently. One of those changes broke Postfix.
Has the program never worked after it was installed? Then it was
built incorrectly. Follow my instructions or ask your maintainer.
I give supp
On 3/8/2012 4:16 μμ, Wietse Venema wrote:
ldd(1) is your friend.
Thanks Wietse,
Does this help?
[root@dc postfix]# ldd smtp
linux-vdso.so.1 => (0x7fff275ff000)
libldap-2.4.so.2 => /usr/local/openldap/lib64/libldap-2.4.so.2
(0x7fe2b796d000)
liblber-2.4.so.2 => /usr/local/openldap/lib
Nikolaos Milas:
> Aug 3 15:09:46 dc postfix/master[13988]: warning: process
> /usr/libexec/postfix/smtp pid 13997 killed by signal 11
If the program worked before this happened, suspect DLL hell.
Mixing different versions of Berkeley DB, upgrading a third-party
library (SASL, etc.) that introduc
er
throws an "unknown mail transport error" when delivering local logwatch
messages (the only ones generated currently).
Can anyone suggest some solution? I've tried various things (emptied the
queue, configured particular inet_interfaces) without success.
Thanks i
gt; Dec 9 14:15:32 esprimo postfix/qmgr[8828]: warning: private/smtp
>> socket: malformed response
>> Dec 9 14:15:32 esprimo postfix/qmgr[8828]: warning: transport smtp
>> failure -- see a previous warning/fatal/panic logfile record for the
>> problem description
>> Dec
g/fatal/panic logfile record for the
problem description
Dec 9 14:15:32 esprimo postfix/error[9241]: 990CA32C2F:
to=, relay=none, delay=0.44,
delays=0.35/0.01/0/0.08, dsn=4.3.0, status=deferred (unknown mail
transport error)
same is the case with testuser1
Dec 9 14:18:17 esprimo postfix/pickup
Sufian Hameed:
> Dec 9 14:15:32 esprimo postfix/master[8826]: warning: process
> /usr/libexec/postfix/smtp pid 9235 killed by signal 11
>
> what seems to be the problems ?
You MUST respect the instructions in the mailing list welcome message.
Wietse
TO REPORT A PROBLEM see http://www.p
On Dec 9, 2010, at 7:22 AM, Sufian Hameed wrote:
> Dec 9 14:18:18 esprimo postfix/qmgr[8828]: warning: transport smtp failure
> -- see a previous warning/fatal/panic logfile record for the problem
> description
what does this log entry say ?
cription
Dec 9 14:15:32 esprimo postfix/error[9241]: 990CA32C2F:
to=, relay=none, delay=0.44, delays=0.35/0.01/0/0.08,
dsn=4.3.0, status=deferred (unknown mail transport error)
same is the case with testuser1
Dec 9 14:18:17 esprimo postfix/pickup[8827]: E6BCC32C30: uid=503
from=
Dec 9 14:18
il server (postfix 2.2.10, Devecot, IMSS/SPS 7.0).
I noticed recently that some emails are delivered with very late (some
hours, one or 2 days) even if the emails are sent from a local domain
user
to a local domain user.
In the mailq, i can see the bounced emails with the error (delivery
t
rily suspended: unknown mail transport error).
Is there any idea that can help?
Thank you in advance.
Rachid
--
one or 2 days) even if the emails are sent from a local domain user
to a local domain user.
In the mailq, i can see the bounced emails with the error (delivery
temporarily suspended: unknown mail transport error).
Is there any idea that can help?
Thank you in advance.
Rachid
--
domain user.
>
> In the mailq, i can see the bounced emails with the error (delivery
> temporarily suspended: unknown mail transport error).
>
> Is there any idea that can help?
You need to report panic/fatal/warning messages from your mail logfile.
http://www.postfix.org/DEBUG_README.html#logging
Wietse
days) even if the emails are sent from a local domain
user to a local domain user.
In the mailq, i can see the bounced emails with the error (delivery
temporarily suspended: unknown mail transport error).
Is there any idea that can help?
It may help by finding what is really going on.
To do
(delivery
> temporarily suspended: unknown mail transport error).
>
> Is there any idea that can help?
>
> Thank you in advance.
>
> Rachid
>
--
the error (delivery
temporarily suspended: unknown mail transport error).
Is there any idea that can help?
Thank you in advance.
Rachid
The Doctor:
> I am trying to send via majordomo but yet
> I do see
>
> Dec 1 10:35:28 doctor doctor[31]: postfix/error[22238]: 371E112CFAB3:
> to=, relay=none, delay=157827, delays=157783/43/0/0.21, dsn=4.3.0,
> status=deferred (unknown mail transport error)
>
> This
relay=none, delay=157827, delays=157783/43/0/0.21, dsn=4.3.0,
> > status=deferred (unknown mail transport error)
> >
> > This is the first time I have seen this.
> >
> > What can done to rectify?
> >
>
>
> What's with the domain-less to= ?
On 12/1/2010 12:45 PM, The Doctor wrote:
> I am trying to send via majordomo but yet
> I do see
>
> Dec 1 10:35:28 doctor doctor[31]: postfix/error[22238]: 371E112CFAB3:
> to=, relay=none, delay=157827, delays=157783/43/0/0.21, dsn=4.3.0,
> status=deferred (unknown ma
I am trying to send via majordomo but yet
I do see
Dec 1 10:35:28 doctor doctor[31]: postfix/error[22238]: 371E112CFAB3:
to=, relay=none, delay=157827, delays=157783/43/0/0.21, dsn=4.3.0,
status=deferred (unknown mail transport error)
This is the first time I have seen this.
What can done to
Thanks for responding. It appears that we had a duplicate mail alias, which
caused the ldap map to return two mailhosts and made our smtp processes
die. Fixed that and the problem seems to have gone away.
Rich
Rich Bishop:
> Sep 30 20:22:18 jay postfix/qmgr[10510]: qmgr_transport_throttle: transport
> smtp: status: 4.3.0 reason: unknown mail transport error
> Sep 30 20:22:18 jay postfix/qmgr[10510]: warning: transport smtp failure --
> see a previous warning/fatal/panic logfile record for
I have a RHEL5 machine running Redhat's build of postfix 2.3.3 and am having
problems with messages being sporadically deferred with 'unknown mail transport
error'.
The machine is a gateway for listserv, so it does receive lots of mail at
times. It appears that the problem is
On Sun, Aug 22, 2010 at 11:17 PM, Wietse Venema wrote:
> Squeeshh Me:
>> Wietse: ok, here it is:
>> egrep '(warning|error|fatal|panic):' /var/log/maillog | more
>>
>> Aug 22 21:50:17 node2 postfix/virtual[71240]: panic: file size limit
>> 100 < message size 1498997.
>
> Your Postfix version w
Squeeshh Me:
> Wietse: ok, here it is:
> egrep '(warning|error|fatal|panic):' /var/log/maillog | more
>
> Aug 22 21:50:17 node2 postfix/virtual[71240]: panic: file size limit
> 100 < message size 1498997.
Your Postfix version was modified with an unofficial patch
that implements quota in th
On Sun, Aug 22, 2010 at 10:21 PM, Wietse Venema wrote:
> Squeeshh Me:
>> Hi,
>>
>> Thanks for replying. My bad, I realised I posted the log message from
>> /var/log/message. It's quite similar to what I get in postfix log
>> too. Here's the postfix /var/log/mailog version of a test mail that I ju
Squeeshh Me:
> Hi,
>
> Thanks for replying. My bad, I realised I posted the log message from
> /var/log/message. It's quite similar to what I get in postfix log
> too. Here's the postfix /var/log/mailog version of a test mail that I just
> sent, hope this is better (also there are no other warnin
status=deferred
(unknown mail transport error)
mailq command:
4F4056EB019 1498409 Sun Aug 22 21:50:17 sen...@aaa.com
(unknown mail transport
error)
r...@aaa.com
On Sun, Aug 22, 2
Squeeshh Me:
> Aug 21 11:12:55 node1 kernel: pid 40382 (virtual), uid 5000: exited on
> signal 6
For details, look in your MAILLOG file.
Wietse
http://www.postfix.org/DEBUG_README.html#logging
Look for obvious signs of trouble
Postfix logs all failed and successful deliveries to a logf
Hi Folks,
Need your advise on how to solve a problem related to 'unknown mail
transport error'. I've narrowed the error to linked to VDA. VDA works fine
for cases where (incoming mail size) + (existing mailbox file size) is
greater than the quota set for the mailbox.
Example:
Quo
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
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 the original problem report:
>
> Aug 2 14:52:06 postfix postfix/local[29097]: 720441D34008:
> t
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, r
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
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
cipients mail delivery starts as expected
>> but stops
>> short before end of list. The exact count changes, probably due to
different
>> state of of concurrent mail queue entries.
>>
>> The error message is an "unknown mail transport error", the mail stays
>>
ps
> short before end of list. The exact count changes, probably due to different
> state of of concurrent mail queue entries.
>
> The error message is an "unknown mail transport error", the mail stays
> in the queue and
> delivery starts over again from the beginni
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
postfix postfix/local[29097]: 720441D34008:
to=, orig_to=,
relay=local, delay=77, delays=0.23/0/0/77, dsn=2.0.0, status=sent
(delivered to maildir)
Aug 2 14:52:08 postfix postfix/error[32270]: 720441D34008:
to=, relay=none, delay=79, delays=0.23/79/0/0.67,
dsn=4.3.0, status=deferred (unknown
j...@weitan.org:
> But now for my understanding how mail is processed:
>
> the qmgr first makes a lookup locally and if not successful he will
> proceed to the relay-entries?
No, I guess that is how EXIM works.
With Postfix, the queue manager asks a different daemon (trivial-rewrite).
This daemo
On Tue, Jun 15, 2010 at 03:58:43PM +0200, j...@weitan.org wrote:
> the qmgr first makes a lookup locally and if not successful he will
> proceed to the relay-entries?
No. See
http://www.postfix.org/ADDRESS_REWRITING_README.html
http://www.postfix.org/OVERVIEW.html
http://
Hi,
> http://www.postfix.org/STANDARD_CONFIGURATION_README.html
>
> Look for mail gateway.
Works.
Thanks.
But now for my understanding how mail is processed:
the qmgr first makes a lookup locally and if not successful he will
proceed to the relay-entries?
qmgr -> try to deliver local if NOT suc
j...@weitan.org:
[ Charset ISO-8859-1 unsupported, converting... ]
> Hi,
>
> > Do not list weitan.org in mydestination. It should be a relay
> > destination. Therefore, use relay_domains and relay_recipient_maps
> > as explained in ADDRESS_CLASS_README and STANDARD_CONFIGURATION_README.
>
> > Use
Hi,
> Do not list weitan.org in mydestination. It should be a relay
> destination. Therefore, use relay_domains and relay_recipient_maps
> as explained in ADDRESS_CLASS_README and STANDARD_CONFIGURATION_README.
> Use virtual_alias_maps (NOT VIRTUAL ALIAS DOMAINS) to deliver that
> one user locall
j...@weitan.org:
> My intention is:
>
> everyth...@weitan.org relay to weitan.org
Do not list weitan.org in mydestination. It should be a relay
destination. Therefore, use relay_domains and relay_recipient_maps
as explained in ADDRESS_CLASS_README and STANDARD_CONFIGURATION_README.
> Now, how c
Hi Wietse,
main.cf:
+ mailbox_transport=smtp:[weitan.org] # forward everything ...
+ mailbox_transport_maps=hash:/etc/postfix/mailbox_transport_maps # ...
except some mails
With mailbox_transport_maps:
+ jan local
You have set up an infinite loop, asking the local delivery agent
t
Hi Wietse,
>> main.cf:
>> + mailbox_transport=smtp:[weitan.org] # forward everything ...
>> + mailbox_transport_maps=hash:/etc/postfix/mailbox_transport_maps # ...
>> except some mails
>>
>> With mailbox_transport_maps:
>> + jan local
>
> You have set up an infinite loop, asking the local delivery
red in /var/mail/jan
>
> 2.) adding the following config to main.cf gives unknown mail transport error
>
> main.cf:
> + mailbox_transport=smtp:[weitan.org] # forward everything ...
> + mailbox_transport_maps=hash:/etc/postfix/mailbox_transport_maps # ...
> except some mails
>
Dear list,
to cut it short:
1.) local delivery works well without mailbox_transport_maps configured
postfix/local: to=, relay=local (..) status=sent
(delivered to mailbox)
Mail entered in /var/mail/jan
2.) adding the following config to main.cf gives unknown mail transport error
main.cf
Цитат от Brian Evans - Postfix List :
> On 12/10/2009 11:57 AM, c...@mail.bg wrote:
>> Hello I'm having weird problems with unknown mail transport error.
>>
>> I moved a working postfix server from a linux machine to a netbsd one
>> and at first I thou
On 12/10/2009 11:57 AM, c...@mail.bg wrote:
> Hello I'm having weird problems with unknown mail transport error.
>
> I moved a working postfix server from a linux machine to a netbsd one
> and at first I thought everything was working. I am receiving emails
> to all my mail
Hello I'm having weird problems with unknown mail transport error.
I moved a working postfix server from a linux machine to a netbsd one
and at first I thought everything was working. I am receiving emails
to all my mails that are hosted on this server, however I can't send
ma
Oops.. just noticed that the Subject of this thread isn't very
descriptive for what I was asking. I was tackling an error condition
and was going to ask about it, but then resolved it. Apparently I
edited the draft without editing the subject. It should've read "How
to restrict mail reception of so
Thanks for that information! It pointed me to the right direction.
Yes, I was using "accounts" and "addresses" interchangeably because I
wanted to be able to control both. In other words, there are both
actual accounts (virtual and UNIX) and addresses (aliases) that either
need to be accessible pub
On Sunday, June 21, 2009 at 21:12 CEST,
Ville Walveranta wrote:
> I'm finally implementing into production the systems for which I got
> excellent advise from this list last fall (or was it last summer?).
> However, I have one issue I haven't been able to figure out: How do
> I restrict mail
Hello all,
I'm finally implementing into production the systems for which I got
excellent advise from this list last fall (or was it last summer?).
However, I have one issue I haven't been able to figure out: How do I
restrict mail reception only to certain accounts from external
sources? The syst
Henri Chevreton:
> Feb 13 14:25:37 alty postfix/master[3972]: warning: process
> /usr/lib/postfix/local pid 19045 killed by signal 6
That is your problem.
Wietse
rning: private/local socket:
malformed response
Feb 13 14:25:37 alty postfix/qmgr[18753]: qmgr_transport_throttle:
transport local: status: 4.3.0 reason: unknown mail transport error
Feb 13 14:25:37 alty postfix/qmgr[18753]: warning: transport local
failure -- see a previous warning/fatal/panic logfile r
87 matches
Mail list logo
