Re: Server Transition: IMPORTANT: PLEASE READ!

[Mark]

My intention is to stay connected. It would be great, however, if I could be 
referred to the beginning or intermediate list? I want to stay connected, even 
though most of what goes across this list, is for people that even using the 
Mac for quite some time. Would be great to find someplace to ask questions to 
learn how to become a more expert at Mac. Movie from a PC environment. Moving 
because, my experience with iOS was great.
arosind...@me.com 

Sent from my iPhone

On Jun 24, 2014, at 6:32 PM, JAKE JOEHL  wrote:

I would like to stay on here too, for the time being.
Jake
JAKE JOEHL
jajo...@att.net



On Jun 23, 2014, at 7:12 PM, Jessica Benzing  wrote:

But I am on the list. Just please don't take me off?  

Sent from my iPhone

> On Jun 22, 2014, at 4:35 PM, Eileen Misrahi  wrote:
> 
> Sorry for confusing your name with someone else's. Please accept my apology. 
> 
> Eileen
>> On Jun 22, 2014, at 5:30 AM, "Gordon, Lynne & Tracy" 
>>  wrote:
>> 
>> Hello everybody
>> 
>> As some of you may be aware, we have been planning for some time to migrate 
>> the Mac Access server to a new physical server system and also to a new DNS 
>> host. This involves a very great deal of work on our part and I’d like to 
>> tell you a little bit about why that is the case.
>> 
>> For some time now, we have been experiencing a problem with the server 
>> administration tools we used to use to help us administrate both the member 
>> listing for all of our groups, and also other vital server configurational 
>> data. The net result of these problems is that the member listing is not 
>> visible to us at all, neither is any of the other server data, or the list 
>> data itself.  Therefore, the only access we have to the list configuration 
>> is that which every user has to their own specific configuration. Without 
>> going into too much technical detail, Gordon keeps having to manually 
>> rebuild the Open Directory database because there’s a problem somewhere in 
>> the system and it keeps causing corruption. The GUI-based administration 
>> tools are useless so Gordon needs to use the Terminal and command line tools 
>> to keep this airplane flying! Indeed, Apple’s own engineering staff have 
>> been unable to determine the cause of the problem and their ultimate advice 
>> was to simply trash the server instance totally and rebuild it from the 
>> ground up with a new OS install. That is fine in principle, but we are keen 
>> to retain as much information as possible in order to minimise inconvenience 
>> to our clients and group members. Please know that even those of you who are 
>> not our direct clients are important to us. Although our first duty is to 
>> those for whom we host services, we regard all of our members as part of 
>> what we do. Anyway I am babbling. e h
>> 
>> This means that, in order to obtain the address of each user, along with any 
>> specific configuration settings they may have set, we have to 
>> effectivelyΩzsw log in as though we were that user via the web interface at 
>> .
>>  Aside from this, we’re going to have to manually replicate all of the 
>> generic list data onthe new server for every single one of the groups 
>> hosted here. This, believe me, is no easy task; as some of the groups used 
>> by our commercial clients use very highly configured virtual hosts. One of 
>> our most valued non-commercial clients has multilingual options configured 
>> which we are also very keen to replicate. We shall be in touch with that 
>> client directly shortly to discuss the way forward for them.
>> 
>> Gordon has spent most of this weekend working behind the scenes in the room 
>> from which we run all of our servers; (I’ve almost forgotten what he looks 
>> like! ;-)); on the new system, and even as I write he estimates that several 
>> more days will elapse before we’re ready to even test the new system 
>> locally, let alone expose it to the Internet. Why am I telling you all this? 
>> It’s really quite simple. We require, and would very much appreciate, your 
>> assistance.
>> 
>> It would make our lives far easier if you as list members would take a 
>> moment to drop us a line privately, using the support address 
>>  to let us know whether or not you anticipate or 
>> intend to remain a member of this group in the medium to long term, or even 
>> whether you wish us to add you to the new system at all. As well as this, we 
>> would be grateful if you would please let us have details of any specific 
>> settings you have configured on our server. For instance, if you are using 
>> digest mode to receive messages in bulk, whether you have a system password 
>> configured which overrides the default, etc.. Of course, when the new 
>> instance goes live, you will be able to modify your own configuration once 
>> you’ve been subscribed. We are simply trying to save you the work and 
>>

