Here is where you have a problem of sorts...
Outlook can indeed be opened by Access. There is the possibility of checking an Outlook library in the References list. Many folks have been able to read Outlook mail from Access.
BUT...
Your issue is that you want to do something with incoming mail. Here is where you run into a tech-check. Access, Outlook, Word, Excel, and just about any other window-oriented program you could name are oriented towards the Windows paradigm of programming, which is to say, they respond to EVENTS. A button click, a mouse move, a mouse-wheel move, a key entry, ... these and many other things trigger events. The Windows O/S "delivers" the events to the program, which must then decide what to do with them.
A "MAIL RECEIVED" event (not its proper name) is an OUTLOOK event. You cannot easily get Outlook to pass that event to Access. Even if you did, Access has no clue as to what a NewMail event means because it does not get one of those normally. It would see the code delivered from Windows O/S and say, in effect, "And what has this to do with me?"
You can program Outlook to respond to such an event because it has a VBA facility. But Access cannot get to the Outlook Event handler. That leaves you with designing a scheme to notify Access (which must be running) that it has mail to receive.
The final implication is that you have Access and Outlook sharing memory and somehow sharing data. But I don't know offhand of a way to make them share EVENTS. So that means your Access code has to do the only other thing available to it... loop.
You can include an invocation of the DoEvents routine to let other programs have a shot. You can create a startup form that self-minimizes and holds a timer that runs every X seconds (units of the timer are milliseconds). You can let Access run with lower priority than Outlook and then just let Access run flat-out forever. But in essence, you have no easy way to get Access to immediately notice new mail.
Now, the next question is, can you do this anyway? Sure. But you will spend many nights reading the manuals and wondering how you let yourself be talking into this project.
The next step is that even if you COULD do this (and I'm not saying you CAN'T), you would have to devise a scheme to identify the mail messages you wanted to see and somehow filter them so you can ignore personal mail to the same person/account. That will involve some text parsing of the subject line and perhaps analysis of the file body.
OK, one last little gotcha... if you happen to get a worm through e-mail and your automation OPENS it (even if only to reject it), you probably just launched a program from an unknown source to run on your machine with YOUR permissions and privileges. Do you really want to do that?
I don't want you to think this can't be done. What I want you to know is the magnitude of the task you have set for yourself.