Hi Ralf,
I've checked the postfix package again and it _IS_ correct. I've
a different guess as this is only one way your could end up with
default_privs = root in main.cf: Either you manually configured it or
you bootstrapped incorrectly. Please do the following and compare it
with my values
Hello List !
There is a problem with postfix-2.4.1 (at least) packaged in
openpkg. When starting, it complains about bad permissions on binaries;
-bash-3.00# postfix start
postfix/postfix-script: warning: not owned by group postdrop:
/openpkg/sbin/postqueue
postfix/postfix-script: warning
On Wed, May 30, 2007, Olivier Kaloudoff wrote:
There is a problem with postfix-2.4.1 (at least) packaged in openpkg.
When
starting, it complains about bad permissions on binaries;
-bash-3.00# postfix start
postfix/postfix-script: warning: not owned by group postdrop:
/openpkg
On Wed, May 30, 2007, Olivier Kaloudoff wrote:
Yes Ralf, for the binaries, G is different;
bash-3.00# openpkg rpm -V postfix
S.5...GT c /openpkg/etc/postfix/access
S.5...GT c /openpkg/etc/postfix/aliases
S.5...GT c /openpkg/etc/postfix/canonical
S.5...GT c /openpkg/etc/postfix
Ralf,
building postfix on a brand new install (debian etch), postfix
refuses to start with the following error;
minimal_etch:/# postfix start
postfix: fatal: file /openpkg/etc/postfix/main.cf: parameter
default_privs: user root has privileged user ID
minimal_etch:/# type postfix
Le mercredi 30 mai 2007, Ralf S. Engelschall écrivait :
Strange. I've no clue why this is the case and how it happened for you.
Please fix it by reinstalling the postfix package via openpkg rpm
-Uvh --force.
hi kalou,
please, try a :
ldd
and checks the dependants libraries.
(sometime
On Wed, May 30, 2007, Olivier Kaloudoff wrote:
building postfix on a brand new install (debian etch), postfix
refuses to start with the following error;
minimal_etch:/# postfix start
postfix: fatal: file /openpkg/etc/postfix/main.cf: parameter default_privs:
user root has
is set to no, but at the
end of the build process, I get:
(...)
rpmtool:files: pass 1 (preparation and syntactical expansions)
rpmtool:files: pass 2 (filesystem-based expansions)
rpmtool:files: pass 3 (duplication removal and cleanup)
+ exit 0
error: Bad file: /openpkg/RPM/SRC/postfix/postfix-2.4.0
file: /openpkg/RPM/SRC/postfix/postfix-2.4.0-whoson.patch: No
such file or directory
The rpmbuild process looks for all files declared in Source and
Patch lines, complaining loudly if something is missing.
I generally create a file, build.sh, in the SRC/package directory
with the options I want
Wilson Jason[EMAIL PROTECTED] wrote on 2007-03-01 04:26:
This I have done and worked out the order of the parameters is
important.
Using 'syslog(target=remote)' fails, but
'syslog(remotehost=localhost,target=remote)'
works.
The remotehost parameter needs to be specified before you
Wilson Jason[EMAIL PROTECTED] wrote on 2007-02-28 02:00:
Could someone please help me with configuring postfix to sends its logs to
both a local file and to a syslog server?
For debugging aid please have a look at the last paragraph of
http://marc.theaimsgroup.com/?l=openpkg-devm
into a huge string.
This also leads to
the problem of one defective file - independent of the
application - affects
all fsl applications.
Had worked this out too.
Ok - recompiled fsl with debugging enabled and then postfix
with the new fsl library.
By doing this I was able to see messages like
Replying to myself -
Some additional testing I managed to break it down to:
fsl-l2tool 'syslog(target=remote)'
l2tool:ERROR: failed to parse specification (invalid use; line
1, column 23: `ote)'; failed to configure channel with
'target=remote')
It would appear to me that the configuration
Could someone please help me with configuring postfix to sends its logs
to both a local file and to a syslog server?
I have read the online FAQ at http://www.ossp.org/pkg/lib/fsl/faq.html
and I still cant seem to get it to work.
The configuration file I have is shown below. I have tried many
On Thu, Jan 11, 2007, Ralf S. Engelschall wrote:
FYI: Those of you who are using the Postfix MTA with UCE prevention
configuration, please notice that e.g. the ORBL.org recently has closed
its doors and that a few others are also no longer available. I've
reinvestigated which RBLs are still
Doug Summers wrote:
Caleb Epstein wrote:
On 6/19/06, Doug Summers [EMAIL PROTECTED] wrote:
I'm having a weird Postfix problem that's only affecting 2 machines. All
of my machines are in the same domain, although some are in a different
subnet. Using the same OpenPKG postfix binaries
On 6/19/06, Doug Summers [EMAIL PROTECTED] wrote:
I'm having a weird Postfix problem that's only affecting 2 machines. All
of my machines are in the same domain, although some are in a different
subnet. Using the same OpenPKG postfix binaries and the exact same
main.cf file (all systems forward
Caleb Epstein wrote:
On 6/19/06, Doug Summers [EMAIL PROTECTED] wrote:
I'm having a weird Postfix problem that's only affecting 2 machines. All
of my machines are in the same domain, although some are in a different
subnet. Using the same OpenPKG postfix binaries and the exact same
main.cf file
Am Dienstag, 21. März 2006 12:47 schrieb Torsten Homeyer:
Ralf S. Engelschall wrote:
On Tue, Mar 21, 2006, Bernhard Reiter wrote:
[...]
Thus I am suggesting the following patch (only minimally tested).
[...]
+{ ! ps -elf|grep postfix/m[a]ster /dev/null 21 \
+ /kolab
to test for the postfix process in the process list
please check it is the one you expect (the OpenPKG postfix master),
not just any postfix master process before you decide to kill it.
According to my kill manpages, kill -0 will only check if the process
exists, not try to actually send
are horribly and totally unelegant, but
they work on all known Unix platforms...
And there my be more than one OpenPKG instance with a running Postfix on
a given system.
Yes!
It is a lot better to precisely look for the one postfix process we want,
Ralf suggestion does this.
Nevertheless we
Torsten Homeyer [EMAIL PROTECTED] writes:
Ralf S. Engelschall wrote:
On Tue, Mar 21, 2006, Bernhard Reiter wrote:
[...]
Thus I am suggesting the following patch (only minimally tested).
[...]
+{ ! ps -elf|grep postfix/m[a]ster /dev/null 21 \
+ /kolab/libexec/postfix/master
Am Montag, 20. März 2006 13:32 schrieb Bernhard Reiter:
Using OpenPKG 2.5
b) postfix
/kolab/sbin/postfix start
failed, because of an old master.pid (without process).
The message of postfix-scripts did not end up in the logs
and openpkg did not fail.
This was more complicated then I have
Am Montag, 20. März 2006 18:41 schrieb Bill Campbell:
On Mon, Mar 20, 2006, Bernhard Reiter wrote:
Am Montag, 20. März 2006 13:32 schrieb Bernhard Reiter:
Using OpenPKG 2.5
b) postfix
/kolab/sbin/postfix start
failed, because of an old master.pid (without process).
The message
Am Montag, 20. März 2006 18:52 schrieb Bernhard Reiter:
Am Montag, 20. März 2006 18:41 schrieb Bill Campbell:
On Mon, Mar 20, 2006, Bernhard Reiter wrote:
Am Montag, 20. März 2006 13:32 schrieb Bernhard Reiter:
Using OpenPKG 2.5
b) postfix
/kolab/sbin/postfix start
failed
Taking Doug Henry's suggestion I rebuilt my IRIX binaries using only
GCC3, making symlinks to all of these to the GCC4 names. Everything I've
built, including perl, has built with no extra configuration (except for
openssl sudo).
However - I'm having issues building postfix and I believe
Am Donnerstag, 12. Januar 2006 17:57 schrieb Bernhard Reiter:
Hi,
Nevertheless we still have the general question what
about world-readable logfiles at all...
Also my example shows that different logfiles have different dangers,
a summary log is not as important or a log from an
By default the /openpkgdir/var/postfix/log/postfix.log is word readable.
This gives users of the system
the possibility to do some sort of email traffic analysis
for email flowing through the system.
http://cvs.openpkg.org/getfile/openpkg-src/postfix/fsl.postfix?v=1.6
has
file(
path
Am Mittwoch, 11. Januar 2006 15:34 schrieb Bernhard Reiter:
By default the /openpkgdir/var/postfix/log/postfix.log is word readable.
This gives users of the system
the possibility to do some sort of email traffic analysis
for email flowing through the system.
http://cvs.openpkg.org/getfile
On Wed, Jan 11, 2006, Bernhard Reiter wrote:
Am Mittwoch, 11. Januar 2006 15:34 schrieb Bernhard Reiter:
By default the /openpkgdir/var/postfix/log/postfix.log is word readable.
This gives users of the system
the possibility to do some sort of email traffic analysis
for email flowing
On Wed, Jan 11, 2006, Ralf S. Engelschall wrote:
OTOH this is a general issue and not really Postfix related. So we
should raise the general question whether logfiles in OpenPKG should be
world-readable or not? What are the opinions?
If we restrict the setting to non-world-readable I would
Running Postfix 2.2.5 but the same errors are happening on the
OpenPKG-Current version:
After successfully building Postfix (used openpkg build as well as
openpkg rpm --rebuild) I'm getting these errors when sending mail,
either local or forwarded:
Dec 30 16:20:16 bravery warning postfix
I installed Postfix (latest from OpenPKG 2.4 updates) on a HPUX 11.00
box and copied over the main.cf from a working RHEL 3.0 machine. I'm
running into problems creating any of the .db files required to get
things started - aliases.db, access.db, virtual.db. For some reason
postmap thinks I'm
Doug Summers wrote:
I installed Postfix (latest from OpenPKG 2.4 updates) on a HPUX 11.00
box and copied over the main.cf from a working RHEL 3.0 machine. I'm
running into problems creating any of the .db files required to get
things started - aliases.db, access.db, virtual.db. For some reason
Simon J Mudd wrote:
Simon J Mudd [EMAIL PROTECTED] writes:
[snip]
OpenPKG
[EMAIL PROTECTED]:/openpkg/RPM/PKG/openpkg/bin/openpkg rpm -qa
openpkg-20050613-20050613
gcc-3.4.4-20050707.TEST_FOR_AIX
^^^
fsl-1.6.0-2.4.0
db-4.3.28.0-2.4.0
Hi,
I just installed postfix-2.2.1-20050315 and noticed that some paths in
the default configuration are not set to appropriate OpenPKG values.
Namely:
mail_spool_directory = /var/mail
mailq_path = /usr/bin/mailq
manpage_directory = /usr/local/man
newaliases_path = /usr/bin/newaliases
just go to
syslog.
I tried configuring /openpkg/etc/fsl/fsl.postfix as follows but this did
not seem to work:
[...]
What do I need to make the logging change? Stop all processes.
[...]
Yes, completely stopping and restarting Postfix is definitely required.
ok. As this does
not seem to work:
ident (postfix/.+)/.+ q{
prefix(
prefix=%b %d %H:%M:%S %N %L $1[%P]:
)
- {
debug: syslog(
facility=mail,
ident=postfix,
remotehost=127.0.0.1,
remoteport=514
I compiled,configured and started OpenPKG postfix with aparently no errors, but
I Can't get positive connection nor any error.
When I : telnet localhost smtp I got:
[EMAIL PROTECTED] log]# telnet localhost smtp
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
but no, 220
On Tue, Aug 17, 2004, Alexander Belck wrote:
I compiled,configured and started OpenPKG postfix with aparently no errors, but
I Can't get positive connection nor any error.
When I : telnet localhost smtp I got:
[EMAIL PROTECTED] log]# telnet localhost smtp
Trying 127.0.0.1...
Connected
I found a reference in main.cf to a unexisting file. After correcting that I now
got a 220 respons, but
after entering the rcpt to: [EMAIL PROTECTED]
the connection is aborted and I found in log:
Aug 17 19:55:00 arara.spsul.net critical postfix/smtpd[3900]: fatal: net/mask
pattern 200.232.113.0
I found the wrong reference. Still some problems, but I'll try postfix chanell
as I thing they aren't related to OpenPKG yet.
Thanks,
Alex
Citando [EMAIL PROTECTED]:
I found a reference in main.cf to a unexisting file. After correcting that I
now
got a 220 respons, but
after entering
On Tue, Jul 27, 2004, Alexander Belck wrote:
Sorry to resend, but I still can't upgrade postfix to rel 2.1 due to
whoson.patch, and don't know how to proceed
When issuing command:
/opkg/bin/openpkg rpm --define 'with_fdsetsize yes' --define 'with_ldap yes'
--define 'with_mysql yes
On Sun, Jul 25, 2004, Bill Campbell wrote:
On Sun, Jul 25, 2004, Alexander Belck wrote:
When compiling postfix with[_whoson yes ... patch does not apply]
I posted a replacement patch for this yesterday or the day before. I
think there's a new version of postfix in the CURRENT tree
It still not apply correctly to me. From command:
/opkg/bin/openpkg rpm --define 'with_fdsetsize yes' --define 'with_ldap yes'
--define 'with_mysql yes' --define 'with_sasl yes' --define 'with_ssl yes'
--define 'with_whoson yes' --rebuild
ftp://ftp.openpkg.org/release/2.1/UPD/postfix-2.1.4-2.1.1
When compiling postfix with:
/opkg/bin/openpkg rpm --define 'with_fdsetsize yes' --define 'with_ldap yes'
--define 'with_mysql yes' --define 'with_sasl yes' --define 'with_ssl yes'
--define 'with_whoson yes' --rebuild
ftp://ftp.openpkg.org/release/2.1/SRC/postfix-2.1.4-2.1.0.src.rpm || exit $?
I
On Sun, Jul 25, 2004, Alexander Belck wrote:
When compiling postfix with:
/opkg/bin/openpkg rpm --define 'with_fdsetsize yes' --define 'with_ldap yes'
--define 'with_mysql yes' --define 'with_sasl yes' --define 'with_ssl yes'
--define 'with_whoson yes' --rebuild
ftp://ftp.openpkg.org/release/2.1
I attempted to rebuild Postfix with more options, but received the errors
below. I have sasl, ssl, ldap, mysql installed, something else I need to
configure before compiling? The errors indicate some libs are closed?
openpkg rpm --rebuild --define 'with_fsl yes' --define 'with_ssl yes'
--define
On Tue, 16 Mar 2004, Michael Schloh von Bennewitz wrote:
I tried out pine for the first time today. It seems to connect to whatever
is listening to port 25 (postfix, netcat, etcetera), but only if its
configuration is correct.
Now I'm wondering if it's postfix, I can telnet to port 25 but I
--On Dienstag, 16. März 2004 12:36 -0600 Mike's List [EMAIL PROTECTED]
wrote:
I tried out pine for the first time today. It seems to connect to
whatever is listening to port 25 (postfix, netcat, etcetera), but only
if its configuration is correct.
Now I'm wondering if it's postfix, I can
On Tue, 16 Mar 2004, Steffen Weinreich wrote:
--On Dienstag, 16. März 2004 12:36 -0600 Mike's List [EMAIL PROTECTED]
wrote:
I tried out pine for the first time today. It seems to connect to
whatever is listening to port 25 (postfix, netcat, etcetera), but only
if its configuration
Has anyone come up with a procedure to get all of the above compiled and
working properly with each other?
Actually, SASL support in Postfix isn't 100% necessary in my case, but
even trying to build Postfix w/o SASL support is resulting in the fol-
lowing:
/ilocal/bin/cc -O2 -pipe -I/ilocal
as to whether the original questioner ever got this
working themselves..) So, if anyone has, can you post a procudure to
go about this?
On Wed, 2004-02-04 at 15:12, Martin Konold wrote:
Am Wednesday 04 February 2004 07:45 pm schrieb Christopher M. O'Malley:
Actually, SASL support in Postfix isn't 100
object code won't make it into
the postfix binary.
Thanks. I did look at the spec file to see how I might do it myself, but I
don't yet know cosmetic from critical.
Removing just the AUXLIBS fsl line did the trick and I'm not running an
logging with postfix-1.1.11-20021014.
-Andrew
Thomas,
Thanks again for your assistance.
I am still looking to log to at least one file, whether through fsl
writing to wherever it likes, fsl to my mail log, fsl to syslog or just
from postfix to syslog.
Since the last case (postfix to syslog) might be the most expeditious
while other
of fsl is no longer conditional, see
http://cvs.openpkg.org/chngview?cn=4714. However, we forgot to remove
the obsolete option from the description. Gotcha#1 - fixed and thanks
Ok. I will presume therefore that I am using fsl with postfix.
The good news for you is that fsl has an output
Ralf,
Please excuse the delay in my thanks, but I only just got around to
testing this.
Your instructions to modify postfix to use syslog..
# rpm -Uvh ftp://ftp.openpkg.org/current/SRC/postfix-1.1.7-20020404.src.rpm
# cd /cw/RPM/SRC/postfix
# vi postfix.spec
[remove line 128 (AUXLIBS
Having just migrated from locally built mostly-defaults postfix to the
OpenPKG version, I've noticed a couple of difference which I have so far
been unable to track to the source.
This may be an RPM and/or Postfix issue. Since my previous install used
mostly defaults, I expect differences
Ralf,
Now fixed with postfix-1.1.7-20020404 and higher.
Built and installed on Solaris 8. Thanks for the quick turnaround.
-Andrew-
--
| -Andrew J. Caines- 703-886-2689[EMAIL PROTECTED] |
| Unix Systems Engineer
Platform is Solaris 8 + MU 7 + recent RS including all the usual build
packages.
Building postfix-1.1.7-20020331 with rpm --rebuild as user cw fails as
follows:
8
[src/util]
/cw/bin/cc -O2 -pipe -I/cw/include -DDEF_CONFIG_DIR=\/cw/etc/postfix\ -DHAS_DB
-DHAS_PCRE -DHAS_POSIX_REGEXP
60 matches
Mail list logo