Re: Server Transition: IMPORTANT: PLEASE READ!

[Peter Greco]

I'd like to stay on too please!
Peter
<--- Mac Access At Mac Access Dot Net --->

To reply to this post, please address your message to mac-access@mac-access.net

You can find an archive of all messages postedto the Mac-Access forum at 
either the list's own dedicated web archive:

or at the public Mail Archive:
.
Subscribe to the list's RSS feed from:


As the Mac Access Dot Net administrators, we do our very best to ensure that 
the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and 
worm-free.  However, this should in no way replace your own security strategy.  
We assume neither liability nor responsibility should something unpredictable 
happen.

Please remember to update your membership preferences periodically by visiting 
the list website at:

Re: Server Transition: IMPORTANT: PLEASE READ!

[JAKE JOEHL]

I would like to stay on here too, for the time being.
Jake
JAKE JOEHL
jajo...@att.net



On Jun 23, 2014, at 7:12 PM, Jessica Benzing  wrote:

But I am on the list. Just please don't take me off?  

Sent from my iPhone

> On Jun 22, 2014, at 4:35 PM, Eileen Misrahi  wrote:
> 
> Sorry for confusing your name with someone else's. Please accept my apology. 
> 
> Eileen
>> On Jun 22, 2014, at 5:30 AM, "Gordon, Lynne & Tracy" 
>>  wrote:
>> 
>> Hello everybody
>> 
>> As some of you may be aware, we have been planning for some time to migrate 
>> the Mac Access server to a new physical server system and also to a new DNS 
>> host. This involves a very great deal of work on our part and I’d like to 
>> tell you a little bit about why that is the case.
>> 
>> For some time now, we have been experiencing a problem with the server 
>> administration tools we used to use to help us administrate both the member 
>> listing for all of our groups, and also other vital server configurational 
>> data. The net result of these problems is that the member listing is not 
>> visible to us at all, neither is any of the other server data, or the list 
>> data itself.  Therefore, the only access we have to the list configuration 
>> is that which every user has to their own specific configuration. Without 
>> going into too much technical detail, Gordon keeps having to manually 
>> rebuild the Open Directory database because there’s a problem somewhere in 
>> the system and it keeps causing corruption. The GUI-based administration 
>> tools are useless so Gordon needs to use the Terminal and command line tools 
>> to keep this airplane flying! Indeed, Apple’s own engineering staff have 
>> been unable to determine the cause of the problem and their ultimate advice 
>> was to simply trash the server instance totally and rebuild it from the 
>> ground up with a new OS install. That is fine in principle, but we are keen 
>> to retain as much information as possible in order to minimise inconvenience 
>> to our clients and group members. Please know that even those of you who are 
>> not our direct clients are important to us. Although our first duty is to 
>> those for whom we host services, we regard all of our members as part of 
>> what we do. Anyway I am babbling. e h
>> 
>> This means that, in order to obtain the address of each user, along with any 
>> specific configuration settings they may have set, we have to 
>> effectivelyΩzsw log in as though we were that user via the web interface at 
>> .
>>  Aside from this, we’re going to have to manually replicate all of the 
>> generic list data onthe new server for every single one of the groups 
>> hosted here. This, believe me, is no easy task; as some of the groups used 
>> by our commercial clients use very highly configured virtual hosts. One of 
>> our most valued non-commercial clients has multilingual options configured 
>> which we are also very keen to replicate. We shall be in touch with that 
>> client directly shortly to discuss the way forward for them.
>> 
>> Gordon has spent most of this weekend working behind the scenes in the room 
>> from which we run all of our servers; (I’ve almost forgotten what he looks 
>> like! ;-)); on the new system, and even as I write he estimates that several 
>> more days will elapse before we’re ready to even test the new system 
>> locally, let alone expose it to the Internet. Why am I telling you all this? 
>> It’s really quite simple. We require, and would very much appreciate, your 
>> assistance.
>> 
>> It would make our lives far easier if you as list members would take a 
>> moment to drop us a line privately, using the support address 
>>  to let us know whether or not you anticipate or 
>> intend to remain a member of this group in the medium to long term, or even 
>> whether you wish us to add you to the new system at all. As well as this, we 
>> would be grateful if you would please let us have details of any specific 
>> settings you have configured on our server. For instance, if you are using 
>> digest mode to receive messages in bulk, whether you have a system password 
>> configured which overrides the default, etc.. Of course, when the new 
>> instance goes live, you will be able to modify your own configuration once 
>> you’ve been subscribed. We are simply trying to save you the work and 
>> minimise your inconvenience. :)
>> 
>> We have not far short of 500 members in this group alone now, and it would 
>> be a horrendously laborious task for Gordon to use the web interface to 
>> inspect every single user’s individual configuration; especially since the 
>> majority of users have never changed any settings. You may say “why not just 
>> use the defaults then?” That in theory may save time. But we are anxious to 
>> have the transition be as seamless as possible for everybody and, therefore, 
>> we’d like t

