Sure, it is established that there is a desire to send/receive data – using email for some reason. Why email? What is the process that would use email doing?
Email is not typically used for automated integrations. It can be (there are even some standards defined for doing so for EDI) but in general it is not. Other transports provide capabilities that email cannot.
If you just need to indicate that wM IS can interact with SMTP or read emails from an inbox (created for this purpose), you can say “yes it can” right now.
It takes a bit of set up and some development of FLOW services but it definitely can send emails (with attachments) via SFTP, and can read emails from a POP3- or IMAP-capable server inbox and process them in some way.
If by “POC” you mean “learn how to” the URLs to the docs that @Sonam_Chauhan shared are the place to start.
At the risk of being repetitive, don’t do this if at all possible. The one scenario where email is appropriate is sending email notifications to people about failed (or successful) activity within an integration hosted on wM IS. If notifying people is what the client is after, then certainly pursue that. But if they intend to use email for data transport, try to avoid that.
#webMethods