[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 6 Oct 2003 12:00:51 +0200
From: Georg Horn <horn@...lenz-net.de>
To: popa3d-users@...ts.openwall.com, barry@...notte.ca
Subject: Re: POP before SMTP Patches not working on FreeBSD 4.6
On Sat, Oct 04, 2003 at 02:21:35PM -0300, Barry Veinotte wrote:
> I am trying to get some form of POP before SMTP working with
> sendmail and popa3d. The solution that is most attractive (after
> trying and failing with several) is here:
> http://www.koblenz-net.de/~horn/smtp_after_pop/README
>
> However, the patch will not work on my machine. I get this after
> each section:
>
> patch -p0 < popa3d-0.5.1-smtp_after_pop-1.diff
> Hmm... Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |diff -r -u popa3d-0.5.1/Makefile popa3d-0.5.1-smtp_after_pop-1/Makefile
> |--- popa3d-0.5.1/Makefile Sun Oct 28 02:10:49 2001
> |+++ popa3d-0.5.1-smtp_after_pop-1/Makefile Fri Feb 7 12:24:51 2003
> --------------------------
> File to patch:
First, i have made a new patch that works with popa3d-0.5.1 and Berkley-DB
3.3.x (3.3.11 here). The old one was made on an old SuSE-6.3 System with
sendmail 8.9.3 and Berkley-DB 1.8... You can download the new patch from:
http://www.koblenz-net.de/~horn/popa3d-0.5.1-smtp_after_pop-2.diff
Then you may run the patch program while you are in the directory containing
the popa3d-0.5.1 subdir:
# ls -1d pop*
popa3d-0.5.1/
popa3d-0.5.1-smtp_after_pop-2.diff
# patch -p0 < popa3d-0.5.1-smtp_after_pop-2.diff
patching file popa3d-0.5.1/Makefile
patching file popa3d-0.5.1/params.h
patching file popa3d-0.5.1/pop_root.c
patching file popa3d-0.5.1/standalone.c
patching file popa3d-0.5.1/startup.c
This one works fine here on a slackware 9.0 system with sendmail 8.12.10
> Would also love to hear what the easiest implimentation is that works.
Mine, of course. ;-)))
Bye,
Georg
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