Re: Server Transition: IMPORTANT: PLEASE READ!

[Jessica Benzing]

But I am on the list. Just please don't take me off?  

Sent from my iPhone

> On Jun 22, 2014, at 4:35 PM, Eileen Misrahi  wrote:
> 
> Sorry for confusing your name with someone else's. Please accept my apology. 
> 
> Eileen
>> On Jun 22, 2014, at 5:30 AM, "Gordon, Lynne & Tracy" 
>>  wrote:
>> 
>> Hello everybody
>> 
>> As some of you may be aware, we have been planning for some time to migrate 
>> the Mac Access server to a new physical server system and also to a new DNS 
>> host. This involves a very great deal of work on our part and I’d like to 
>> tell you a little bit about why that is the case.
>> 
>> For some time now, we have been experiencing a problem with the server 
>> administration tools we used to use to help us administrate both the member 
>> listing for all of our groups, and also other vital server configurational 
>> data. The net result of these problems is that the member listing is not 
>> visible to us at all, neither is any of the other server data, or the list 
>> data itself.  Therefore, the only access we have to the list configuration 
>> is that which every user has to their own specific configuration. Without 
>> going into too much technical detail, Gordon keeps having to manually 
>> rebuild the Open Directory database because there’s a problem somewhere in 
>> the system and it keeps causing corruption. The GUI-based administration 
>> tools are useless so Gordon needs to use the Terminal and command line tools 
>> to keep this airplane flying! Indeed, Apple’s own engineering staff have 
>> been unable to determine the cause of the problem and their ultimate advice 
>> was to simply trash the server instance totally and rebuild it from the 
>> ground up with a new OS install. That is fine in principle, but we are keen 
>> to retain as much information as possible in order to minimise inconvenience 
>> to our clients and group members. Please know that even those of you who are 
>> not our direct clients are important to us. Although our first duty is to 
>> those for whom we host services, we regard all of our members as part of 
>> what we do. Anyway I am babbling. e h
>> 
>> This means that, in order to obtain the address of each user, along with any 
>> specific configuration settings they may have set, we have to 
>> effectivelyΩzsw log in as though we were that user via the web interface at 
>> .
>>  Aside from this, we’re going to have to manually replicate all of the 
>> generic list data onthe new server for every single one of the groups 
>> hosted here. This, believe me, is no easy task; as some of the groups used 
>> by our commercial clients use very highly configured virtual hosts. One of 
>> our most valued non-commercial clients has multilingual options configured 
>> which we are also very keen to replicate. We shall be in touch with that 
>> client directly shortly to discuss the way forward for them.
>> 
>> Gordon has spent most of this weekend working behind the scenes in the room 
>> from which we run all of our servers; (I’ve almost forgotten what he looks 
>> like! ;-)); on the new system, and even as I write he estimates that several 
>> more days will elapse before we’re ready to even test the new system 
>> locally, let alone expose it to the Internet. Why am I telling you all this? 
>> It’s really quite simple. We require, and would very much appreciate, your 
>> assistance.
>> 
>> It would make our lives far easier if you as list members would take a 
>> moment to drop us a line privately, using the support address 
>>  to let us know whether or not you anticipate or 
>> intend to remain a member of this group in the medium to long term, or even 
>> whether you wish us to add you to the new system at all. As well as this, we 
>> would be grateful if you would please let us have details of any specific 
>> settings you have configured on our server. For instance, if you are using 
>> digest mode to receive messages in bulk, whether you have a system password 
>> configured which overrides the default, etc.. Of course, when the new 
>> instance goes live, you will be able to modify your own configuration once 
>> you’ve been subscribed. We are simply trying to save you the work and 
>> minimise your inconvenience. :)
>> 
>> We have not far short of 500 members in this group alone now, and it would 
>> be a horrendously laborious task for Gordon to use the web interface to 
>> inspect every single user’s individual configuration; especially since the 
>> majority of users have never changed any settings. You may say “why not just 
>> use the defaults then?” That in theory may save time. But we are anxious to 
>> have the transition be as seamless as possible for everybody and, therefore, 
>> we’d like to have this data available in a database which I shall be 
>> compiling for Gordon as and when we receive each member’s response. We plan 
>> t

Re: Server Transition: IMPORTANT: PLEASE READ!

[Eileen Misrahi]

Sorry for confusing your name with someone else's. Please accept my apology. 

Eileen  
On Jun 22, 2014, at 5:30 AM, "Gordon, Lynne & Tracy"  
wrote:

> Hello everybody
> 
> As some of you may be aware, we have been planning for some time to migrate 
> the Mac Access server to a new physical server system and also to a new DNS 
> host. This involves a very great deal of work on our part and I’d like to 
> tell you a little bit about why that is the case.
> 
> For some time now, we have been experiencing a problem with the server 
> administration tools we used to use to help us administrate both the member 
> listing for all of our groups, and also other vital server configurational 
> data. The net result of these problems is that the member listing is not 
> visible to us at all, neither is any of the other server data, or the list 
> data itself.  Therefore, the only access we have to the list configuration is 
> that which every user has to their own specific configuration. Without going 
> into too much technical detail, Gordon keeps having to manually rebuild the 
> Open Directory database because there’s a problem somewhere in the system and 
> it keeps causing corruption. The GUI-based administration tools are useless 
> so Gordon needs to use the Terminal and command line tools to keep this 
> airplane flying! Indeed, Apple’s own engineering staff have been unable to 
> determine the cause of the problem and their ultimate advice was to simply 
> trash the server instance totally and rebuild it from the ground up with a 
> new OS install. That is fine in principle, but we are keen to retain as much 
> information as possible in order to minimise inconvenience to our clients and 
> group members. Please know that even those of you who are not our direct 
> clients are important to us. Although our first duty is to those for whom we 
> host services, we regard all of our members as part of what we do. Anyway I 
> am babbling. e h
> 
> This means that, in order to obtain the address of each user, along with any 
> specific configuration settings they may have set, we have to effectivelyΩzsw 
> log in as though we were that user via the web interface at 
> .
>  Aside from this, we’re going to have to manually replicate all of the 
> generic list data on   the new server for every single one of the groups 
> hosted here. This, believe me, is no easy task; as some of the groups used by 
> our commercial clients use very highly configured virtual hosts. One of our 
> most valued non-commercial clients has multilingual options configured which 
> we are also very keen to replicate. We shall be in touch with that client 
> directly shortly to discuss the way forward for them.
> 
> Gordon has spent most of this weekend working behind the scenes in the room 
> from which we run all of our servers; (I’ve almost forgotten what he looks 
> like! ;-)); on the new system, and even as I write he estimates that several 
> more days will elapse before we’re ready to even test the new system locally, 
> let alone expose it to the Internet. Why am I telling you all this? It’s 
> really quite simple. We require, and would very much appreciate, your 
> assistance.
> 
> It would make our lives far easier if you as list members would take a moment 
> to drop us a line privately, using the support address 
>  to let us know whether or not you anticipate or 
> intend to remain a member of this group in the medium to long term, or even 
> whether you wish us to add you to the new system at all. As well as this, we 
> would be grateful if you would please let us have details of any specific 
> settings you have configured on our server. For instance, if you are using 
> digest mode to receive messages in bulk, whether you have a system password 
> configured which overrides the default, etc.. Of course, when the new 
> instance goes live, you will be able to modify your own configuration once 
> you’ve been subscribed. We are simply trying to save you the work and 
> minimise your inconvenience. :)
> 
> We have not far short of 500 members in this group alone now, and it would be 
> a horrendously laborious task for Gordon to use the web interface to inspect 
> every single user’s individual configuration; especially since the majority 
> of users have never changed any settings. You may say “why not just use the 
> defaults then?” That in theory may save time. But we are anxious to have the 
> transition be as seamless as possible for everybody and, therefore, we’d like 
> to have this data available in a database which I shall be compiling for 
> Gordon as and when we receive each member’s response. We plan to maintain 
> this database in the longer term, so that we do have a permanent record of 
> who is currently a member of our groups, and any specific configuration they 
> may be using.
> 
> Sadly, as I’ve already indicated, 

