Exchange mailbox question

Using Exchange 2013

I have a number of email addresses that I want to use for automation (e.g, network scanner to email scans, application reporting...).

These addresses will send but not receive email (also want each task to have it's own address)

Should I set each one up as it's own mailbox?  Or something with Send as with shared mailboxes or distribution lists?  Or something else?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you configure internal IP addresses to be able to relay emails through the Exchange server then you don't need to have an actual physical mail box.  For example, in our office selected devices are allowed to use the SMTP in Exchange without having to login (relaying).  So we can actually put anything for the email address as the sender and Exchange will just relay the emails.  I believe this is what you're trying to achieve.

So for examples, you can set the copier as and scanner as, etc.  Exchange doesn't care and the recipient will know where the email was sent from.

Please see the following articles on how to set relaying:

Exchange 2013 - how to configure an internal relay connector

Exchange 2013 - Allowing a Host/IP to Relay Mail

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jason CrawfordTransport NinjaCommented:
It depends on who you will be sending these emails to.  Will you be sending to external email addresses?
JC_ITAuthor Commented:
The emails would all be to internal addresses.
Jason CrawfordTransport NinjaCommented:
1. Enable verbose logging on all send and receive connectors
2. Create a new receive connector and call name is something unique to the type of email you'll be relaying
3. Specify the LAN IP of the application server in the 'Remote IP Ranges' field
4. Check the TLS box under the Authentication tab
5. Check the Anonymous box in the Permissions Group tab

That should be it if you're only relaying to internal addresses.  If you ever want to send to external, run this command:

Get-ReceiveConnector <Connector Name> | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"

Open in new window

If troubleshooting is required, check the SMTPReceive logs here:

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.