How to identify if CA API Portal 4.2 internal SMTP server works fine

Document ID : KB000111612
Last Modified Date : 20/08/2018
Show Technical Document Details
Introduction:
As new users register with the CA API Portal 4.2, a registration email would go out to that user to follow on and logon to the Portal.

Sometimes, users wait a long time for that email or don't even receive it.

How to identify if the Internal SMTP on the Portal is working fine?
(Provided we have not configured an external SMTP Mail Server to be used)
Environment:
CA API Portal 4.2.x configured with Internal OOTB SMTP Mail.
Instructions:
One can inspect the internal SMTP container on the portal to verify its mail log and see if any request is hanging there or the delay is outside the Portal.

Using the below command:

docker exec -it $(docker ps --format "{{.ID}}" --filter name=smtp) tail -f /var/log/mail.log

One can see how the internal SMTP (Postfix) is processing the needed requests/emails:

2018-08-15T06:22:23.564212+00:00 smtp postfix/smtpd[20843]: connect from portal_pssg.7o2rckidaq4nw8shoteyaxx4w.8w5a6oxyctgk9xqbzmxdmhb16.portal_private[10.0.0.8]
2018-08-15T06:22:23.805799+00:00 smtp postfix/smtpd[20843]: Anonymous TLS connection established from portal_pssg.7o2rckidaq4nw8shoteyaxx4w.8w5a6oxyctgk9xqbzmxdmhb16.portal_private[10.0.0.8]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
2018-08-15T06:22:23.862064+00:00 smtp postfix/smtpd[20843]: using backwards-compatible default setting mynetworks_style=subnet to permit request from client "portal_pssg.7o2rckidaq4nw8shoteyaxx4w.8w5a6oxyctgk9xqbzmxdmhb16.portal_private[10.0.0.8]"
2018-08-15T06:22:23.862112+00:00 smtp postfix/smtpd[20843]: using backwards-compatible default setting mynetworks_style=subnet to permit request from client "portal_pssg.7o2rckidaq4nw8shoteyaxx4w.8w5a6oxyctgk9xqbzmxdmhb16.portal_private[10.0.0.8]"
2018-08-15T06:22:23.915375+00:00 smtp postfix/smtpd[20843]: D6E0D1C1629: client=portal_pssg.7o2rckidaq4nw8shoteyaxx4w.8w5a6oxyctgk9xqbzmxdmhb16.portal_private[10.0.0.8]
2018-08-15T06:22:23.916476+00:00 smtp postfix/cleanup[21414]: D6E0D1C1629: message-id=<1407666840.2.1534314143554.JavaMail.noreply@<portal>.<domain>>
2018-08-15T06:22:23.952066+00:00 smtp postfix/qmgr[115]: D6E0D1C1629: from=<noreply@<portal>.<domain>>, size=938, nrcpt=1 (queue active)
2018-08-15T06:22:27.016914+00:00 smtp postfix/smtp[21415]: D6E0D1C1629: to=<user-email@user-email-domain>, relay=mail.domain[130.200.94.252]:25, delay=3.2, delays=0.09/0.12/1.9/1, dsn=2.6.0, status=sent (250 2.6.0 <1407666840.2.1534314143554.JavaMail.noreply@<portal>.<domain>> [InternalId=27492085662315, Hostname=MAILSRV.domain] Queued mail for delivery)
2018-08-15T06:22:27.017485+00:00 smtp postfix/qmgr[115]: D6E0D1C1629: removed
2018-08-15T06:22:30.712956+00:00 smtp postfix/smtpd[20843]: disconnect from portal_pssg.7o2rckidaq4nw8shoteyaxx4w.8w5a6oxyctgk9xqbzmxdmhb16.portal_private[10.0.0.8] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 commands=6
2018-08-15T06:22:32.128128+00:00 smtp postfix/smtpd[20843]: connect from localhost[127.0.0.1]
2018-08-15T06:22:32.128257+00:00 smtp postfix/smtpd[20843]: lost connection after CONNECT from localhost[127.0.0.1]
2018-08-15T06:22:32.128277+00:0


So we can see how the email is processed.

If one see errors in the mail.log - please contact CA Support to get help in resolving such errors.