For new computers:
Setup everything like you like it, and then copy the Administrator profile, over-writing the Default User profile. Bang whiz.
If you need something more complicated or dynamic, you're looking at GPO, custom ADM templates or tools to make them, maybe some regedit or login scripts - and maybe (maybe not) roaming profiles.
I may have misread their page, or they may have clarified the point. I thought that, when I read their page yesterday, it said 'connection to port 25 from another network is bad.' Ignoring, as you said, those who do inbound SMTP and outbound SMTP on the same server, or perform some variety of authentication. Now that I've re-read it, it doesn't match my memory.
The big things that tripped us up was the IP block list. We're supposedly 'dynamic' although we're not. The ISP doesn't differentiate their IP blocks, apparently, so the static customers get lumped in with the dynamic users from AOL's point of view.
Then they should be listed on rfc-ignorant.
Their page says
* AOL's mail servers may reject connections from IP addresses which have no reverse-DNS (PTR record assigned).
So, not that they have to match, although I thought I'd read that elsewhere, but that they MAY reject if there is NO rDNS.
Second point
Sorry - slightly mis-worded. Link from the link on the original post.
Quote:
The second way to test your server is to telnet to the IP address in question on port 25 from a different Internet Service Provider and manually initiate an SMTP transaction. If you can send mail from yourself from the different ISP, your server is an open relay.
Are you on DSL? My company's mail server is on DSL from the telco, who doesn't actually have 'business-class' versus 'residential class' DSL service.
AOL also requires that your R-DNS matches what you claim your domain name to be. Do you have your PTR records in order? If you're on DSL (or dial-up) that can be difficult or impossible, depending on your provider.
I also question AOL's explanation of 'open relay.' They say that, if someone not on your network can connect to port 25 on your server, then you're an open relay. This entirely ignores POP-before-SMTP, IMAP-before-SMTP, and SMTP AUTH, which is what we use.
They may be better about it than their simple explanation; I only filled out their webform last night, so I don't have my results in yet. My solution was to hard-code the MX record for AOL.com to actually be my ISP's SMTP server, so mail to AOL gets relayed from a more legitimate-seeming source.
The government doesn't need to own the phone lines - there is recourse already. Threaten Verizon - tell them you're going to call the DPUC. Dpeartment of Public Utilities Commission.
Or maybe call the DPUC first, THEN call Verizon, depending on what the DPUC says. You'll have service faster than you can say "Attorney General."
I'll have to speak up for our own product here. The IP Tattletale family is a sysadmin-friendly set of devices for exactly this, and more. The original Tattletale, still sold, is a POTS-line based product with a Central Station contract. This one will fit your needs much better.
It can spit out everything via SNMP; with an add-on license you can even use the device itself to aggregate other SNMP-based devices. For large-scale environments, you can roll your own MRTG or RRDtool configs, or you can buy the IP Tattletale Central, which is a 1U linux box that hold historical data and can push out threshold settings and configs to many Tattletale units.
I can't believe I'm actually posting a link to Snopes.com to Slashdot. I usually just have to do it to the people at work who think that they can buy oil/gasoline from companies that don't trade with Middle Eastern companies, or something.
sigh
At any rate, here you go. No truth - just cuz it's on Yahoo, don't ignore that fact that it was written by the GODDAM WORLD WEEKLY NEWS. Christ on a crutch...
AD doesn't allow for the same kind of delegation that NDS does. In NDS, the root admin can actually make a portion of the tree that he has no rights to, can't get back, and possibly not even see. Under AD, the top-level admins can ALWAYS somehow take ownership.
Actually, it can make (for example) coal much cleaner to burn, and more efficient as well due to the pre-processing. There was more in the article dealing with the other ways in which this would be an excellent adjunct to our existing fossil-fuel economy and most associated businesses, while ALSO reducing our need to pull this stuff up from the ground.
No problem with mine - supposedly, the tongue is one of the fastest-healing parts of the body. Think about it, most of the mucous-membrane tissue has to be pretty robust, it's always in contact with foreign matter.
Cutter John was in the wheelchair (typically playing the role of Captain Kirk), NOT Steve Dallas, who typically had little patience for that kind of play. Especially when they removed his transmission from his 'vette. . .
Administration of the data in a directory is a sensitive point. Data administration concerns data management with a directory structure and content. The IBM SecureWay Directory server comes with a set of management utilities to assist an administrator in managing the directory's contents.
There are command line utilities that are used to handle large amounts of data, for example, to import thousands of entries in one single step. These utilities include the following:
* ldif
* ldif2db
* bulkload
* db2ldif
Because they access data in the database directly, the tools listed above must run on a directory server. Note that the ldif2db, bulkload, and the db2ldif utilities support the conversion from a specified local character set to/from UTF-8 (see also 4.3, "UTF-8 Support" on page 83).
Another set of utilities are more geared towards handling of single (or a few) entries at a time. These include:
* ldapsearch
* ldapmodify
* ldapdelete
* ldapmodrdn
* ldapadd
These latter tools use LDAP to communicate to an LDAP server, and they can, therefore, be run on a server or a client. They are, therefore, included in the IBM SecureWay Directory Client SDK. Source code for these utilities is provided, too, to allow application programmers to modify them as required or as sample programs to learn about LDAP programming. A parameter allows to specify whether LDAP Version 2 or Version 3 is to be used (the default is Version 2).
While you have some reasonable points, 'blind' means 'entirely unable to see.' The Lions (a big fundraiser for this cause) like to use the term 'Low Vision', to also refer to macular degeneration, all other kinds of retinopathy, etc.
Fidelco, the guide-dog organization that my wife and I raise puppies for, uses the term 'visually impaired' as well, and they're not a bunch of politically-correct crusaders. George Salpietro, the Senior VP of the foundation, is himself impaired and uses a Fidelco guide dog, but he's not blind. He can see a few feet, with very little detail. So he'll say, "Hi" and look right at you, which can cause a little shear between your experience and stereotype.
In Connecticut, SNET (the local telco) no longer sells a service that guarantees that a LADA circuit will be over actual copper. If you get one, it could be over pure copper today, and tomorrow part of the run could be digital; which of course leaves you crap out of luck.
Our mailserver was an open relay for some time (previous admin.) We got blacklisted. I gave everyone in the organization one week to turn on SMTP AUTH in Outlook, then required it at the server. Resubmitted our server for testing; got a clean bill of health in less than an hour.
The Calendaring and Scheduling Core Object is a collection of
calendaring and scheduling information. Typically, this information
will consist of a single iCalendar object. However, multiple
iCalendar objects can be sequentially grouped together. The first
line and last line of the iCalendar object MUST contain a pair of
iCalendar object delimiter strings. The syntax for an iCalendar
object is as follows:
We have an Advanced Resource Management Process Improvement Team. Name chosen for tongue-in-cheek purposes, thank god. Their letterhead is one of the Word clipart with some stick figure raising its arms, like it's trying to hold something up.
At Pfizer, in the clinical testing pharmacy, we had the Document Information Management group. DIMG or the DIM group.
Slashdot Mirror
You ever see In the Company of Men?
For new computers: Setup everything like you like it, and then copy the Administrator profile, over-writing the Default User profile. Bang whiz. If you need something more complicated or dynamic, you're looking at GPO, custom ADM templates or tools to make them, maybe some regedit or login scripts - and maybe (maybe not) roaming profiles.
The big things that tripped us up was the IP block list. We're supposedly 'dynamic' although we're not. The ISP doesn't differentiate their IP blocks, apparently, so the static customers get lumped in with the dynamic users from AOL's point of view.
Then they should be listed on rfc-ignorant. Their page says
* AOL's mail servers may reject connections from IP addresses which have no reverse-DNS (PTR record assigned).
So, not that they have to match, although I thought I'd read that elsewhere, but that they MAY reject if there is NO rDNS.
Second point
Sorry - slightly mis-worded. Link from the link on the original post.
Quote:
The second way to test your server is to telnet to the IP address in question on port 25 from a different Internet Service Provider and manually initiate an SMTP transaction. If you can send mail from yourself from the different ISP, your server is an open relay.
AOL also requires that your R-DNS matches what you claim your domain name to be. Do you have your PTR records in order? If you're on DSL (or dial-up) that can be difficult or impossible, depending on your provider.
I also question AOL's explanation of 'open relay.' They say that, if someone not on your network can connect to port 25 on your server, then you're an open relay. This entirely ignores POP-before-SMTP, IMAP-before-SMTP, and SMTP AUTH, which is what we use.
They may be better about it than their simple explanation; I only filled out their webform last night, so I don't have my results in yet. My solution was to hard-code the MX record for AOL.com to actually be my ISP's SMTP server, so mail to AOL gets relayed from a more legitimate-seeming source.
Or maybe call the DPUC first, THEN call Verizon, depending on what the DPUC says. You'll have service faster than you can say "Attorney General."
How does 10 years of experience translate into knowing about the hardware bug they slipped into your keyboard?
I'll have to speak up for our own product here. The IP Tattletale family is a sysadmin-friendly set of devices for exactly this, and more. The original Tattletale, still sold, is a POTS-line based product with a Central Station contract. This one will fit your needs much better.
It can spit out everything via SNMP; with an add-on license you can even use the device itself to aggregate other SNMP-based devices. For large-scale environments, you can roll your own MRTG or RRDtool configs, or you can buy the IP Tattletale Central, which is a 1U linux box that hold historical data and can push out threshold settings and configs to many Tattletale units.
</commercial>
Come on - this was a post from 1994, and the poster doesn't even say THEN that this was new.
sigh
At any rate, here you go. No truth - just cuz it's on Yahoo, don't ignore that fact that it was written by the GODDAM WORLD WEEKLY NEWS. Christ on a crutch...
Of course, 98 and ME (AFAIK) don't automatically go looking for the Windows Update server at all, unless there was a patch for that.
Q. Can I run SUS on an Active Directory domain controller?
A. Yes, SUS 1.0 SP1 allows for this.
AD doesn't allow for the same kind of delegation that NDS does. In NDS, the root admin can actually make a portion of the tree that he has no rights to, can't get back, and possibly not even see. Under AD, the top-level admins can ALWAYS somehow take ownership.
I think that you meant to say, "Java is owned by Sun." I also know that YOU know that, but that really took me a second to try to wrap my mind around.
Actually, it can make (for example) coal much cleaner to burn, and more efficient as well due to the pre-processing. There was more in the article dealing with the other ways in which this would be an excellent adjunct to our existing fossil-fuel economy and most associated businesses, while ALSO reducing our need to pull this stuff up from the ground.
No problem with mine - supposedly, the tongue is one of the fastest-healing parts of the body. Think about it, most of the mucous-membrane tissue has to be pretty robust, it's always in contact with foreign matter.
Cutter John was in the wheelchair (typically playing the role of Captain Kirk), NOT Steve Dallas, who typically had little patience for that kind of play. Especially when they removed his transmission from his 'vette. . .
7.8 Command Line Utilities
Administration of the data in a directory is a sensitive point. Data administration concerns data management with a directory structure and content. The IBM SecureWay Directory server comes with a set of management utilities to assist an administrator in managing the directory's contents.
There are command line utilities that are used to handle large amounts of data, for example, to import thousands of entries in one single step. These utilities include the following:
* ldif
* ldif2db
* bulkload
* db2ldif
Because they access data in the database directly, the tools listed above must run on a directory server. Note that the ldif2db, bulkload, and the db2ldif utilities support the conversion from a specified local character set to/from UTF-8 (see also 4.3, "UTF-8 Support" on page 83).
Another set of utilities are more geared towards handling of single (or a few) entries at a time. These include:
* ldapsearch
* ldapmodify
* ldapdelete
* ldapmodrdn
* ldapadd
These latter tools use LDAP to communicate to an LDAP server, and they can, therefore, be run on a server or a client. They are, therefore, included in the IBM SecureWay Directory Client SDK. Source code for these utilities is provided, too, to allow application programmers to modify them as required or as sample programs to learn about LDAP programming. A parameter allows to specify whether LDAP Version 2 or Version 3 is to be used (the default is Version 2).
While you have some reasonable points, 'blind' means 'entirely unable to see.' The Lions (a big fundraiser for this cause) like to use the term 'Low Vision', to also refer to macular degeneration, all other kinds of retinopathy, etc. Fidelco, the guide-dog organization that my wife and I raise puppies for, uses the term 'visually impaired' as well, and they're not a bunch of politically-correct crusaders. George Salpietro, the Senior VP of the foundation, is himself impaired and uses a Fidelco guide dog, but he's not blind. He can see a few feet, with very little detail. So he'll say, "Hi" and look right at you, which can cause a little shear between your experience and stereotype.
In Connecticut, SNET (the local telco) no longer sells a service that guarantees that a LADA circuit will be over actual copper. If you get one, it could be over pure copper today, and tomorrow part of the run could be digital; which of course leaves you crap out of luck.
Our mailserver was an open relay for some time (previous admin.) We got blacklisted. I gave everyone in the organization one week to turn on SMTP AUTH in Outlook, then required it at the server. Resubmitted our server for testing; got a clean bill of health in less than an hour.
Light week for the DNSRBL lists, maybe?
iCalendar Object
The Calendaring and Scheduling Core Object is a collection of
calendaring and scheduling information. Typically, this information
will consist of a single iCalendar object. However, multiple
iCalendar objects can be sequentially grouped together. The first
line and last line of the iCalendar object MUST contain a pair of
iCalendar object delimiter strings. The syntax for an iCalendar
object is as follows:
icalobject = 1*("BEGIN" ":" "VCALENDAR" CRLF
icalbody
"END" ":" "VCALENDAR" CRLF)
The following is a simple example of an iCalendar object:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
BEGIN:VEVENT
DTSTART:19970714T170000Z
DTEND:19970715T035959Z
SUMMARY:Bastille Day Party
END:VEVENT
END:VCALENDAR
It's not quite as bad as stuffing them into some app their not used to through a complex delivery method.
You should note that the 'whore' comment was, in fact, in italics. This indicates that it was written by the submitter, not the editor.
At Pfizer, in the clinical testing pharmacy, we had the Document Information Management group. DIMG or the DIM group.