Forum Discussion

Alexander_Slink's avatar
Alexander_Slink
Icon for Altostratus rankAltostratus
Apr 20, 2017

APM email agent and VFRY command.

Hello everyone! In our environment we have smtp server on which blocked VRFY command and F5 device on which configured APM policy with email agent. F5 device can not sends messages using VRFY command:

220 smtp_server.example.com ESMTP
EHLO TEST_DEVICE
250-smtp_server.example.com
250-PIPELINING
250-SIZE 15728640
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
VRFY test_user@example.com
502 5.5.1 VRFY command is disabled
QUIT
221 2.0.0 Bye

How I can skip the VFRY command?

4 Replies

  • Hi : I have the same problem after v11 upgrade to v13

     

    B.R. Kevin.Y

     

  • I opened the support case and they provided me information that this is the bug: ID652146 "[APM] Email not sent because of VRFY change". In anticipation of HF.

     

  • Laudec's avatar
    Laudec
    Icon for Nimbostratus rankNimbostratus

    Also experiencing this issue. Opened a support case for the bug ID. Running 13.0.0 HF2

     

  • I verified I'm having this same issue. is the VRFY a new thing that it does in 13.0?

     

    Nevermind: I found the bug: https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnote-supplement-hotfix-bigip-13-0-0.htmlA652146-1

     

    652146-1 : Email agent does not send email if the remote server does not provide a 200 OK response to VRFY request. Component: Access Policy Manager

     

    Symptoms: Access Policy Email Agent does not send email if the remote server does not provide a 200 OK response to VRFY request.

     

    Conditions: The version of CURL included in 13.0.0 uses VRFY requests to confirm recipients are valid before sending mail. Many servers consider VRFY a potential leak of information and will respond "252 - Not verified" and the BIG-IP system will not send the message.

     

    Impact: The Access Policy Email Agent does not send mail messages or log an error about mail not being sent.

     

    Workaround: None.