Unable to send mail: ERROR 550 - Verification failed for SRS0=HHH=TT=example.org=sender@example.com invalid sender

Follow

Comments

13 comments

  • Avatar
    Plesk

    It seems there is an error in this KB

    Item 5:

    # chmod 755 /usr/lib/plesk-9.0/postfix-local
    # chown popuser:popuser /usr/lib/plesk-9.0/postfix-local

    should be:

    # chmod 755 /usr/lib64/plesk-9.0/postfix-local
    # chown popuser:popuser /usr/lib64/plesk-9.0/postfix-local

     

    0
    Comment actions Permalink
  • Avatar
    Bulat Tsydenov

    Thank you for bringing this to our attention. The article has been changed accordingly.

    0
    Comment actions Permalink
  • Avatar
    Plesk

    Is the postfix-local for Debian 8 also usable for Ubuntu?

    0
    Comment actions Permalink
  • Avatar
    Nikolay Zhmuk

    Yes, it is, patch for Debian 8 is applicable for Ubuntu 16.04

    0
    Comment actions Permalink
  • Avatar
    Michel Otte (Edited )

    While it's nice to have a fix in place for 17.5.x, the micro updates of Plesk will eventually override the patched postfix-local, unless you block updates for the whole plesk-mail-pc-driver RPM package in the masin section of the /etc/yum.conf like so:

    exclude=plesk-mail-pc-driver*
    0
    Comment actions Permalink
  • Avatar
    Artyom Baranov

    @Michel Otte,

    By blocking updates you may miss some important update.

    There is another way - create a cron task that will be executed after each Daily Maintenance task to re-apply the fix.

    0
    Comment actions Permalink
  • Avatar
    Oxilion (Edited )

    The compilation failed of postsrsd on CentOS/CloudLinux 7. gcc also has to be installed for this to work so make sure it's installed:

     

    yum install -y unzip cmake gcc

     

    0
    Comment actions Permalink
  • Avatar
    Oxilion

    You can add something like this to your cronjob as a way to keep updates available but reset the fix if the postfix-local is overwritten.

    diff /root/postfix-local /usr/lib64/plesk-9.0/postfix-local || (cp -f /root/postfix-local /usr/lib64/plesk-9.0/postfix-local && service postfix restart)

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @Oxilion

    Hi!
    Thank you for sharing these hints.

    They may be useful for other Pleskians.

    0
    Comment actions Permalink
  • Avatar
    Lenor

    I have the Same Problem today, but with:

    Debian 8.11
     

    Plesk Onyx 
    Version 17.8.11 Update #39 !!!

     

    Double checked

    1
    Comment actions Permalink
  • Avatar
    Alexandr Redikultsev

    Hi @Lenor,

    In case you are seeing the same error and SRS is rewriting correctly (I mean that the error message is false positive), then I would recommend checking the following article:

    https://support.plesk.com/hc/en-us/articles/115002925609-Mail-forwarding-does-not-work-Recipient-address-rejected-User-unknown-in-virtual-mailbox-table 

     

    In case it will not help either, please submit a support request: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support- 

    0
    Comment actions Permalink
  • Avatar
    Lenor

    @Alexandr. 

    how can i fix this? turning off SRS seems not good, as we usually would like not to reduce functions but to fix Problems. 

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Lenor,

    Am I correct the article https://support.plesk.com/hc/en-us/articles/115002925609-Mail-forwarding-does-not-work-Recipient-address-rejected-User-unknown-in-virtual-mailbox-table%C2%A0 suits your conditions?

    The cause there is that SRS is not enabled on relay host side.

    That's why the ideal resolution is to enable acceptance of SRS emails from Plesk on the relay host, so it should be resolved at relay host side.

     

    In case it would not help, the additional investigation will be required, please, submit a support request: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support- 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request