Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error_performing_condition in scenario #836

Closed
pascalmaes opened this issue Dec 27, 2019 · 10 comments
Closed

error_performing_condition in scenario #836

pascalmaes opened this issue Dec 27, 2019 · 10 comments

Comments

@pascalmaes
Copy link

I get the error error_performing_condition when I manage a list
See the log file:

logfile.txt

Version

Sympa version 6.2.52

Installation method

From source

Expected behavior

No error

Actual behavior

As said: an error_performing_condition

Additional information

The content of send.private is the default one
send.private.txt

@ikedas
Copy link
Member

ikedas commented Dec 28, 2019

Hi @pascalmaes,

Sympa/Scenario.pm in your Sympa looks modified. Please rewind all of your changes and check if the problem will be reproduced.

@pascalmaes
Copy link
Author

pascalmaes commented Dec 28, 2019

It is not as I have installed the version 6.2.52 from the sources:

  • configure
  • make
  • make install
  • cpanm --installdeps --with-recommends .
  • /var/sympa/bin/sympa.pl --upgrade
# diff sympa-6.2.52/src/lib/Sympa/Scenario.pm /var/sympa/bin/Sympa/Scenario.pm
#
# ls -l /var/sympa/bin/Sympa/Scenario.pm
-rw-r--r-- 1 root root 58717 Dec 27 16:51 /var/sympa/bin/Sympa/Scenario.pm

@ikedas
Copy link
Member

ikedas commented Dec 28, 2019

I don’t know why Sympa was installed under /var/sympa instead of /home/sympa without “—prefix” configure option.

BTW do you filter the log? If you did, please show us entire logs.

@pascalmaes
Copy link
Author

Here is the script I"m using to configure Sympa:
configure.txt

I give the log file from the starting of Sympa and Apache2 to the error

@pascalmaes
Copy link
Author

Hello,

The problems comes from the scenario include.send.header
It contains:

equal([is_bcc], 1) smtp,dkim,md5,smime -> request_auth

If I delete the scenario, all is going well; if the scenario exists, I have the error:

Jan 18 10:46:40 sympa-test.sipr.ucl.ac.be wwsympa[28411]: info Sympa::Scenario::authz() Error in scenario Sympa::Scenario <send.newsletter;/var/sympa/default/scenari/send.newsletter>, context Sympa::List test-sympa-4@listes.uclouvain.be: (error-performing-condition)

@pascalmaes
Copy link
Author

The problem is related to "is_bcc".

If I don't use the include; send.header scénario but I choose the public_nobcc, I have the same error:

Jan 18 11:05:45 sympa-test.sipr.ucl.ac.be wwsympa[30460]: info Sympa::Scenario::authz() Error in scenario Sympa::Scenario <send.public_nobcc;/var/sympa/default/scenari/send.public_nobcc>, context Sympa::List test-sympa-4@listes.uclouvain.be: (error-performing-condition)

@pascalmaes
Copy link
Author

pascalmaes commented Jan 19, 2020

To be sure, I have reinstall Sympa 6.2.52 from nothing:

# ./configure --prefix=/var/sympa --with-confdir=/etc/sympa --with-perl=/usr/bin/perl --with-user=sympa --with-group=sympa --with-postalias=/usr/sbin/postalias --with-postmap=/usr/sbin/postmap
# make
# make install

I create a list (newsletter) and the I change the sending mode to public_nobcc; you will fin de log file as attachment
sympalog.txt

@ikedas
Copy link
Member

ikedas commented Jan 20, 2020

Reported problem is slightly similar to #841 (though I don't know why "err" log entries aren't shown in your bug report). @pascalmaes, could you please apply this patch, restart Sympa services and web service and check if the problem will be solved?

@ikedas ikedas added the bug label Jan 20, 2020
@pascalmaes
Copy link
Author

Hello,

It works fine with the patch.

Thanks

@ikedas
Copy link
Member

ikedas commented Jan 20, 2020

Thanks for confirming! This issue is closed as a duplicate of #841.

@ikedas ikedas closed this as completed Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants