Vicki Brown:
> How many times do I need to say that /etc/postfix IS postfix.
You can either remove the symlink "/usr/local/cutedge/postfix/etc"
or you can add a configuration setting "alternate_config_directories
= /usr/local/cutedge/postfix/etc".
See email below for more. I have nothing to add t
> On Nov 22, 2015, at 11:13 PM, Peter wrote:
>
> On 11/23/2015 05:51 PM, Vicki Brown wrote:
>> Also, from my discussion with him, Bernard Teo does seem to know what he's
>> doing.
>
> I suggest you type "man postfix", scroll down to the bottom and look at
> the list of authors, then compare th
On 11/23/2015 05:51 PM, Vicki Brown wrote:
> Also, from my discussion with him, Bernard Teo does seem to know what he's
> doing.
I suggest you type "man postfix", scroll down to the bottom and look at
the list of authors, then compare that list to the two people who have
been trying to help you h
On Sun, Nov 22, 2015 at 08:51:46PM -0800, Vicki Brown wrote:
> command_directory = /usr/sbin
> config_directory = /etc/postfix
> daemon_directory = /usr/libexec/postfix
> manpage_directory = /usr/share/man
> queue_directory = /private/var/spool/postfix
> readme_directory = /usr/share/doc/postfix
>
On Sun, Nov 22, 2015 at 08:45:48PM -0800, Vicki Brown wrote:
> How many times do I need to say that /etc/postfix IS postfix.
Zero, instead you need to listen. You're here to get help from
folks who understand Postfix deeply. You can get help, but only
if you start listening, and stop objecting
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
manpage_directory = /usr/share/man
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
sample_directory = /usr/share/doc/postfix/examples
This installation has b
How many times do I need to say that /etc/postfix IS postfix.
> On Nov 20, 2015, at 04:24, Wietse Venema wrote:
>
> Viktor Dukhovni:
>> On Thu, Nov 19, 2015 at 03:26:27PM -0800, Vicki Brown wrote:
>>
>>> The only program that uses /usr/local/cutedge/postfix/etc is.. postfix.
>>
>> Well, the re
Wietse Venema:
> Viktor Dukhovni:
> > On Thu, Nov 19, 2015 at 03:26:27PM -0800, Vicki Brown wrote:
> >
> > > The only program that uses /usr/local/cutedge/postfix/etc is.. postfix.
> >
> > Well, the real Postfix uses /etc/postfix, as evidenced by the errors
> > logged by postdrop(1). Whatever is
Viktor Dukhovni:
> On Thu, Nov 19, 2015 at 03:26:27PM -0800, Vicki Brown wrote:
>
> > The only program that uses /usr/local/cutedge/postfix/etc is.. postfix.
>
> Well, the real Postfix uses /etc/postfix, as evidenced by the errors
> logged by postdrop(1). Whatever is asking sendmail(1) and postd
On Thu, Nov 19, 2015 at 03:26:27PM -0800, Vicki Brown wrote:
> The only program that uses /usr/local/cutedge/postfix/etc is.. postfix.
Well, the real Postfix uses /etc/postfix, as evidenced by the errors
logged by postdrop(1). Whatever is asking sendmail(1) and postdrop(1)
to use that other path
> On Nov 19, 2015, at 14:44, Wietse Venema wrote:
>
> You have programs that STILL USE /usr/local/cutedge/postfix/etc as
> the Postfix configuration directory. Those programs will not work.
The only program that uses /usr/local/cutedge/postfix/etc is.. postfix.
In a typical installation of Cut
We use the Cutedge LaunchDaemons to start postfix and SMTP at boot time. I
don't use it to configure postfix (although I could); I just edit the files
(very rarely up until this past week).
> IIRC from an earlier post of yours, you're using OS X Server
Yes, on the internal IMAP/POP server. Not
On Thu, Nov 19, 2015 at 03:11:14PM -0800, Vicki Brown wrote:
> > You have programs that STILL USE /usr/local/cutedge/postfix/etc as
> >
> > the Postfix configuration directory.
>
> No, I do not.
>
> There is no /usr/local/cutedge/postfix/etc configuration directory; it's
> a symbolic link. Ther
> You have programs that STILL USE /usr/local/cutedge/postfix/etc as
>
> the Postfix configuration directory.
No, I do not.
There is no /usr/local/cutedge/postfix/etc configuration directory; it's a
symbolic link. There is only one postfix config directory.
Please don't shout at me.
> On No
On Thu, 19 Nov 2015, Wietse Venema wrote:
Vicki Brown:
cutedge is a company that makes a mail /postfix startup service front end.
This was a spurious (coincidental) error, long past resolved and
unrelated. /usr/local/cutedge/postfix/etc is actually a symlink
to /etc/postfix...
This is NOT LON
Vicki Brown:
> cutedge is a company that makes a mail /postfix startup service front end.
> This was a spurious (coincidental) error, long past resolved and
> unrelated. /usr/local/cutedge/postfix/etc is actually a symlink
> to /etc/postfix...
This is NOT LONG PAST RESOLVED.
You have programs th
Two questions:
When qmgr says "socket: malformed response" - is there any way yo find out what
response it got?
When qmgr says "Connection refused", does that actually mean the filter refused
to connect? Or that mgr refused to try the filter?
- Vicki
: malformed response
postfix/qmgr[21552]: warning: transport filter failure -- see a previous
warning/fatal/panic logfile record for the problem description
If I dig back to 04:53 I find
postfix/qmgr[21552]: warning: private/filter socket: malformed response
postfix/qmgr[21552]: warning: transport
Vicki Brown:
> I have two long and complicated errors at approximately midnight on both Nov
> 17 and Nov 18; however, the spam checking continued happily for 2 hours after
> that.
>
> mail.log:Nov 18 00:02:31 g3po postfix/pipe[590]: E8F682F69538:
> to=, relay=spamfilter, delay=438, delays=436/0
>> On Nov 18, 2015, at 10:49, Wietse Venema wrote:
>>
>> You need to show PIPE DAEMON logging. That will show WHY the pipe
>> daemon terminated with an error, WHY you are getting "connection
>> refused" errors, and so on.
>>
>>$ grep 'postfix/pipe.*fatal' /some/log/file
>>
>> All Postfix da
Vicki Brown:
> > On Nov 18, 2015, at 03:45, Wietse Venema wrote:
> >
> > Please report the logfile record FROM PROCESS 74861. THAT logfile
> > record says WHY it terminated with a fatal error.
> >
>
> From mail.log
>
> Nov 17 02:38:29 g3po postfix/master[69788]: warning: process
> /usr/libexe
Vicki Brown:
> Nov 17 02:38:29 g3po postfix/qmgr[70628]: warning: transport spamchk failure
> -- see a previous warning/fatal/panic logfile record for the problem
> description
> Nov 17 02:38:29 g3po postfix/master[69788]: warning: process
> /usr/libexec/postfix/pipe pid 74861 exit status 1
Wie
>>
>> /var/log/mail.log shows
>>
>> Nov 17 02:38:29 g3po postfix/qmgr[70628]: warning: private/spamchk socket:
>> malformed response
>> Nov 17 02:38:29 g3po postfix/qmgr[70628]: warning: transport spamchk failure
>> -- see a previous warning/fatal/pani
On 17 Nov 2015, at 18:22, Vicki Brown wrote:
Is there anything I can do to troubleshoot?
Enhance that script to log its failures & capture the stderr of what it
calls rather than just tossing back to Postfix.
17 02:38:29 g3po postfix/qmgr[70628]: warning: private/spamchk socket:
> malformed response
> Nov 17 02:38:29 g3po postfix/qmgr[70628]: warning: transport spamchk failure
> -- see a previous warning/fatal/panic logfile record for the problem
> description
> Nov 17 02:38:29 g3po post
y=0.29, delays=0.04/0/0.16/0.09,
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as C71C93EC722)
Nov 17 02:35:40 g3po postfix/qmgr[70628]: DB1842F5FFDB: removed
Nov 17 02:35:39 g3po spamd[70255]: prefork: child states: II
Then it crashed.
/var/log/mail.log shows
Nov 17 02:38:29 g3po postfix/qmgr[
On Mon, Oct 21, 2013 at 09:51:01PM +0300, Maksim Kulik wrote:
> > Report the output of:
> >
> > ldd bin/posttls-finger
>
> ldd posttls-finger
> posttls-finger:
> libssl.so.8 => /usr/local/lib/libssl.so.8 (0x800ac1000)
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800d29000)
Interesti
On Mon, 21 Oct 2013 18:10:44 +
Viktor Dukhovni articulated:
> Is this the default SSL library for the OS? (/usr/local/lib rather
> than /usr/lib or /lib)?
The latest version, available in the ports system is: OpenSSL 1.0.1e 11
Feb 2013
The default version is: OpenSSL 0.9.8x 10 May 2012, or a
Thank you again!
The problem is fixed now. I just rebuilt openssl port without zlib support.
It solved the problem.
>> Openssl version - openssl-1.0.1_8
>When was it last updated? When did the problem start?
This is the most recent version from freebsd ports. This is new
installation. I just installed Freebsd 9.2 stable, updated ports to the
latest version and installed postfix. The problem started as soon
On Mon, Oct 21, 2013 at 08:02:33PM +0300, Maksim Kulik wrote:
> Postfix version - postfix-2.10.1,1
Probably immaterial. In Postfix 2.11-20131001 you can disable SSL
compression, which seems to be broken below. Sure seems like a
buggy OpenSSL or zlib.
> Openssl version - openssl-1.0.1_8
When w
Viktor, thank you for your help!
Postfix version - postfix-2.10.1,1
Openssl version - openssl-1.0.1_8
FreeBSD version - FreeBSD 9.2-STABLE #1 r256306:
Log and backtrace:
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public L
Maksim Kulik:
> Hello!
> I have postfix 2.10 on freebsd 9.2.
> When i try to send some emails, i get following in mail log:
> Oct 21 16:56:27 1gb postfix/smtp[7038]: < imx6.ngs.ru[195.19.71.16]:25: 220
> imx6.ngs.ru ESMTP ready
> Oct 21 16:56:27 1gb postfix/smtp[7038]: > imx6.ngs.ru[195.19.71.16]:2
t terminator)
> smtp[7038]: input attribute name: (end)
The SMTP client obtained fresh seed material for its from tlsmgr(8) while
getting ready to start a new TLS session.
> Oct 21 16:56:27 1gb postfix/qmgr[1889]: warning: private/smtp socket:
> malformed response
> Oct 21 16:56:27 1
smtp[7038]: input attribute value:
RW5yuoKfeonUvpgq0BdCuA+TZeEsKcnC5boyBvJUgg0=
Oct 21 16:56:27 1gb postfix/smtp[7038]: private/tlsmgr: wanted attribute:
(list terminator)
Oct 21 16:56:27 1gb postfix/smtp[7038]: input attribute name: (end)
Oct 21 16:56:27 1gb postfix/qmgr[1889]: warning: private/smtp socket:
malfo
Per olof Ljungmark:
> On 02/12/12 20:15, Wietse Venema wrote:
> > Per olof Ljungmark:
> >> Feb 12 00:10:18 x61s-po postfix/smtp[31030]: warning: per-session SASL
> >> client initialization: generic failure
> >> Feb 12 00:10:18 x61s-po postfix/smtp[31030]: fatal: SASL per-connection
> >> initializat
On 02/12/12 20:15, Wietse Venema wrote:
> Per olof Ljungmark:
>> Feb 12 00:10:18 x61s-po postfix/smtp[31030]: warning: per-session SASL
>> client initialization: generic failure
>> Feb 12 00:10:18 x61s-po postfix/smtp[31030]: fatal: SASL per-connection
>> initialization failed
>
> Your (Cyrus) SAS
Per olof Ljungmark:
> Feb 12 00:10:18 x61s-po postfix/smtp[31030]: warning: per-session SASL
> client initialization: generic failure
> Feb 12 00:10:18 x61s-po postfix/smtp[31030]: fatal: SASL per-connection
> initialization failed
Your (Cyrus) SASL library reports a generic failure. This is
as go
00:10:18 x61s-po postfix/smtp[31030]: fatal: SASL per-connection
initialization failed
Feb 12 00:10:19 x61s-po postfix/qmgr[13091]: warning: private/smtp
socket: malformed response
Feb 12 00:10:19 x61s-po postfix/qmgr[13091]: warning: transport smtp
failure -- see a previous warning/fatal/panic
Kammen van, Marco, Springer SBM NL:
> Jul 7 12:23:04 servername postfix/qmgr[32036]: warning: transport relay
> failure -- see a previous warning/fatal/panic logfile record for the
> problem description
If the above suggestion was not clear enough, then the following
one may help:
Wietse
Hi All,
The last couple of days I'm seeing more and more of these errors:
Jul 7 12:23:04 servername postfix/master[4219]: warning: process
/usr/local/postfix/libexec/smtp pid 13490 exit status 1
Jul 7 12:23:04 servername postfix/qmgr[32036]: warning: private/relay
socket: malf
41 matches
Mail list logo
