The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

Hi again,

Le 03/10/12 16:19, christopher pax a écrit :

is is some examples of our configuration

/etc/sympa.conf
## Main robot hostname
domain  lists.example.com


lists.example.com sympa_alias entry:
crazylist: "| /home/sympa/bin/queue address@concealed"


vhost directory:
/home/sympa/etc/example.com/
robot.conf


example.com sympa_alias entry:
board: "| /home/sympa/bin/queue address@concealed"
OK. This is normal configuration, but risky as any alias is copletely local, without any notion of domain. See below.



It is clear to me, I may have set things upin the wrong way. If i defined a list on the lists.example.com robot with the same name as one on the example.com robot, the moderation release would go to the one defined on lists.example.com.
When you have two robots, you can have two lists with the same name, one on each robot.
The separation at the alias level depends on your MTA.

For example, with sendmail, we use the virtusertable. It is activated through the " FEATURE(virtusertable)" configuration option.

Let's say that lists.example.com is the default domain on your server, then you add the following to the virtusertable file:

@example.com    example.com-%1%3

Then each address for the domain example.com will be declared like this:

example.com-localpart

In your examples, you would have the following alias:

example.com-board: "| /home/sympa/bin/queue address@concealed"

I was under the assumption that sympa would be able to under stand which list to work with via the sympa_alias file.
Yes it will and it certainly does. However, you had troubles with the moderation process, i.e. the processing of your "quiet distribute" command. Considering that the mails to the lists on each robot are probably well routed (as you clearly use each domain in the aliases), it is likely that the command was misguided.

In the aliases, you're supposed to configure the sympa command alias as well.

Please check what you defined for address@concealed and address@concealed.

Theoretically, if you didn't change the name of the sympa mail command local part in your configs, you're supposed to have something like this (in the case you're using sendmail with the virtusertable option and lists.example.com is the default mail domain on the server):

sympa    "| /home/sympa/bin/queue address@concealed"
example.com-sympa    "| /home/sympa/bin/queue address@concealed"

This way, you're sur any command sent to sympa will be forwarede to the right robot.

Regards,

David

if there are more configurations you need to see, let me know.

On Wed, Oct 3, 2012 at 9:51 AM, David Verdin <address@concealed> wrote:

Hi Christopher,

I don't get it. You have two robots in one server, right?

What is the difference between example.com and lists.example.com?

The error looks like you sent a moderation message to the wrong robot. When you have two robots, you must have two sympa service aliases (address@concealed and address@concealed).
If you send to address@concealed a moderation message for a list located on lists.example.com, it won't work.

Please elaborate a little, because I really don't understand what your problem is exactly.

Cheers,

David

Le 03/10/12 15:16, christopher pax a écrit :

The lists that I have setup to be moderated do not work.

I have two two robot, one for our main site example.com and one for the list server itself lists.example.com.

with the way our mail works, we need a ldap alias to direct mail to the server. so mail has to be sent to lists.example.com even though they are defined on the example.com robot. 

I get the following error when releasing a message in the moderation queue:

Oct  3 09:14:45 sydlpr1 sympa[8594]: Commands::parse() Parsing: QUIET DISTRIBUTE a_test_list 69f6fe8e4890a0948a5c75e7b240adeb 

Oct  3 09:14:45 sydlpr1 sympa[8594]: Message::new() Cannot open message file /home/sympa/spool/moderation/a_test_list_69f6fe8e4890a0948a5c75e7b240adeb.distribute : No such file or directory 

Oct  3 09:14:45 sydlpr1 sympa[8594]: Commands::distribute() Commands::distribute(): Unable to create Message object /home/sympa/spool/moderation/a_test_list_69f6fe8e4890a0948a5c75e7b240adeb.distribute 

please help, this is a critical feature to us.

thanks.

Attachment: smime.p7s
Description: Signature cryptographique S/MIME