Apology for multiple PR (112106, 112107, 112108) submissions...
Hi, I ported Wcalc to FreeBSD, and wanted to get it added to the ports section. Hence, I did a web-submit of the PR. Some problem occurred, and I never got a response back from the PR web-submit system. I then queried the database to see if the PR was submitted, but nothing turned up. Assuming that the PR was not submitted, I did a re-submit again, and again - which was basically a mistake on my part. Sincere apologies for this - I should have been more patient. The multiple PRs' are: 112106, 112107, and 112108. Henceforth, I will be more careful while making submissions. Thanks! -Amarendra ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apology for multiple PR (112106, 112107, 112108) submissions...
On Wed, Apr 25, 2007 at 11:35:16AM +0530, Amarendra Godbole wrote: I then queried the database to see if the PR was submitted, but nothing turned up. It takes 5-10 minutes for the automated processes all to run to process the latest PRs before they will show up on the web page. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lynx -vulnerabilities- is this permanent?
Simon L. Nielsen wrote: On 2007.04.19 19:01:39 +0800, Foxfair Hu wrote: vuxml - security-team's baby. Cc added. The problem is caused by interesting version numbering in the www/lynx-current port which now conflicts with www/lynx: [EMAIL PROTECTED]:lynx-current] make -V PKGNAME lynx-2.8.7d4 Basically the problem was fixed in lynx-current (I assume, I haven't checked) 2.8.6d14 which really should have been 2.8.6.d14 to avoid problems like this. [EMAIL PROTECTED]:~] pkg_version -t 2.8.6d14 2.8.6_4 [EMAIL PROTECTED]:~] pkg_version -t 2.8.6.d14 2.8.6_4 I will try to have a look at how to work around this tonight, but I don't know if I will get to it today. [Cut off individuals Cc] Can we remove 2nd and 4th entry? Look at the version info on lynx site, I don't think current statement is a correct one: lynx 2.8.6* 2.8.6d14 ja-lynx 2.8.6* 2.8.6d14 Diff as below: - cvs diff: Diffing . Index: vuln.xml === RCS file: /home/pcvs/ports/security/vuxml/vuln.xml,v retrieving revision 1.1317 diff -u -d -b -w -r1.1317 vuln.xml --- vuln.xml23 Apr 2007 14:12:10 - 1.1317 +++ vuln.xml25 Apr 2007 04:01:21 - @@ -11487,7 +11487,6 @@ namelynx/name nameja-lynx/name rangelt2.8.5_1/lt/range - rangegt2.8.6*/gtlt2.8.6d14/lt/range /package package namelynx-ssl/name @@ -11515,7 +11514,7 @@ /references dates discovery2005-10-17/discovery entry2005-10-30/entry - modified2006-10-05/modified + modified2007-04-25/modified /dates /vuln ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/111811: [NEW PORT] net/ruby-rrdtool: A Ruby interface to rrdtool
Cheng-Lung Sung wrote:
Hi Jonathan,
Is it possible to put ${SETENV} ${GEM_ENV} before ${RUBYGEMBIN}?
Since Konstantin's new port required passing
MAKEFLAGS=CPPFLAGS=-I/${LOCALBASE}/include
to the gem build/install environment.
Looks OK to me, I will test it today and report back.
Jonathan
--
Jonathan Weiss
http://blog.innerewut.de
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grace 5.1.21 port
Hello, Great news! Thanks a lot for your effort! Where may I learn how to become a port maintainer? I've seen the Porter's Handbook, but I am not sure I will have enough time to read all this handbook in order to maintain the grace port. There some short handbook to know the basic skills to become a maintainer? cheers, Xavier On Tue, 24 Apr 2007 22:40:15 +0200 Thierry Thomas [EMAIL PROTECTED] wrote: Le Mar 17 avr 07 à 13:38:03 +0200, Xavier Otazu [EMAIL PROTECTED] écrivait : Hello: ¡Hello! I do not know if this e-mail account is a mail-list or a personal e-mail. Anyway, I woul like to say to the maintainer of this port to upgrade it to the newest recent version, i.e. 5.1.21. Just upgraded. Note: there is currently no maintainer for this port; if you are interested, you could grab its maintainership. Regards, -- Th. Thomas. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: x11-toolkits/gtk20
On Tue, Apr 24, 2007 at 10:33:55PM -0400, Mike Jakubik wrote: Michael Johnson wrote: On Apr 24, 2007, at 7:47 PM, Mike Jakubik wrote: gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.10.11/gdk' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.10.11' gmake: *** [all] Error 2 Some how you compiled cairo with WITHOUT_X11. Recompile graphics/cairo with out WITHOUT_X11 defined. Thats odd, because i never specified this option. This was part of a xfce4 compile. Going in to cairo's port manually, and only typing in make still results in it using WITHOUT_X11. I had to manually edit the Makefile and take that IF out for it to compile properly. Is it possible you have this set in make.conf? -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: x11-toolkits/gtk20
On Apr 24, 2007, at 10:33 PM, Mike Jakubik wrote: Michael Johnson wrote: On Apr 24, 2007, at 7:47 PM, Mike Jakubik wrote: gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/ gtk+-2.10.11/gdk' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/ gtk+-2.10.11' gmake: *** [all] Error 2 Some how you compiled cairo with WITHOUT_X11. Recompile graphics/ cairo with out WITHOUT_X11 defined. Thats odd, because i never specified this option. This was part of a xfce4 compile. Going in to cairo's port manually, and only typing in make still results in it using WITHOUT_X11. I had to manually edit the Makefile and take that IF out for it to compile properly It's a hidden knob in cairo we don't advertise because it causes problems like this, but we had had enough requests for no-x11 support in cairo to add this knob. run 'make -V WITHOUT_X11' in graphics/cairo and see what the output is Michael PGP.sig Description: This is a digitally signed message part
Building a mail application.. some advice appreciated
Hi I am looking for some general advice and guidance for selecting software components to fulfill a proof of concept test. I need a mail application with features requiring that incoming mails, which should comply with a predetermined format, be initially examined for compliance with that format. Each sender (read user) has to be uniquely identified in the database system and a log kept of every mail received. Sender verification requirements are high and, among other things, the output from attachment processing must provide an input to the verification system. Mails that pass verification requirements are to be initially processed by the receiving server and the results of verification transferred to a mysql database. Subsequently data has to be extracted from the email, processed and the results stored in a mysql database. Processing includes the use of scripts to generate email responses and other functions. Attachments have to be extracted and passed for processing and results stored in a mysql db. Mails that do not comply with the verification requirements need to be passed to another server for logging and processing. The system has to be scaleable. I realise I have not given a lot of detailed information but here is the rub I need to build, as quickly as possible, a proof of concept, using readily available software components. The OS is freebsd (currently 6.1) running postfix. What components would you choose for this exercise? Be able to build quickly and easily is the priority for this stage and low server demand would not be some important at this time. Thanks in advance for any input you can give David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
gmake compile error
Is this a problem with the gmake port (a dependency of qt4) or should I
go ahead and submit the bug report to GNU gcc?
...
cd doc ; make install
./../etc/mkinstalldirs /usr/local/man/man1 /usr/local/info
install -o root -g wheel -m 444 ./screen.1 /usr/local/man/man1/screen.1
make screen.info
makeinfo --no-split ./screen.texinfo -o screen.info
./screen.texinfo:2891: warning: Accent command `@'' must not be followed
by whitespace.
if test -f screen.info; then d=.; else d=.; fi; if test -f
$d/screen.info; then for f in $d/screen.info*; do install -o root -g
wheel -m 444 $f /usr/local/info;done; if /bin/sh -c 'install-info
--version' /dev/null 21; then install-info --info- -DQT_NO_THREAD
-DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQMAKE_OPENSOURCE_EDITION -c
/usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake/generators/mac/pbuilder_pbx.cpp
c++: Internal error: Killed: 9 (program cc1plus)
Please submit a full bug report.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1
Stop in /usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake.
*** Error code 1
Stop in /usr/ports/devel/qmake4.
{standard input}: Assembler messages:
{standard input}:26701: Warning: end of file not at end of a line;
newline inserted
{standard input}:27666: Error: unknown pseudo-op: `.l1'
*** Error code 1
FreeBSD zeus.foster.dmz 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12
10:40:27 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
--
Said one park ranger, 'There is considerable overlap between the
intelligence of the smartest bears and the dumbest tourists.'
Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building a mail application.. some advice appreciated
--On Wednesday, April 25, 2007 06:43:34 -0700 David Southwell [EMAIL PROTECTED] wrote: Hi I am looking for some general advice and guidance for selecting software components to fulfill a proof of concept test. I need a mail application with features requiring that incoming mails, which should comply with a predetermined format, be initially examined for compliance with that format. You're going to have to be a bit more specific. Are you referring to the transport information? Or the data? Or both? It makes a big difference how you go about inspecting the email. If you're referring to transport, then use mail/postfix-policyd-weight. If you're referring to data, then spamassassin or another content-inspector would work. You just need to modify the rules of either (or both) to suit your test. Each sender (read user) has to be uniquely identified in the database system and a log kept of every mail received. Sender verification requirements are high and, among other things, the output from attachment processing must provide an input to the verification system. Mails that pass verification requirements are to be initially processed by the receiving server and the results of verification transferred to a mysql database. Look at this postfix doc: ADDRESS_VERIFICATION_README Subsequently data has to be extracted from the email, processed and the results stored in a mysql database. Processing includes the use of scripts to generate email responses and other functions. Postfix delivers to mysql. Then you script whatever you want using db queries. Attachments have to be extracted and passed for processing and results stored in a mysql db. amavisd Mails that do not comply with the verification requirements need to be passed to another server for logging and processing. The system has to be scaleable. To what? Anything is scalable if you have enough boxes and storage. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Re: qmake compile error
mark foster [EMAIL PROTECTED] writes:
Is this a problem with the gmake port (a dependency of qt4) or should I
go ahead and submit the bug report to GNU gcc?
qmake, not gmake; I corrected the subject line
...
cd doc ; make install
./../etc/mkinstalldirs /usr/local/man/man1 /usr/local/info
install -o root -g wheel -m 444 ./screen.1 /usr/local/man/man1/screen.1
make screen.info
makeinfo --no-split ./screen.texinfo -o screen.info
./screen.texinfo:2891: warning: Accent command `@'' must not be followed
by whitespace.
if test -f screen.info; then d=.; else d=.; fi; if test -f
$d/screen.info; then for f in $d/screen.info*; do install -o root -g
wheel -m 444 $f /usr/local/info;done; if /bin/sh -c 'install-info
--version' /dev/null 21; then install-info --info- -DQT_NO_THREAD
-DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQMAKE_OPENSOURCE_EDITION -c
/usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake/generators/mac/pbuilder_pbx.cpp
c++: Internal error: Killed: 9 (program cc1plus)
Please submit a full bug report.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1
Stop in /usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake.
*** Error code 1
Stop in /usr/ports/devel/qmake4.
{standard input}: Assembler messages:
{standard input}:26701: Warning: end of file not at end of a line;
newline inserted
{standard input}:27666: Error: unknown pseudo-op: `.l1'
*** Error code 1
This trace doesn't make sense to me. Are you using parallel building
of some sort? If so, turn it off; even though it's probably not
causing the problem, it's obscuring debug information.
FreeBSD zeus.foster.dmz 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12
10:40:27 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
Are your ports the same age?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Making a local branch of the ports tree
I know I've seen this discussed a dozen times, but google is letting me down right now. Basically, I want to create a private branch of the ports tree for scripts and other stuff that isn't suitable to submit back to the main ports tree, and use portupgrade and other ports tools to maintain this across a bunch of systems that mount their ports tree via NFS. My thought is to make /usr/ports/private (or similar) and teach cvsup not to blow it away. Then I just need to make sure that portupgrade and other tools see it. Does anyone have a HOWTO or list of steps to get this going? I know this has been discussed before but I can't find any reference to it now. -- Bill Moran http://www.potentialtech.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printable Porters' Handbook ghostscript-gpl-nox11 problem
On Apr 23, 2007, at 3:47 PM, David J Brooks wrote: You can find in several printable formats here: ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/porters- handbook Thank you. That is exactly what I was looking for. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making a local branch of the ports tree
On Apr 25, 2007, at 1:22 PM, Bill Moran wrote:
My thought is to make /usr/ports/private (or similar) and teach cvsup
not to blow it away. Then I just need to make sure that portupgrade
and other tools see it.
Does anyone have a HOWTO or list of steps to get this going? I know
this has been discussed before but I can't find any reference to it
now.
I use /usr/port/local and name all the ports kci-XXX for whatever
port we have. mostly these are pseudo ports which pull in all the
dependencies for our various server needs. (I'll probably post this
to my website sometime...)
Step 1: mkdir /usr/ports/local
Step 2: create the following /usr/ports/Makefile.local
-- cut here --
# local Makefile additions for top-level ports to add our local
category.
SUBDIR += local
-- cut here --
So now the ports infrastructure knows about that directory.
Step 3: Inside /usr/ports/local, create a Makefile something like this:
--cut here--
COMMENT = KCI local ports
SUBDIR += kci-base
SUBDIR += kci-monitor
SUBDIR += kci-searchserver
.include bsd.port.subdir.mk
--cut here--
Where every subdir of /usr/ports/local is listed here so as to inform
the ports infrastructure of your local ports. You must list every
port you want to be visible in your INDEX file which we will update
below.
Here is my example /usr/ports/local/kci-base/Makefile which installs
the bare minimum essentials we need on every server:
--cut here--
PORTNAME= kci-base
PORTVERSION=25
PORTREVISION= 0
CATEGORIES= local
VALID_CATEGORIES=local
MASTER_SITES= # empty
DISTFILES= # none
EXTRACT_ONLY= # empty
MAINTAINER= [EMAIL PROTECTED]
COMMENT=Base applications needed on all KCI servers
RUN_DEPENDS=bash:${PORTSDIR}/shells/bash \
rsync:${PORTSDIR}/net/rsync \
jove:${PORTSDIR}/editors/jove \
nano:${PORTSDIR}/editors/nano \
gmake:${PORTSDIR}/devel/gmake \
portupgrade:${PORTSDIR}/ports-mgmt/portupgrade \
portaudit:${PORTSDIR}/ports-mgmt/portaudit
# Don't let stupid programs ask for configuration.
#BATCH= YES
NO_WRKSUBDIR= YES
NO_BUILD= YES
.if make(package)
DEPENDS_TARGET=package
.endif # .if make(package)
# do nothing here, but can't use NO_INSTALL since it won't make the
depends
do-install:
.include bsd.port.mk
--cut here--
The KEY thing is to set the VALID_CATEGORIES to the name of the
local base ports category, in my case local. Other than that, it
can be just like any other port normally part of the ports tree, and
needs the necessary support files every port needs. I haven't been
able to work out how to do this globally in the /usr/ports/
Makefile.local. If you do, please share.
Now, the only step left is to get your local ports into the INDEX.
Here is where we use some trickery... I observed that the make_index
script from ports uses make describe output and cross-references
stuff to generate INDEX. However, the INDEX file itself is nearly
the same format... so if we feed make describe from our local
subtree and concatenate it with the existing INDEX and ignore all
warnings about make_index not finding port names (since they were
already substituted in the INDEX file...) we generate the output we
want. The following script, localportindex, does this:
--cut here--
#!/bin/sh
# hack to append our local ports to the /usr/ports/INDEX-6 file to
let the
# portupgrade and portinstall utilities see them.
# Run this after normal update of INDEX file, such as portsnap or
fetchindex
# $Id: localportindex 480 2006-06-16 15:14:38Z khera $
# for FreeBSD 6.x
PORTSBASE=/usr/ports
PORTSDIRNAME=`cd $PORTSBASE ; /bin/pwd` # for fixingup NFS/symlink
pathnames
INDEX=${PORTSBASE}/INDEX-6
LOCAL=${PORTSBASE}/local
tmpfile=`/usr/bin/mktemp -t index` || exit 1
# make_index script complains a ton about using the INDEX file rather
than the
# raw describe output so we just toss the errors. this is probably
a bad
# thing to do, but nobody will die because of it...
(cd $LOCAL; make describe | sed -e [EMAIL PROTECTED]@[EMAIL PROTECTED];
cat ${INDEX}) | \
perl ${PORTSBASE}/Tools/make_index 2 /dev/null | grep ^kci $tmpfile
echo Local ports appended to $INDEX file:
cat $tmpfile
cat $tmpfile ${INDEX}
rm -f $tmpfile
--cut here--
Note that I use the fact all my ports start with kci- to pull them
from the newly generated INDEX file and append that data to the
actual INDEX file. This step takes just seconds as opposed to tens
of minutes (or longer) to regenerate the INDEX from scratch.
All of the above works 100% well with portsnap and cvsup. I don't
recall having to teach either how to ignore the local subdir. If you
use cvsup, be sure to use some means to have a virgin INDEX file
before re-running the above index script, like using make fetchindex.
Here is my srcupdate script which updates the source + ports on my
Re: Making a local branch of the ports tree
Bill Moran [EMAIL PROTECTED] writes: I know I've seen this discussed a dozen times, but google is letting me down right now. It's not heavily documented, but most people who need it seem to be able to figure it out pretty easily. The trick for a full-net search might be using bsd.local.mk. Basically, I want to create a private branch of the ports tree for scripts and other stuff that isn't suitable to submit back to the main ports tree, and use portupgrade and other ports tools to maintain this across a bunch of systems that mount their ports tree via NFS. Right. Plenty of people do that. My thought is to make /usr/ports/private (or similar) and teach cvsup not to blow it away. Then I just need to make sure that portupgrade and other tools see it. Exactly right. cvsup won't blow anything away unless it put it there in the first place, so that's not an issue for your local tree. For the tools to see it, you just need the directory included in the SUBDIR variable in the main ports Makefile, and everything else will follow. Does anyone have a HOWTO or list of steps to get this going? I know this has been discussed before but I can't find any reference to it now. Just put your SUBDIR += private line into bsd.local.mk, and you should be off to the races. That file *is* in the cvs tree, so cvsup will normally smash it unless I'm overlooking something. Using an exclude file seems like the easiest way to fix that, although separate version control might work better in the long run (there are plenty of other options, too; I don't know which is the normal choice). Be well. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qmake compile error
Lowell Gilbert wrote:
qmake, not gmake; I corrected the subject line
Er, ah, yes thanks.
...
cd doc ; make install
./../etc/mkinstalldirs /usr/local/man/man1 /usr/local/info
install -o root -g wheel -m 444 ./screen.1 /usr/local/man/man1/screen.1
make screen.info
makeinfo --no-split ./screen.texinfo -o screen.info
./screen.texinfo:2891: warning: Accent command `@'' must not be followed
by whitespace.
if test -f screen.info; then d=.; else d=.; fi; if test -f
$d/screen.info; then for f in $d/screen.info*; do install -o root -g
wheel -m 444 $f /usr/local/info;done; if /bin/sh -c 'install-info
--version' /dev/null 21; then install-info --info- -DQT_NO_THREAD
-DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQMAKE_OPENSOURCE_EDITION -c
/usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake/generators/mac/pbuilder_pbx.cpp
c++: Internal error: Killed: 9 (program cc1plus)
Please submit a full bug report.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1
Stop in /usr/ports/devel/qmake4/work/qt-x11-opensource-src-4.2.3/qmake.
*** Error code 1
Stop in /usr/ports/devel/qmake4.
{standard input}: Assembler messages:
{standard input}:26701: Warning: end of file not at end of a line;
newline inserted
{standard input}:27666: Error: unknown pseudo-op: `.l1'
*** Error code 1
This trace doesn't make sense to me. Are you using parallel building
of some sort? If so, turn it off; even though it's probably not
causing the problem, it's obscuring debug information.
Not that I'm aware of. The only anomaly I can think of on this host is
that it's running as a guest under vmware-server.
FreeBSD zeus.foster.dmz 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12
10:40:27 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
Are your ports the same age?
Yes, I just recently did a cvsup.
What else can I try? pkg_add -r qmake4 would only sidestep the problem.
--
Said one park ranger, 'There is considerable overlap between the
intelligence of the smartest bears and the dumbest tourists.'
Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building a mail application.. some advice appreciated
On Apr 25, 2007, at 8:43 AM, David Southwell wrote: Hi I am looking for some general advice and guidance for selecting software components to fulfill a proof of concept test. I need a mail application with features requiring that incoming mails, which should comply with a predetermined format, be initially examined for compliance with that format Presumably you are talking about the the format of the body of the message. Or will the formated information all be in the headers? The tools you use will depend on that (and other things). Each sender (read user) has to be uniquely identified in the database system and a log kept of every mail received. Sender verification requirements are high and, among other things, the output from attachment processing must provide an input to the verification system. In order to help understand what you need it is important to break up the word verification and by sender. In mail transport jargon sender means the address passed as the argument (an email address) to the MAIL FROM directive during SMTP. Do you mean that or do you mean something else by sender. By verification, do you just want to know whether it is a valid sender or do you want to authenticate the sender? That is, do you want to have confidence that the sender is who they say they are? When dealing with things like verification people like to break down the muddle into distinct tasks. One is identification. For example, a username usually works to *identify* a particular user, so we know what user we are talking about. Authentication is how we know that the person (or entity) wanting to use that identify really is who they say that are. For example knowing a password is used to authenticate. (Then there is authorization) which I will leave aside for now). For email there already are two good systems for authentication. PGP and S/MIME. Most toolkits for dealing with mail usually come with easy support for either of those. For example, along with the many perl modules that exist for dealing with mail, there are modules for processing PGP or S/MIME signed messages. Mails that pass verification requirements are to be initially processed by the receiving server and the results of verification transferred to a mysql database. Again, that depends on what the processing actually will be. You will not do this within the MTA, but will pass (usually through an alias to a pipe, just like in mailman) the message to some program or script. Whether it's written in perl, python, awk etc is up to you, though there will already be nice packages in perl and python (and lots of other choices) for doing this kind of thing. You will want a system that has nice integration with MySQL. Again, all of the popular scripting languages do. Attachments have to be extracted and passed for processing and results stored in a mysql db. Again, you will want to use some system that has modules or libraries for dealing with email attachments. Perl is what I'm most familiar with, but all the other ones will have such libraries/modules as well. Mails that do not comply with the verification requirements need to be passed to another server for logging and processing. When you say another server do you mean some other service to deal with these, some other mail server or some other host? The system has to be scaleable. I realise I have not given a lot of detailed information but here is the rub I need to build, as quickly as possible, a proof of concept, using readily available software components. In a sense, any mailing list management system (that can use a mysql backend) already does what specify. So do many other things that process mail (like customer relations systems, or bug/ticket reporting systems). The OS is freebsd (currently 6.1) running postfix. What components would you choose for this exercise? Be able to build quickly and easily is the priority for this stage and low server demand would not be some important at this time. I would really need to know what the problem is that you are trying to solve really is. That way, we'll have a better understanding of whether email is the right solution, whether this has already been done, what kind of authentication really is needed, etc. So tell us what you are trying to do with the system, and it will be easier to make meaningful recommendations. Cheers, -j ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building a mail application.. some advice appreciated
On Wednesday 25 April 2007 12:12:44 Jeffrey Goldberg wrote: Hi I am looking for some general advice and guidance for selecting software components to fulfill a proof of concept test. I need a mail application with features requiring that incoming mails, which should comply with a predetermined format, be initially examined for compliance with that format Presumably you are talking about the the format of the body of the message. Thanks for getting back to me subject and body needed to be checked for data content (which is in the form of command strings) and format validity plus data content checking for a number of headers. Or will the formated information all be in the headers? The tools you use will depend on that (and other things). Each sender (read user) has to be uniquely identified in the database system and a log kept of every mail received. Sender verification requirements are high and, among other things, the output from attachment processing must provide an input to the verification system. In order to help understand what you need it is important to break up the word verification and by sender. In mail transport jargon sender means the address passed as the argument (an email address) to the MAIL FROM directive during SMTP. Do you mean that or do you mean something else by sender. By verification, do you just want to know whether it is a valid sender or do you want to authenticate the sender? Both. That is, do you want to have confidence that the sender is who they say they are? When dealing with things like verification people like to break down the muddle into distinct tasks. One is identification. For example, a username usually works to *identify* a particular user, so we know what user we are talking about. Authentication is how we know that the person (or entity) wanting to use that identify really is who they say that are. For example knowing a password is used to authenticate. (Then there is authorization) which I will leave aside for now). Iddentification and authentication processess are assisted by the email containing attachments which are small one time use files that should only be in the possession of a specific valid user. For email there already are two good systems for authentication. PGP and S/MIME. Most toolkits for dealing with mail usually come with easy support for either of those. For example, along with the many perl modules that exist for dealing with mail, there are modules for processing PGP or S/MIME signed messages. Mails that pass verification requirements are to be initially processed by the receiving server and the results of verification transferred to a mysql database. Again, that depends on what the processing actually will be. You will not do this within the MTA, but will pass (usually through an alias to a pipe, just like in mailman) the message to some program or script. Whether it's written in perl, python, awk etc is up to you, though there will already be nice packages in perl and python (and lots of other choices) for doing this kind of thing. You will want a system that has nice integration with MySQL. Again, all of the popular scripting languages do. I am familiar with gawl/awk and php. Attachments have to be extracted and passed for processing and results stored in a mysql db. Again, you will want to use some system that has modules or libraries for dealing with email attachments. Perl is what I'm most familiar with, but all the other ones will have such libraries/modules as well. Mails that do not comply with the verification requirements need to be passed to another server for logging and processing. When you say another server do you mean some other service to deal with these, some other mail server or some other host? another mail server The system has to be scaleable. I realise I have not given a lot of detailed information but here is the rub I need to build, as quickly as possible, a proof of concept, using readily available software components. In a sense, any mailing list management system (that can use a mysql backend) already does what specify. So do many other things that process mail (like customer relations systems, or bug/ticket reporting systems). The OS is freebsd (currently 6.1) running postfix. What components would you choose for this exercise? Be able to build quickly and easily is the priority for this stage and low server demand would not be some important at this time. I would really need to know what the problem is that you are trying to solve really is. The focus of the application is around the transmission of small one time use encrypted files by identified and authenticated users attached to the emails plus the interpretation of terse formated data found in the subject and body of the email. Email is the only practical
Re: Building a mail application.. some advice appreciated
Hi, additionally to former posts, maybe have a look at /usr/ports/mail/dbmail I am not sure about your detailed needs, but maybe this will help. You can use it for storing (postfix as frontend) and retrieving (dbmail includes pop3/imap daemon) mails in a database. Most of the config, e.g. users, passwords can live in the database. With sieve filters (stored in the database too) you can filter mails (vacation, folder filter, redirect, delete, ...). The avelsieve plugin of squirrelmail can give u a nice frontend for changinge the rules per user. For more infos about dbmail have a look at http://www.dbmail.org/dokuwiki/doku.php bye, Andy ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building a mail application.. some advice appreciated
On Apr 25, 2007, at 3:37 PM, David Southwell wrote: Iddentification and authentication processess are assisted by the email containing attachments which are small one time use files that should only be in the possession of a specific valid user. Then doesn't this solve your problem? The attachment itself will serve to sufficiently identify and authenticate the sender. What more do you need? You will not do this within the MTA, but will pass (usually through an alias to a pipe, just like in mailman) the message to some program or script. Whether it's written in perl, python, awk etc is up to you, though there will already be nice packages in perl and python (and lots of other choices) for doing this kind of thing. You will want a system that has nice integration with MySQL. Again, all of the popular scripting languages do. I am familiar with gawl/awk and php. PHP then. awk doesn't have the libraries. I don't know how much there is for PHP processing mail, but I suspect that there is enough. Mails that do not comply with the verification requirements need to be passed to another server for logging and processing. When you say another server do you mean some other service to deal with these, some other mail server or some other host? another mail server Well, then from PHP (if that is what you go with) you can just pass the message off via PHP's mail submission tools. I would really need to know what the problem is that you are trying to solve really is. The focus of the application is around the transmission of small one time use encrypted files by identified and authenticated users attached to the emails plus the interpretation of terse formated data found in the subject and body of the email. As I said, the ones with those attachments should be sufficient for the authentication you need. I guess that it is the terse formated data ones that are of concern. Will those messages be generated directly be humans typing them in, or will there be some sort of program generating them? Quite simply, how much control or discretion do you have over the email clients? What sorts of tools are generating the encrypted files? Do you have any control over those tools? Email is the only practical solution. Yes, I see that from what you described in your answer to my earlier query. This might also help work around the webmail problem. S/ MIME or PGP can be made to work with most email clients, with webmail being the real stumbling block. You can simply direct anyone using a webmail system to do their stuff directly over HTTPS to your server (since those webmail users at those times are capable of having interactive web based sessions). Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: x11-toolkits/gtk20
Wesley Shields wrote: Thats odd, because i never specified this option. This was part of a xfce4 compile. Going in to cairo's port manually, and only typing in make still results in it using WITHOUT_X11. I had to manually edit the Makefile and take that IF out for it to compile properly. Is it possible you have this set in make.conf? Nope, i checked that one. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: x11-toolkits/gtk20
Michael Johnson wrote: Thats odd, because i never specified this option. This was part of a xfce4 compile. Going in to cairo's port manually, and only typing in make still results in it using WITHOUT_X11. I had to manually edit the Makefile and take that IF out for it to compile properly It's a hidden knob in cairo we don't advertise because it causes problems like this, but we had had enough requests for no-x11 support in cairo to add this knob. run 'make -V WITHOUT_X11' in graphics/cairo and see what the output is # make -V WITHOUT_X11 yes ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Is there anybody will port the ATI linux driver to FreeBSD?
Sorry, but we need to do something... i can help if u want, but tell me how. I dont like my freebsd with vesa in my laptop. I have an ATI Mobility x1400 Andrés (acr30) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: x11-toolkits/gtk20
On Apr 25, 2007, at 9:18 PM, Mike Jakubik wrote: Michael Johnson wrote: Thats odd, because i never specified this option. This was part of a xfce4 compile. Going in to cairo's port manually, and only typing in make still results in it using WITHOUT_X11. I had to manually edit the Makefile and take that IF out for it to compile properly It's a hidden knob in cairo we don't advertise because it causes problems like this, but we had had enough requests for no-x11 support in cairo to add this knob. run 'make -V WITHOUT_X11' in graphics/cairo and see what the output is # make -V WITHOUT_X11 yes its defined somewhere then. PGP.sig Description: This is a digitally signed message part
Re: Is there anybody will port the ATI linux driver to FreeBSD?
Andres Hernandez [EMAIL PROTECTED] writes: Sorry, but we need to do something... i can help if u want, but tell me how. I dont like my freebsd with vesa in my laptop. I have an ATI Mobility x1400 The ATI driver isn't open-source, so porting it isn't really an option. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
games/freebsd-games larn
Guys, sometime during the last couple of month ``larn'' got broken.
When I start playing it, everything goes well until I find an object -
potion or scroll. If I try to pick it up, I get BUS error.
Any ideas what's going on?
Also, I'm attaching patch that allows ``larn'' to correctly send an email
when the game is over.
Cheers!
--dima
*** larn/bill.c.ORIGSun Sep 19 16:16:10 2004
--- larn/bill.c Sun Sep 19 16:16:15 2004
***
*** 129,136
cp = mail;
sprintf(fname, /tmp/#%dlarnmail, getpid());
for (i = 0; i 6; i++) {
! if ((fd = open(fname, O_WRONLY | O_TRUNC | O_CREAT),
! 0660) == -1)
exit(0);
while (*cp != NULL) {
if (*cp[0] == '1') {
--- 129,136
cp = mail;
sprintf(fname, /tmp/#%dlarnmail, getpid());
for (i = 0; i 6; i++) {
! if ((fd = open(fname, O_WRONLY | O_TRUNC | O_CREAT,
! 0660)) == -1)
exit(0);
while (*cp != NULL) {
if (*cp[0] == '1') {
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
