You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using version 1.7.0 and encountering an issue with the SMS number truncate option. Despite enabling this setting, it doesn't seem to trim the SMS number as expected.
Our system is connected to an LDAP database where mobile numbers are stored in the 'mobile' attribute in the format 1-555-555-5555. The relevant section of my configuration is as follows:
sms_sanitize_number works as expected, removing hyphens (-) from the numbers. However, sms_truncate_number does not trim the number length to 10 digits. Instead of sending emails to [email protected], it sends them to [email protected], causing delivery to fail. Adjusting sms_truncate_number_length to other values (e.g., 9) does not seem to impact the behavior.
Modifying the LDAP mobile number format is not feasible, as it’s used consistently for email signatures.
Any insights or guidance on how to resolve this issue would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered:
I am using version 1.7.0 and encountering an issue with the SMS number truncate option. Despite enabling this setting, it doesn't seem to trim the SMS number as expected.
Our system is connected to an LDAP database where mobile numbers are stored in the 'mobile' attribute in the format 1-555-555-5555. The relevant section of my configuration is as follows:
sms_sanitize_number works as expected, removing hyphens (-) from the numbers. However, sms_truncate_number does not trim the number length to 10 digits. Instead of sending emails to [email protected], it sends them to [email protected], causing delivery to fail. Adjusting sms_truncate_number_length to other values (e.g., 9) does not seem to impact the behavior.
Modifying the LDAP mobile number format is not feasible, as it’s used consistently for email signatures.
Any insights or guidance on how to resolve this issue would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: