[solved by reinstalling] zimbraMtaSmtpdRejectUnlistedRecipient and zimbraMtaSmtpdRejectUnlistedSender not working

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
User avatar
mcdaniels
Posts: 34
Joined: Thu Aug 03, 2023 4:42 pm

[solved by reinstalling] zimbraMtaSmtpdRejectUnlistedRecipient and zimbraMtaSmtpdRejectUnlistedSender not working

Post by mcdaniels »

Hi,

If I try to:

Code: Select all

sudo -u zimbra zmprov mcf zimbraMtaSmtpdRejectUnlistedRecipient yes
sudo -u zimbra zmprov mcf zimbraMtaSmtpdRejectUnlistedSender yes
My system tells me that the attribute is invalid:

Code: Select all

ERROR: account.INVALID_ATTR_NAME (invalid attr name: invalid attr name - unable to modify attributes: ldap host=myhost:389: entry update failed)
So I wonder whether the two attributes above are false for Zimbra V10 although they are mentioned here: https://wiki.zimbra.com/wiki/Rejecting_ ... _and_above

On the other handside if I

Code: Select all

sudo -u zimbra ./zmprov desc -a zimbraMtaSmtpdRejectUnlistedRecipient
it gives me:

Code: Select all

/opt/zimbra/bin# sudo -u zimbra ./zmprov desc -a zimbraMtaSmtpdRejectUnlistedRecipient
zimbraMtaSmtpdRejectUnlistedRecipient
    Value for postconf smtpd_reject_unlisted_recipient

               type : enum
              value : yes,no
           callback : 
          immutable : false
        cardinality : single
         requiredIn : 
         optionalIn : server,globalConfig
              flags : serverInherited
           defaults : no
                min : 
                max : 
                 id : 1534
    requiresRestart : 
              since : 8.5.0
    deprecatedSince : 
I even get the active parameters of these variables:

Code: Select all

prov> gcf zimbraMtaSmtpdRejectUnlistedSender
zimbraMtaSmtpdRejectUnlistedSender: no
prov> gcf zimbraMtaSmtpdRejectUnlistedRecipient
zimbraMtaSmtpdRejectUnlistedRecipient: no
so it is available

Update: I am just setting up a fresh 10.0.2 on a vm and try to use the command above... I keep this updated, hoping someone can give me a hint. ;-)

Update2: Unfortunatly I have to tell you, that the command is working in the new installed vm... Hm... Perhaps its because I updated from 8.8.15 to 10.0.2, I don't know.

This is definitly very disappointing, cause I am looking forward to reinstall the whole server, if there is no solution.

Update 3: Reinstalled the whole server now with 10.0.2 and the commands work like a charm. I don't know what happened to my other installation (we will problably never discover). I think it may be related to the inplace - update of 8.8.15 - FOSS to 10.0.2 FOSS.
Post Reply