Seeking recommendation for anti-spam software
I am running a mail server using Postfix and Dovecot. I would like to hear people's recommendation for which port to use to add server side anti-spam. The problem these days is a richness of choices, so it's hard to know port which to try. And call it a quirk of mine, but I really dislike (server) software with a large number of dependencies. That rules out Spam Assassin. But I am fairly conversant with mail and Postfix/Dovecot in general, so I don't mind any integration work. I apologize if this has been discussed before, but I just joined the list (I am already on so many FreeBSD lists already). I appreciate any insight that people can offer. Richard Coleman [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mozilla and courier-imap
Ed Budd wrote: I'm using the most recent ports for mozilla and courier-imap on an up-to-date FreeBSD-stable. Very often I will not see new messages in a folder until I restart mozilla. I was convinced it was mozilla that was broken, but I've seen similar behavior using Thunderbird on my Windows box. Now I'm not so sure. How are messages being routed to folders? If you're using some kind of server-side filtering make sure the box is checked that says "check this folder for new messages" in the properties of each folder. If the only filtering is through the user-configured rules in mozilla/thunderbird then everything gets delivered to the INBOX (or whatever is set up as imap root folder) and then filtered/routed to other folders AFTER the client is opened/started. IOW this may be normal behaviour, not a broken client. All the filtering is on the client side, so that is not the problem. The odd thing is that the client shows that there are new messages in the folder. But when you click on the folder, none of the new messages are in the listing. It looks like a caching problem, but I'm not sure if it is the client or server that is having the problem. But thanks for the response. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mozilla and courier-imap
I'm using the most recent ports for mozilla and courier-imap on an up-to-date FreeBSD-stable. Very often I will not see new messages in a folder until I restart mozilla. I was convinced it was mozilla that was broken, but I've seen similar behavior using Thunderbird on my Windows box. Now I'm not so sure. Anyone else seen this? What is another decent IMAP client in ports? Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: need help on CFLAGS in /etc/make.conf please
Paul Seniura wrote: Chapter 2 of "FreeBSD Developers' Handbook": | 2.4 Compiling with cc | | -O |Create an optimized version of the executable. The compiler |performs various clever tricks to try and produce an executable |that runs faster than normal. You can add a number after the -O |to specify a higher level of optimization, but this often exposes |bugs in the compiler's optimizer. For instance, the version of cc |that comes with the 2.1.0 release of FreeBSD is known to produce |bad code with the -O2 option in some circumstances. | |Optimization is usually only turned on when compiling a release |version. |[...] HUH?!? "the version of cc that comes with 2.1.0" has those -O bugs Good grief, we're running 5.x (-Current, actually)! I can't find any mention of any such bugs with GCC 3.x on i386. Unless there is evidence of more recent gcc bugs, that part of the handbook should really be removed. I can easily imagine the reaction on this list if the reverse were true, and the gcc handbook was knocking FreeBSD for a bug in release 3.0 (or whatever). Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Looking for remote console access card that works with FreeBSD
I'm looking for a remote console card that will work with FreeBSD 5.2 or -current. The machine is a Dell Poweredge 2450. By remote console card, I'm referring to a PCI card that uses a separate network connection so that you can remotely access the equivalent of a serial console via a web browser or telnet/ssh session. Essentially, I need to have remote access to single user mode on a collocated box. I know that AMI makes such cards (MegaRAC G2), but I don't know if they will work with FreeBSD. I checked the hardware compatibility list on the web site, but there was no mention of such cards. Any recommendations would be appreciated. Thanks. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Anyone got MythTV or Freevo working on FreeBSD?
I'm building a PVR (personal video recorder) right now that will be based on either MythTV or Freevo. I'm building it using the WinTV PVR 350 card. From looking at the web pages and documentation for each project, it seems that both of these projects are heavily Linux-centric. Has anybody had success in building either of these packages on a FreeBSD system? Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how 'which'?
Marty Landman wrote: I just installed joe from the ports collection and can run it fine from /usr/local/bin/joe. What puzzles me is that I get a null response to 'which joe'. What am I not understanding here? Type the command "rehash", then try again. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: newbie source question
Marty Landman wrote: I installed the 4.8 mini iso w/o the source and would like to now install the source code too. How is this done, and is there a beginner's tutorial on working with gcc (I assume that's the standard compiler?) on fbsd? Chapter 21 of the FreeBSD handbook covers most of this. Most people that are tracking FreeBSD via source use the utility "cvsup". This part of the handbook covers this utility as well as how to build FreeBSD from source. Once you've read the handbook, it's not that hard at all. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html Also, once you get the source, the comments inside the main Makefile (/usr/src/Makefile) also give the steps necessary to build from source. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: newbie: to pipe the result of a program as commandlineparameter for another.
Zhang Weiwu wrote: Hello. I just checkouted a big program. What I want to do is to remove all CVS/ folders from the hierarchy. There might be other ways to do so (give me a hint?). What I can think of is to run find(1) to find out all CVS folders, and pass them as parameters of rm(1), but I don't know how to do so. That's the purpose of the "xargs" command. For instance, if you wanted to recursively delete all files in the directory /home/foo ending in ".o", you could use the command find /home/foo -name '*.o' -print | xargs rm -f Of course, people will point out that find has options that will allow it to remove files directly. But using xargs is a more general technique that will work in other situations. For instance, if you wanted to "touch" all your *.c files so that they have current modification times, you could use the following find /home/foo -name '*.c' -print | xargs touch Also, xargs knows about the maximum size allowable for the command line, and will use the minimum number of process invocations necessary. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dedicate 1 CPU to a single process
Till Plewe wrote: Can one processor on a dual processor machine be reserved exclusively for the use of a single process? If that is not posssible how can I stop one process being moved back and forth between the two CPUs. - Till I do not believe that is currently possible with FreeBSD. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SNMP help
After installing the net-snmp port, add snmpd_enable="YES" to your /etc/rc.conf. Then the snmpd daemon will start upon next boot (startup script should be in /usr/local/etc/rc.d). Then do your standard Openview snmp discovery for this machine. That should be enough to get you started. If you want to change the data reported, you will need to do some reading at that point to learn how to extend the MIB. The O'reilly book on snmp is logical place to start for this. Richard Coleman [EMAIL PROTECTED] Ronnie Clark wrote: Thanks all for the suggestions. I have the port installed, but how do I configure this beast to work with OpenView? I have looked at the online docs for the port, but it is all jibberish to this newbie. Anyone have a simple to follow doc or set of guidelines to setup net-snmp to be monitored by Openview? Thanks again in advance, Ron Clark --- Dan Nelson <[EMAIL PROTECTED]> wrote: In the last episode (Oct 29), Ronnie Clark said: I have been tasked with building two new FreeBSD Servers for our enterprise. Today, I was told that they have to have the ability to be polled by OpenView. So I have to load SNMP on these servers. Any suggestions as to what I should load to accomplish this? Install the net-snmp port. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Searching contents of files
Here is the classical way to do a recursive grep.
For csh/tcsh, define the alias
alias rgrep 'find . -type f -print | xargs egrep -i \!* /dev/null'
For bash/zsh, define the shell function
rgrep() { find . -type f -print | xargs egrep -i $1 /dev/null}
There are several variations of these that will work. But these are
both fast and portable, and should work on virtually any flavor of unix.
Richard Coleman
[EMAIL PROTECTED]
jason dictos wrote:
Hi All,
I've always used grep text /*/*/* to recursivly search directories for
files with the specified text string in them, however this method doesn't
always work very well (sometimes it bails out halfway through with error
"Argument list too long").
Is there a more effective way to search the contents of files?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firewall rules
Do a quick google search on "building freebsd firewall". I was building a FreeBSD firewall this week, and several of these sites were very helpful. There are sites for both ipfilter and ipfw. So, take your pick. I'm using ipfilter, but either firewall method will be sufficient for most people. Richard Coleman [EMAIL PROTECTED] Mihail wrote: Hello, I'm trying to set up a firewall with ipfw by using the client firewall type given in rc.firewall as an example. My problem is that the client rules don't allow me to do common web-browsing. What should I add to the script to resolve this without seriously compromising security? cheers, Mihail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup and portupgrade
David Bear wrote: I'm still trying to muddle through the loads of different ways to keep FreeBSD 'current' -- meaning, safely patched, aka RELENG_5_1 (for me) As I conceptualize the operations there are two levels of 'patching', 1) the kernel and base system 2) then all the ports that I may have installed I've read the cvsup docs and can see how to update both the kernel source and ports. But the problem I see is the ports. After the ports collection has cvsupdated, I would still need to do a make install for each port I have previous installed, correct? (or, more appropriately, make deinstall, the cvsup the ports, then make install) Is this making things more difficult? Seems there really should be a cleaner way to keep things updated. I've heard reference to a portupgrade package, but can't find any details on how and what it really does-- and how well it plays with cvsupdate. The other rotten thing here is that cvsupdate requires modula-3 -- and portupgrade requires ruby... It would really be nice if all this were done in the most perfect language, python;-) looking for some advice.. thx. cvsup and portupgrade do different things. Cvsup will keep your copy of a particular source trees (/usr/src, /usr/port, etc.) up-to-date with the current sources in the CVS repository. Actually, cvsup can track the sources along any CVS branch point or by date. There is usually a pre-built binary package for cvsup, so you don't generally need to build it from source (or build the modula3 package). Just get it from the FreeBSD ftp site and use pkg_add to add the binary package. But once you've got the updated sources, you need to update your machine. For /usr/src, you have to follow the procedures to "build the world" Check the handbook for this. For /usr/port, you can update manually (pkg_delete the old version and make install the new version) or use portupgrade. To get started with portupgrade, just do: cd /usr/ports/sysutils/portupgrade make install clean rehash # if you are using csh or tcsh pkgdb -F portsdb -Uu If you want to see the ports that are available for updating, use the command "portversion". You will need to re-run "portsdb -Uu" every time you update the ports source tree using cvsup. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: terminal emulation
He said he needs a serial console. You can't do that with telnet. "cu" and "tip" are the traditional Unix interfaces for this. But they suck. There are many better methods in the ports tree. rc Minnesota Slinky wrote: Just a question, why not just use telnet? Eric F Crist AdTech Integrated Systems, Inc (952) 403-9000 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Koptsevich Sent: Sunday, October 05, 2003 4:35 PM To: [EMAIL PROTECTED] Subject: terminal emulation Hi, I would like to use FreeBSD machine as a serial console to another FreeBSD machine. Server part is described in the Handbook, but I have found nothing about client part. Which program should I use for terminal emulation? How can I make, for instance, xterm to communicate to the serial port? Thanks, Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: terminal emulation
Lowell Gilbert wrote: I would like to use FreeBSD machine as a serial console to another FreeBSD machine. Server part is described in the Handbook, but I have found nothing about client part. Which program should I use for terminal emulation? How can I make, for instance, xterm to communicate to the serial port? cu(1). There are plenty of more featureful comm programs in ports/comms. I use the port "minicom" and recommend it. It's pretty small. It uses a (nice) curses interface, so it doesn't require X11. It also has very few dependences in the ports tree (just the lrzsz port). One thing more thing. The default for minicom is a vt102 terminal. So when you hook up to a FreeBSD server, your first command should be "setenv TERM vt102". Otherwise, FreeBSD will assume cons25. If you want the swiss-army-knife of serial programs, there is always Kermit from the ports tree. It takes awhile to learn because it's got so many options. But once you learn it, it will connect to just about anything. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
