01031149> Thank you for the URL to your maildrop binary. Unfortunately, I'm a
01031149> newbie to Unix, and I don't know how to use RPM -- heck I don't even know
01031149> what it means and what it does. My only exposure to Unix so far has been
01031149> 3 months on FreeBSD, and 2 weeks on Cygwin. Soooo, when using RPM, do I
01031149> need to compile anything? I installed a minimal Cygwin, so I don't have
01031149> gcc or Perl -- is that a problem? Thanks for your patience and
01031149> understanding! Regards....
OK. First, you should install gcc, make, binutils and other
development tools. You must install gdbm too because maildrop use
this.
Then, get maildrop's source tarball from
http://www.flounder.net/~mrsam/maildrop/ (I compiled version 1.2.2.).
I attach my *dirty* patch for maildrop to this email.
Extract the tarball, and apply this patch to sources.
How to build:
$ tar zxvf maildrop-1.2.2.tar.gz
$ cd maildrop-1.2.2
$ patch -p1 < maildrop-1.2.2-cygwin.patch
$ ./configure --with-devel --enable-userdb --enable-maildirquota \
--enable-syslog=1 \
--enable-trusted-users='root mail daemon postmaster qmaild mmdf' \
--enable-restrict-trusted=0
$ make
$ make install-strip
Or, you can get rpm-3.0.6 binary and maildrop's rpm binary package
from my page.and extract this tarball at root directory. This tarball
include a command named 'rpm2cpio'. You can install maildrop's rpm
package by following at root directory:
rpm2cpio maildrop-1.2.2-2.i686-cygwin.rpm | cpio -idv
Sorry my poor English.
Good luck!
--
Rue. SATOH
--- maildrop-1.2.2/maildrop/funcs.C.orig Thu Dec 14 17:52:10 2000
+++ maildrop-1.2.2/maildrop/funcs.C Thu Dec 14 17:52:57 2000
@@ -95,6 +95,7 @@
void setprocgroup()
{
+#ifndef __CYGWIN__
#if HAS_SETPGRP
(void)setpgrp();
@@ -103,6 +104,7 @@
#if HAS_SETPGID
(void)setpgid(0,0);
procgroup_set=1;
+#endif
#endif
#endif
}
--- maildrop-1.2.2/maildrop/sysexits.h.orig Thu Dec 14 19:20:20 2000
+++ maildrop-1.2.2/maildrop/sysexits.h Thu Dec 14 17:55:42 2000
@@ -0,0 +1,118 @@
+/*
+ * Copyright (c) 1987, 1993
+ * The Regents of the University of California. All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ * notice, this list of conditions and the following disclaimer in the
+ * documentation and/or other materials provided with the distribution.
+ * 3. All advertising materials mentioning features or use of this software
+ * must display the following acknowledgement:
+ * This product includes software developed by the University of
+ * California, Berkeley and its contributors.
+ * 4. Neither the name of the University nor the names of its contributors
+ * may be used to endorse or promote products derived from this software
+ * without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ *
+ * @(#)sysexits.h 8.1 (Berkeley) 6/2/93
+ */
+
+#ifndef _SYSEXITS_H_
+#define _SYSEXITS_H_
+
+/*
+ * SYSEXITS.H -- Exit status codes for system programs.
+ *
+ * This include file attempts to categorize possible error
+ * exit statuses for system programs, notably delivermail
+ * and the Berkeley network.
+ *
+ * Error numbers begin at EX__BASE to reduce the possibility of
+ * clashing with other exit statuses that random programs may
+ * already return. The meaning of the codes is approximately
+ * as follows:
+ *
+ * EX_USAGE -- The command was used incorrectly, e.g., with
+ * the wrong number of arguments, a bad flag, a bad
+ * syntax in a parameter, or whatever.
+ * EX_DATAERR -- The input data was incorrect in some way.
+ * This should only be used for user's data & not
+ * system files.
+ * EX_NOINPUT -- An input file (not a system file) did not
+ * exist or was not readable. This could also include
+ * errors like "No message" to a mailer (if it cared
+ * to catch it).
+ * EX_NOUSER -- The user specified did not exist. This might
+ * be used for mail addresses or remote logins.
+ * EX_NOHOST -- The host specified did not exist. This is used
+ * in mail addresses or network requests.
+ * EX_UNAVAILABLE -- A service is unavailable. This can occur
+ * if a support program or file does not exist. This
+ * can also be used as a catchall message when something
+ * you wanted to do doesn't work, but you don't know
+ * why.
+ * EX_SOFTWARE -- An internal software error has been detected.
+ * This should be limited to non-operating system related
+ * errors as possible.
+ * EX_OSERR -- An operating system error has been detected.
+ * This is intended to be used for such things as "cannot
+ * fork", "cannot create pipe", or the like. It includes
+ * things like getuid returning a user that does not
+ * exist in the passwd file.
+ * EX_OSFILE -- Some system file (e.g., /etc/passwd, /etc/utmp,
+ * etc.) does not exist, cannot be opened, or has some
+ * sort of error (e.g., syntax error).
+ * EX_CANTCREAT -- A (user specified) output file cannot be
+ * created.
+ * EX_IOERR -- An error occurred while doing I/O on some file.
+ * EX_TEMPFAIL -- temporary failure, indicating something that
+ * is not really an error. In sendmail, this means
+ * that a mailer (e.g.) could not create a connection,
+ * and the request should be reattempted later.
+ * EX_PROTOCOL -- the remote system returned something that
+ * was "not possible" during a protocol exchange.
+ * EX_NOPERM -- You did not have sufficient permission to
+ * perform the operation. This is not intended for
+ * file system problems, which should use NOINPUT or
+ * CANTCREAT, but rather for higher level permissions.
+ */
+
+#define EX_OK 0 /* successful termination */
+
+#define EX__BASE 64 /* base value for error messages */
+
+#define EX_USAGE 64 /* command line usage error */
+#define EX_DATAERR 65 /* data format error */
+#define EX_NOINPUT 66 /* cannot open input */
+#define EX_NOUSER 67 /* addressee unknown */
+#define EX_NOHOST 68 /* host name unknown */
+#define EX_UNAVAILABLE 69 /* service unavailable */
+#define EX_SOFTWARE 70 /* internal software error */
+#define EX_OSERR 71 /* system error (e.g., can't fork) */
+#define EX_OSFILE 72 /* critical OS file missing */
+#define EX_CANTCREAT 73 /* can't create (user) output file */
+#define EX_IOERR 74 /* input/output error */
+#define EX_TEMPFAIL 75 /* temp failure; user is invited to retry */
+#define EX_PROTOCOL 76 /* remote error in protocol */
+#define EX_NOPERM 77 /* permission denied */
+#define EX_CONFIG 78 /* configuration error */
+
+#define EX__MAX 78 /* maximum listed value */
+
+#endif /* !_SYSEXITS_H_ */
--- maildrop-1.2.2/Makefile.in.orig Thu Dec 14 20:26:17 2000
+++ maildrop-1.2.2/Makefile.in Thu Dec 14 20:27:23 2000
@@ -798,8 +798,8 @@
$(INSTALL_PROGRAM) maildir/maildirmake $(DESTDIR)$(bindir)/$$f
$(INSTALL_PROGRAM) rfc2045/reformime $(DESTDIR)$(bindir)/reformime
$(INSTALL_PROGRAM) rfc2045/makemime $(DESTDIR)$(bindir)/makemime
- . maildrop/uidgid ; test -z "$$gid" && exit 0; test -w /etc || exit 0; cd
$(DESTDIR)$(bindir) && chgrp $$gid maildrop dotlock
- . maildrop/uidgid ; test -z "$$uid" && exit 0; test -w /etc || exit 0; cd
$(DESTDIR)$(bindir) && chown $$uid maildrop dotlock && chmod 6755 maildrop dotlock
+ #. maildrop/uidgid ; test -z "$$gid" && exit 0; test -w /etc || exit 0; cd
+$(DESTDIR)$(bindir) && chgrp $$gid maildrop dotlock
+ #. maildrop/uidgid ; test -z "$$uid" && exit 0; test -w /etc || exit 0; cd
+$(DESTDIR)$(bindir) && chown $$uid maildrop dotlock && chmod 6755 maildrop dotlock
uninstall-maildrop:
for f in maildrop maildirmake reformail dotlock makemime reformime ; do \
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
