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.

Sign up for GitHub

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

Jump to bottom

Family signoff does not work #691

Closed
jth56000 opened this issue Jul 12, 2019 · 62 comments
Closed

Family signoff does not work #691

jth56000 opened this issue Jul 12, 2019 · 62 comments
Labels
question

Comments

@jth56000
Copy link

Version

6.2.22

Installation method

RedHat Rpm package

Expected behavior

We have list from family lists, when a user signoff it should no more receive mail from the family he signoff.

Actual behavior

When a user signoff a family of lists, the entry is correctly created in exclusion_table.
But the user still receive mail from the family lists he signoff.

Additional information

None
@ikedas
Copy link
Member

ikedas commented Jul 12, 2019

Hi @jth56000,

When a user signoff a family of lists, the entry is correctly created in exclusion_table.
But the user still receive mail from the family lists he signoff.

Could you please see "review subscribers" page and check whether that user is still subscribed to that list or not?

@jth56000
Copy link
Author

Hello Ikedas,

The user is still subscribed to the list when signoff from the family lists.

Regards,
Jean

@ikedas
Copy link
Member

ikedas commented Jul 16, 2019

@jth56000, could you show us Sympa's log during operation for signoff?

@jth56000
Copy link
Author

jth56000 commented Jul 16, 2019 via email •
edited by ikedas
Loading

@jth56000
Copy link
Author

jth56000 commented Jul 16, 2019 via email

@jth56000
Copy link
Author

jth56000 commented Jul 16, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 17, 2019

@jth56000, when deletion of the user was requested, the user or the owner would receive a confirmation message. Do they followed instruction described in that message?

@jth56000
Copy link
Author

jth56000 commented Jul 17, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 18, 2019

How did they follow the instruction? Could you please describe in details? I.e.: "They visited a page (URL), clicked (label) button, and..."

@jth56000
Copy link
Author

jth56000 commented Jul 18, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 19, 2019

Hi @jth56000,

Can you access to the database? If you can, could you please execute this SQL statement:

SELECT subscribed_subscriber, included_subscriber, include_sources_subscriber
FROM subscriber_table
WHERE user_subscriber = '(E-mail of the user)' AND
      list_subscriber = '(List name)' AND
      robot_subscriber = '(Domain name of the list)';

and show us the result?

@jth56000
Copy link
Author

jth56000 commented Jul 19, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 19, 2019

naej does not unsubscribe from test-jean+all-14-all-all list, because they have been subscribed instead of included.
jean.thomas will unsubscribe from the list after some time (1 hour or so). Could you please wait for a while?

Though I don't know whether this behavior is defined feature or not, Sympa looks deleting only included members with family_signoff.

@jth56000
Copy link
Author

jth56000 commented Jul 19, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 19, 2019

@jth56000,

What is result of this?

SELECT subscribed_subscriber, included_subscriber, include_sources_subscriber,
date_subscriber, update_subscriber
FROM subscriber_table
WHERE user_subscriber = '(E-mail of the user)' AND
      list_subscriber = '(List name)' AND
      robot_subscriber = '(Domain name of the list)';

And, does inclusion (sync_include task) successfully executed? Please show us the log about task_manager.

@jth56000
Copy link
Author

jth56000 commented Jul 19, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 23, 2019

@jth56000,

What is the result of this?

SELECT subscribed_subscriber, included_subscriber, include_sources_subscriber,
date_subscriber, update_subscriber
FROM subscriber_table
WHERE user_subscriber = '(E-mail of the user)' AND
      list_subscriber = '(List name)' AND
      robot_subscriber = '(Domain name of the list)';

@jth56000
Copy link
Author

jth56000 commented Jul 23, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 23, 2019 •
edited
Loading

Hi Ikeda, Here is the result of the request :

+-----------------------+---------------------+----------------------------+---------------------+---------------------+
| subscribed_subscriber | included_subscriber | include_sources_subscriber | date_subscriber | update_subscriber |
+-----------------------+---------------------+----------------------------+---------------------+---------------------+
|                     0 |                   1 | 80273f3f                   |  2019-07-03 16:26:20 | 2019-07-03 16:26:20 |
+-----------------------+---------------------+----------------------------+---------------------+---------------------+

Jean

Please check if

  • task_manager.pl is running,
  • and list synchronization (sync_include) is performed successfully.

@jth56000
Copy link
Author

jth56000 commented Jul 23, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 23, 2019

List synchronization is performed manually successfully.

To confirm synchronization was performed successfully, please show us the log during synchronization.

@jth56000
Copy link
Author

jth56000 commented Jul 23, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 24, 2019

Is email of the user included in the file /datasan/sympa/abonnes/test-signoff.txt?

@jth56000
Copy link
Author

jth56000 commented Jul 24, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 24, 2019 •
edited
Loading

Hi @jth56000,

Okey, then, please repeat everything written on this issue page, and let us know everything happened.

I honestly feel your answers so far are sometimes fragmentary, and it is hard for me to understand what happened.

@jth56000
Copy link
Author

jth56000 commented Jul 24, 2019 via email