Server Transition: IMPORTANT: PLEASE READ!

[Gordon, Lynne & Tracy]

Hello everybody

As some of you may be aware, we have been planning for some time to migrate the 
Mac Access server to a new physical server system and also to a new DNS host. 
This involves a very great deal of work on our part and I’d like to tell you a 
little bit about why that is the case.

For some time now, we have been experiencing a problem with the server 
administration tools we used to use to help us administrate both the member 
listing for all of our groups, and also other vital server configurational 
data. The net result of these problems is that the member listing is not 
visible to us at all, neither is any of the other server data, or the list data 
itself.  Therefore, the only access we have to the list configuration is that 
which every user has to their own specific configuration. Without going into 
too much technical detail, Gordon keeps having to manually rebuild the Open 
Directory database because there’s a problem somewhere in the system and it 
keeps causing corruption. The GUI-based administration tools are useless so 
Gordon needs to use the Terminal and command line tools to keep this airplane 
flying! Indeed, Apple’s own engineering staff have been unable to determine the 
cause of the problem and their ultimate advice was to simply trash the server 
instance totally and rebuild it from the ground up with a new OS install. That 
is fine in principle, but we are keen to retain as much information as possible 
in order to minimise inconvenience to our clients and group members. Please 
know that even those of you who are not our direct clients are important to us. 
Although our first duty is to those for whom we host services, we regard all of 
our members as part of what we do. Anyway I am babbling. e h

This means that, in order to obtain the address of each user, along with any 
specific configuration settings they may have set, we have to effectivelyΩzsw 
log in as though we were that user via the web interface at 
.
 Aside from this, we’re going to have to manually replicate all of the generic 
list data on the new server for every single one of the groups hosted here. 
This, believe me, is no easy task; as some of the groups used by our commercial 
clients use very highly configured virtual hosts. One of our most valued 
non-commercial clients has multilingual options configured which we are also 
very keen to replicate. We shall be in touch with that client directly shortly 
to discuss the way forward for them.

Gordon has spent most of this weekend working behind the scenes in the room 
from which we run all of our servers; (I’ve almost forgotten what he looks 
like! ;-)); on the new system, and even as I write he estimates that several 
more days will elapse before we’re ready to even test the new system locally, 
let alone expose it to the Internet. Why am I telling you all this? It’s really 
quite simple. We require, and would very much appreciate, your assistance.

It would make our lives far easier if you as list members would take a moment 
to drop us a line privately, using the support address  
to let us know whether or not you anticipate or intend to remain a member of 
this group in the medium to long term, or even whether you wish us to add you 
to the new system at all. As well as this, we would be grateful if you would 
please let us have details of any specific settings you have configured on our 
server. For instance, if you are using digest mode to receive messages in bulk, 
whether you have a system password configured which overrides the default, 
etc.. Of course, when the new instance goes live, you will be able to modify 
your own configuration once you’ve been subscribed. We are simply trying to 
save you the work and minimise your inconvenience. :)

We have not far short of 500 members in this group alone now, and it would be a 
horrendously laborious task for Gordon to use the web interface to inspect 
every single user’s individual configuration; especially since the majority of 
users have never changed any settings. You may say “why not just use the 
defaults then?” That in theory may save time. But we are anxious to have the 
transition be as seamless as possible for everybody and, therefore, we’d like 
to have this data available in a database which I shall be compiling for Gordon 
as and when we receive each member’s response. We plan to maintain this 
database in the longer term, so that we do have a permanent record of who is 
currently a member of our groups, and any specific configuration they may be 
using.

Sadly, as I’ve already indicated, it simply is not practical to expect Gordon 
to spend the time trawling through the web interface like that. Therefore, for 
those users who do not respond to this request, we will assume that they no 
longer wish to be a part of our group and as such we will not include them. It 
is vital that we h