[BlueOnyx:07225] Re: Can't delete virtual sites since mailman

Thu May 5 11:26:53 -05 2011

If that’s a concern, then using siteX_db as the default for MySQL databases
in the GUI is also problematic.  I’m not saying it’s not, but I am saying
the format is already in use in the MySQL module.  My comment was more that
site1 will never be site2 on the same server, which was the point of
appending random numbers to the beginning of the mailing list email
addresses.

From: blueonyx-bounces at mail.blueonyx.it
[mailto:blueonyx-bounces at mail.blueonyx.it] On Behalf Of Stephanie Sullivan
Sent: Thursday, May 05, 2011 10:29 AM
To: 'BlueOnyx General Mailing List'
Subject: [BlueOnyx:07224] Re: Can't delete virtual sites since mailman

Ø  Using siteX insures you want run into a problem with “newcelebration.com”
and “newhopechurch.org”.  New is new, but site1 will never be site2.

Well, it might be if it’s CMU’d to another server

          -Stephanie

From: blueonyx-bounces at mail.blueonyx.it
[mailto:blueonyx-bounces at mail.blueonyx.it] On Behalf Of Darrell D. Mobley
Sent: Thursday, May 05, 2011 10:05 AM
To: 'BlueOnyx General Mailing List'
Subject: [BlueOnyx:07223] Re: Can't delete virtual sites since mailman

I can contribute to this:

I do something similar to what Dan is suggesting, but instead just use the
siteX parameter.

Sitex is already thrown in the MySQL database code to produce the default
“sitex_” as a prefix.  I prefer “sitex-“ but that is moot.  All my users are
created as “sitex”.  I have started instructing site admins they must adhere
to the “sitex-“ methodology when creating users, such as “sitex-user1”, etc.

Using siteX insures you want run into a problem with “newcelebration.com”
and “newhopechurch.org”.  New is new, but site1 will never be site2.

From: blueonyx-bounces at mail.blueonyx.it
[mailto:blueonyx-bounces at mail.blueonyx.it] On Behalf Of Dan Porter
Sent: Wednesday, May 04, 2011 6:50 PM
To: BlueOnyx General Mailing List
Subject: [BlueOnyx:07220] Re: Can't delete virtual sites since mailman

Michael, 

With regards the the prefix on mailman, let me throw this into the mix as I
do something similar for all of our hosting accounts... 

Right now, I manually assign a prefix to each hosting account.   That prefix
is used on all user names created under that specific account, very similar
to what you are using with the random number.  When an email address is
created, the user name is created with the prefix and then an email alias is
used with the actual name desired for the email address. 

Example: 

The hosting account www.mydomain.com I manually assign the prefix:  myd 
The email address of support at mydomain.com has the user name of myd-support
and the email alias of support 
The email address of support at mydomain.com has the user name of myd-news and
the email alias of news 

The hosting account www.example.com I manually assign the prefix:  exa 
The email address of support at example.com has the user name of exa-support
and the email alias of support 
The email address of support at example.com has the user name of exa-news and
the email alias of news 

Right now, I explain to the hosting customer that they MUST use this prefix
in front of any accounts they create.   If it happened automatically, it
would make life a little easier.  Having a field in the initial setup of the
hosting account called "Prefix" would be a simple way for this to happen
automatically.  Mailman could also use this as well to make sure there were
no duplicates.  Also, since the prefix is entered at the time of the hosting
account setup, it can be checked to be sure there are no other sites using
that prefix.   The admin would simply choose a different prefix for
www.mydomain.com and customer.mydomain.com, so there would be no conflict. 

Just my opinion but giving the admin the ability to choose their own prefix
is much nicer than a random number.   Keeping a unique prefix for the entire
hosting account keeps things simple and lets you sort information easily per
account. 

Dan Porter 
Twin Wolf Technology Group 

---------- Original Message ----------- 
From: Michael Stauber <mstauber at blueonyx.it> 
To: BlueOnyx General Mailing List <blueonyx at mail.blueonyx.it> 
Sent: Wed, 4 May 2011 17:41:55 +0200 
Subject: [BlueOnyx:07218] Re: Can't delete virtual sites since mailman 

> Hi David, 
> 
> > Now, regarding the automatic prefixing of the list names: I actually
think 
> > the first-come first-served approach would be preferable over the random

> > number prefix. I think that someone trying to use 'news at mydomain.com' as

> > the list name (and finding 'news' already in use) would rather accept a 
> > suggestion to use 'mydomain-news at mydomain.com' over being forced to
accept 
> > '284-news at mydomain.com' without a choice. I'd think most list creators 
> > would rather take a second or third try at coming up with a unique list 
> > name than having to accept a random number prefix. 
> > 
> > It's a lot like registering a domain name: I think most people would
like 
> > to creatively come up with their own unique variation rather than accept
a 
> > random number prefix. If I try to register 'mydomain.com' and it's
already 
> > taken, I don't want the registrar to randomly assign '8372-mydomain.com'

> > as my domain. I want to spend some time coming up with a unique 
> > alternative. 
> 
> Sure, that's a good suggestion and I'm thinking about implementing them,
as 
> I'm not entirely happy with the arbitrary prefix to mailman aliasses
either. 
> 
> Part of the problem there is the "conflict avoidance". Lets say we forego
the 
> prefix entirely and someone creates a mailing list named "support". In
that 
> case we need a check to see if there is already a list named "support"
with a 
> conflicting alias. But we also would need to check if there is another 
> "regular" email-alias or even a mailbox named "support" anywhere on the
box. 
> 
> Those checks require a bit of extra coding. Also, on boxes with many
accounts 
> these checks may take a while to go through, as a lot of CODB database
fields 
> need to be checked. But I'll look into it. 
> 
> The idea of using parts of the site name as prefix is also a nice. But say
you 
> have a site named" www.domain.com <http://www.domain.com/> " and another
one named 
> "customer.domain.com". In that case using just the name part of the FQDN
may 
> not be enough. 
> 
> So the best approach is proably to get a fully working check going to see
if 
> an unprefixed mailing list alias is possible, or if that name would cause 
> issues with already existing mailbox names, aliasses or list names. 
> 
> -- 
> With best regards 
> 
> Michael Stauber 
> _______________________________________________ 
> Blueonyx mailing list 
> Blueonyx at mail.blueonyx.it 
> http://mail.blueonyx.it/mailman/listinfo/blueonyx 
------- End of Original Message ------- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20110505/52e12129/attachment.html>