@jth56000
Copy link
Author

jth56000 commented Jul 24, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 24, 2019

Could you please repeat? Or, we’ll find the problem by ourselves.

@jth56000
Copy link
Author

Let's resume the situation
On my server 6.2.22 I have Family of lists such as jean-test with at least one list named jean-test+ir-04-2-c
In this list subscribers are included by a file /datasan/sympa/abonnes/test-signoff.txt
One of the subscribers called [email protected] signoff the family.
This subscriber is not deleted from the list but an entry was created in exclusion_table so he should no more receive email from this family but he does.
All process are correctly started on the server.
Synchronisation is performed successful.
The following request
mysql> SELECT subscribed_subscriber, included_subscriber, include_sources_subscriber, date_subscriber, update_subscriber
-> FROM subscriber_table
-> WHERE user_subscriber = '[email protected]'
-> AND list_subscriber = 'jean-test+ir-04-2-c'
-> AND robot_subscriber = 'services.cnrs.fr';
Gives
+-----------------------+---------------------+----------------------------+---------------------+---------------------+
| subscribed_subscriber | included_subscriber | include_sources_subscriber | date_subscriber | update_subscriber |
+-----------------------+---------------------+----------------------------+---------------------+---------------------+
| 0 | 1 | 244728ab | 2019-07-23 08:33:08 | 2019-07-23 08:33:08 |
+-----------------------+---------------------+----------------------------+---------------------+---------------------+
The issue was reproduced by David VERDIN last year during SYMPA learning session in Montpelier, the SYMPA released used was 6.2.32

@racke
Copy link
Contributor

racke commented Jul 24, 2019

Included subscribers which unsubscribe are noted in the exclusion_list. So how does the entry in table looks for your case?

@jth56000
Copy link
Author

jth56000 commented Jul 25, 2019 via email

@jth56000
Copy link
Author

jth56000 commented Jul 25, 2019 via email

@ikedas
Copy link
Member

ikedas commented Jul 28, 2019

This problem possiblly can be solved by #693. If you can wait for the next release, you may check if the problem will be solved with current beta, 6.2.45b.2.

@jth56000
Copy link
Author

jth56000 commented Jul 30, 2019 via email

@ikedas
Copy link
Member

ikedas commented Aug 14, 2019

You may use COPR sympa-beta repository to check the beta. Please see the description for more details.

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@ikedas
Copy link
Member

ikedas commented Aug 19, 2019 

err main::#914 > Sympa::Upgrade::update_version#91 Unable to write /etc/sympa/data_structure.version; sympa.pl needs write access on /etc/sympa directory: Permission non accord▒e

Please check if /etc/sympa has appropriate permission: Readable by sympa user.

#sympa.pl --upgrade --from 6.2.22 --to 6.2.45-0.1.b.2

Instead, please run:

#sympa.pl --upgrade --from 6.2.22 --to 6.2.45b.2

@racke
Copy link
Contributor

racke commented Aug 19, 2019

Also check that /etc/sympa/data_structure.version is present and writable by Sympa.

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@ikedas
Copy link
Member

ikedas commented Aug 19, 2019 

Upgrade process finished

Upgrade has properly finished. The other errors you reported seem ignorable.

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@racke
Copy link
Contributor

racke commented Aug 19, 2019

Make sure that you don't have stale WWSympa processes running and also check the sympa logs.

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@racke
Copy link
Contributor

racke commented Aug 19, 2019

That's odd - what's at line 2456 in wwsympa.fcgi (and around that) ?

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@ikedas
Copy link
Member

ikedas commented Aug 19, 2019

escape_quote filter has been deprecated. You should repeal customization of templates (if you have customized them), and apply them again.

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@ikedas
Copy link
Member

ikedas commented Aug 19, 2019

At least the customization you showed is not required for recent version of Sympa.

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@jth56000
Copy link
Author

jth56000 commented Aug 19, 2019 via email

@jth56000
Copy link
Author

jth56000 commented Aug 20, 2019 via email

@ikedas
Copy link
Member

ikedas commented Aug 20, 2019 •
edited
Loading

@jth56000,

Please tell us ---

  • what you expected,
  • what you did (configuration in details, operation step by step, ...),
  • and what you see (log, screenshot, ...).

@jth56000
Copy link
Author

jth56000 commented Aug 20, 2019 via email

@ikedas
Copy link
Member

ikedas commented Aug 21, 2019

Configuration? Log? Shots?

@jth56000
Copy link
Author

jth56000 commented Aug 21, 2019 via email

@ikedas
Copy link
Member

ikedas commented Aug 22, 2019

I think the un-subscription is not immediate, it needs the list from the family to re-synchronized members to exclude subscribers who are marked as excluded in exclusion_table, am I right ?

You are right. As I wrote in 19th Jul., synchronization will complete after some time (1 hour or so), and users have to wait for a while.

@ikedas
Copy link
Member

ikedas commented Sep 18, 2019

Okey, I see the problems look being solved. This issue is closed by now.

@ikedas ikedas closed this as completed Sep 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@racke @ikedas @jth56000