ReiserFS has been known to suck under load, like the mail queue directory, or the mail spool of a busy server. It will be a few years before Reiser can be trusted with critical data.
The 1993 bomb blasts certainly did not trigger communal riots.
But they did result in an enormous backlash against the local mafia which supported the terrorists. Most of the mafia leaders fled to countries with no extradiction treaties, or died.
Support? This is the accounting department, and you are costing us money. By the time we are finished with you, you will owe us money. And don't try to deny it, we have caller id.
587/TCP requires SMTP AUTH, and optionally TLS. I doubt that 587/TCP is likely to be blocked at all, since even weak passwords can be protected by SSL.
You: "I have a scheme to save the company 10% of its bandwidth costs and increase your bonus by 15% for innovative cost cutting measures, but that will cause a slight pressure on the balance sheet for the next quarter."
Put this in the first quarter of the year, and you should be able squeeze it through
If you want to use email for marketing, use a confirmed opt-in system.
COI requires the user to ask for the mail, and then actually take action to confirm that (note that merely clicking a link with a HTTP GET is not sufficient for the confirm action, you need to get the user to POST the request). The most preferred form is an email response wth a suitably hard to break key in the mail.
This is the technique used by legitimate mailing list management software (majordomo, mailman, ezmlm, sympa, lyris, ecartis driven lists all support this).
Note that the typical double opt-in excuse of confirming by not unsubscribing is not a valid form of COI. COI requires active user participation in the second step, inaction is not an excuse.
That is only for broken operating systems which are vulnerable.
I recommend Linux/FreeBSD on the desktop for x86, or OS X for those on PPC.
Take your pick, much safer not to use Windows. And if you really have to use Windows, don't hook those boxen to the publicly connected network. Put them behind application level gateways, with really limited internet access (if any) Having a separate box for surfing and checking email helps.
For me, definitely. I run a few GTK+ applications, a couple of Xlib apps so I definitely see large savings in memory use.
Note that I don't use GNOME or KDE, so the actual savings are quite high. The top two memory hogs are Mozilla and X at the moment. My GTK+ apps are using about 4 Mb of RAM each, but 3 MB of that is shared memory, so the effective use is about 8 MB or so.
Slashdot Mirror
Perhaps you need isconf? http://www.infrastructures.org
ReiserFS has been known to suck under load, like the mail queue directory, or the mail spool of a busy server. It will be a few years before Reiser can be trusted with critical data.
She is a better programmer, he is a better administrator. Put them in those roles, and they will do fine.
The 1993 bomb blasts certainly did not trigger communal riots.
But they did result in an enormous backlash against the local mafia which supported the terrorists. Most of the mafia leaders fled to countries with no extradiction treaties, or died.
Support? This is the accounting department, and you are costing us money. By the time we are finished with you, you will owe us money. And don't try to deny it, we have caller id.
Hmmm. The CLI *is* easy to use. Doing what I do with a GUI would just take me longer. (Actually, it does take me far longer to work with a GUI).
So, ease of use for whom?
As far as I am concerned, so long as the GUI works, it doesn't matter what it looks like.
But if you can save the computer a few seconds of time, those seconds add up over the lifetime of the program.
Remember that your program can have many more users than programmers, and their time is worth something too.
No they don't. Spam is quite well defined. Unsolicited Bulk Email.
You can whine all you want about content filtering, but spam is only about consent, not about content.
587/TCP requires SMTP AUTH, and optionally TLS.
I doubt that 587/TCP is likely to be blocked at all, since even weak passwords can be protected by SSL.
You: "I have a scheme to save the company 10% of its bandwidth costs and increase your bonus by 15% for innovative cost cutting measures, but that will cause a slight pressure on the balance sheet for the next quarter."
Put this in the first quarter of the year, and you should be able squeeze it through
Spam is Unsolicited Bulk Email (It has to be both unsolicited and bulk).
This lands up in the mailbox of someone who did not ask for it.
For those violating copyright, both the sender and the reciever have agreed to participate.
The issue is one of consent, not one of content.
Just pull down the CBL zonefile and count the number of listed IPs.
IIRC, SPEWS does list UUnet in there.
The message submissing port to be used by end users is 587/tcp, not port 25/tcp.
Or just VPN to your office and be done with it.
If you want to use email for marketing, use a confirmed opt-in system.
COI requires the user to ask for the mail, and then actually take action to confirm that (note that merely clicking a link with a HTTP GET is not sufficient for the confirm action, you need to get the user to POST the request).
The most preferred form is an email response wth a suitably hard to break key in the mail.
This is the technique used by legitimate mailing list management software (majordomo, mailman, ezmlm, sympa, lyris, ecartis driven lists all support this).
Note that the typical double opt-in excuse of confirming by not unsubscribing is not a valid form of COI. COI requires active user participation in the second step, inaction is not an excuse.
That would depend on whether a record company executive is considered human.
Run both postmasters in parallel, and have slony feed from 7.x to 8.0 (you need to upgrade anyway. 7.2.x has data corruption issues).
Slony is your friend.
That is only for broken operating systems which are vulnerable.
I recommend Linux/FreeBSD on the desktop for x86, or OS X for those on PPC.
Take your pick, much safer not to use Windows. And if you really have to use Windows, don't hook those boxen to the publicly connected network. Put them behind application level gateways, with really limited internet access (if any) Having a separate box for surfing and checking email helps.
Be a real geek! Duct tape forever!
Hmmm, provides is definitely there.
/usr/ports/mail/postfix-current && make install replace is hard to beat :)
And please do not compare RPM to apt-get.
RPM is equivalent to dpkg.
YUM/URPMI/up2date are equivalent to apt-get.
Of course, nothing matches portage, or BSD ports.
cd
For me, definitely. I run a few GTK+ applications, a couple of Xlib apps so I definitely see large savings in memory use.
Note that I don't use GNOME or KDE, so the actual savings are quite high. The top two memory hogs are Mozilla and X at the moment. My GTK+ apps are using about 4 Mb of RAM each, but 3 MB of that is shared memory, so the effective use is about 8 MB or so.
Email headers are required to be 7 bit ASCII. See RFC 2821.
In which case you generate the entire site with a script once :).
CVS + make and your favorite template engine of choice.
perl file1.pl > index.html
perl file2.pl > this-is-my-second-page.html
Generating a static page with everything consistent is then trivial (if something breaks, it breaks everywhere simultaneously).
What makes you think they use ISP relays?
Hell, clickable link:
/. allows an inline img:
http://nixcartel.org/~devdas/minute.png
And if