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

do you know what all the folders/file permissions/owners should be for alias address processing to work? (alias addresses not being created for new lists since the OS was updated) #1834

Closed
SympaNovice opened this issue May 9, 2024 · 0 comments
Labels

Comments

@SympaNovice
Copy link

Since the OS on the listserver was updated, the sympa aliases are no longer being automatically created for any new lists.
This means that when a user sends to a new sympa list, the email is not delivered as the list address in the maillog is seen as 'User unknown'

Version

Sympa 6.2.68

Installation method

manually

Expected behavior

Alias addresses used by sympa should be automatically created on the creation of a new list on the sympa listserver through the web ui

Actual behavior

Since the OS on the listserver was updated, the sympa aliases are no longer being automatically created for any new lists.
This means that when a user sends to a new sympa list, the email is not delivered as the list address in the maillog is seen as 'User unknown' (see excerpt from maillogs below).

Apr 29 12:41:36 listserver sendmail[4242]: 43TBfaji004242: [email protected]... User unknown

As the sender is not notified that delivery has failed, the sender is under the impression their message has been delivered to the group when it hasn't.

I have resolved for a particular new list by logging in as root to the listserver and manually running the command to add the sympa alias addresses to the new list e.g. /home/sympa/bin/alias_manager.pl add mynewlist mydomain.com

Something has changed since the update to cause this issue...I'm thinking it may be permissions to directories/user rights to files

Qs. Would you know what all the folders/file permissions/owners should be or is there any way of finding out what could have changed?

Any help would be greatly appreciated. Thanks

Additional information

Note:
OS Version: Red Hat Enterprise Linux Server release 7.9 (Maipo)
Sympa Version: Sympa 6.2.68

Current permissions:
/home/sympa/default/
-rw-r--r-- 1 root root 436 Apr 7 2022 ldap_alias_entry.tt2
-rw-r--r-- 1 root root 646 Jul 13 2022 list_aliases.tt2

/etc/mail/
-rw-r--r-- 1 root root 0 Feb 29 15:15 aliasesdb-stamp
-rw-r--r-- 1 sympa sympa 2663489 May 8 14:37 sympa_aliases
-rw-r--r-- 1 sympa sympa 5218304 May 8 15:31 sympa_aliases.db

/home/sympa/bin/
-rwxr-xr-x 1 sympa sympa 5417 Apr 7 2022 alias_manager.pl
-rw-r--r-- 1 root root 734 May 8 12:02 $SENDMAIL_ALIASES
-rwxr-xr-x 1 sympa sympa 7278 Apr 7 2022 sympa_newaliases.pl
-rwxr-x--- 1 sympa sympa 10760 Apr 7 2022 sympa_newaliases-wrapper

@SympaNovice SympaNovice changed the title Sympa listserv not creating alias addresses for new lists since the OS was updated do you know what all the folders/file permissions/owners should be for alias address processing to work? (alias addresses not being created for new lists since the OS was updated, ) May 21, 2024
@SympaNovice SympaNovice changed the title do you know what all the folders/file permissions/owners should be for alias address processing to work? (alias addresses not being created for new lists since the OS was updated, ) do you know what all the folders/file permissions/owners should be for alias address processing to work? (alias addresses not being created for new lists since the OS was updated) May 21, 2024
@ikedas ikedas closed this as completed Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants