Distribution Lists

[JoC]

Is there a way to create a distribution list with external email addresses?

[ryocoon]

Do you want to create a distribution list with email addresses that are outside of your scalix server, or do you want to create one that has (as its own) an email address that is not within the domain scope that is not that of your scalix server?

You would have to be a little more specific or give an example I think.

If you want to just add external addresses to a distribution mailing list, you can do so with the CLI commands. Easiest thing to do is to create Directory Entries using "omaddent" and include an internet address in the "-e" part of the command string that matches the external recipient. I use this for some distribution lists that mail to outside contacts and clients.

for example:

Code: Select all

omaddent -e "G=Joe/S=ExternalUser/cn=Joe ExternalUser/ou1=internet/ia=jextuser@somewhere_else.tld"

(gah.. silly autowrapping in the edit area >_< should be one command line)

That would add a directory entry with the name of "Joe ExternalUser" in your public contact directory (you can hide it from casual directory browsing with some other x.400 switches, but it will show up in searches still). You can then add that directory entry easily to your Distribution List.

I'm not sure if you can directly add an inline email address to an "ommodpdln" command set or not as I haven't tried it. I have been using directory entries to keep tabs on what email address is what as well as track what Distribution Lists I have them in.

The external directory entries and distribution lists functioned much like this in Exchange as well, but I remember Gui portions for handling them (although CLI is much more scriptable for large modify jobs and therefor more handy in my case).

[jaime.pinto]

Go to sac and create an internet user with the external email. You have the option to make it display or not in your contact list.

Then, still from sac, create a new group (the dist list) and add the internet user to it, hence, the external user. You can add as many internal or external users you want.

Outlook itself has its own tools to create dist lists independently of Scalix, that can be exported or shared amongst other OL users on the same server, just by making them available on the shared folders.

[eddieedwards]

It is frustrating to have to create and manage users in SAC when all I want to do is add an e-mail address to a mailing list. Most lists I create have to exist on the server (and not simply Outlook DLs) since automated reports and whatnot are sent to these lists from other servers. It would be simpler to just add addresses to a list without the overhead of actual users--even if they are "Internet" users.

Grrr...

[jaime.pinto]

I'm inclined to agree with you, but that is the *Billy Gates* way. Scalix just emulates it.

In the pre-scalix days I'd just edit the /etc/aliases file, add the email (whichever one), save, type newaliases and it was done. I could always see very quickly who was part of a dist list, and I had scripts that would make that available to any user on our intranet, just by massaging the data on the /etc/aliases file.

There may be some sxaa utility or om script to do the same from a shell, but still it's very hard for other users to be let know who is included on a dist list in scalix.

[eddieedwards]

Do you happen to know the om syntax for adding an Internet user? I have a lot to add and would like to script it instead of mousing my way through SAC...

[eddieedwards]

I believe I found it here:

http://www.scalix.com/community/viewtopic.php?t=138

Now, to script the group and a way to leave it out of the directory...

[mikevl]

Hi Eddie

You CAN create them in Outlook if you wish
Remember your Outlook rules are server based and survive while Outlook is not running. So.

If you create a rule to send a mail to adistributionlist@abc.com and you are a member of that list then your Outlook rule would be.
Condition=sent to people or distribution list = adistributionlist@abc.com
Action=forward to people or distribution list= ????
and add the names you want.

Easy

Mike

[eddieedwards]

Two things:

1. It was my understanding that rules written in Outlook are client-side only and if OUtlook is not running, the rules will not be applied. Rules created under SWA, however, are server-side.
2. A rule written the way you say would need to be filtered on the subject or something to work, and I would still need to make my automated scripts send mail to one user and hope that user has their distro list set up properly. Makes more sense to have the script send straight to a pre-defined DL.

[mikevl]

1) Your understanding may have been in error.

2) If your intention is to redistribute mail which is sent to a particular address to a number of people on a distribution list then the methode above is simple. If you need to seperate messages out by Subject of some text within the body of the message then Outlook rules can still easily do tghe job.

As with any software if your preference is to write some piece of code to do a particular job then this is also a great way of doing what you wish to achieve.

Mike

[eddieedwards]

1. Not in error, but from reading posts like this: viewtopic.php?t=6271&highlight=clientside+rules, it appears that there is no longer such a disparity between rules created in Outlook and those in SWA. Back when I started with version 10, there was a huge difference.

2. You misunderstand my point, but that is OK. Thanks for your input.

[mikevl]

Hi Eddie

I have been using Scalix rules from whe Scalix first came on the market. I have found no issues with them ever. Ok some of the rules created in Outlook may not be visible in SWA but is that the issue. You asked for an easier way to distribute mail to a number of users. The method I gave you does this. The method you suggested of creating scripts to do the job also has downsides.

There are many methods you can use. It would take a long time for met to type them all in as I am but a 2 fingured typest.

You choose

Mike

[eddieedwards]

I don't want to argue with you about it. It is not worth it. I am not the original poster of this topic. My point was in regards to the way PDLs are set up within Scalix, not looking for different ways to achieve the same thing through rules/filters. Thank you again for your input.