Email seems caught in a loop and clogging up the store and queue

Hi,

We are having problems with our client's exchange 2007 server - 08.02.0301.000
on a 2008 64bit server.
MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@domain.com keeps sending emails to our journaling@domain.com and user@domain.com. This seems to be caught in a loop of some sort. I've tried deleted the queue contents but they keep re-appearing. Each of these have an attachment within them and are being sent/received at least every minute.
NDR is switched off on the server.
I've tried renaming the queue file but this did not solve the issue, MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@domain.com carried on spamming/clogging up the queue and therefore mailboxes on the exchange.

Any help much appreciated.

 
LVL 1
riverbankAsked:
Who is Participating?
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.

RadweldCommented:
Hello, take a look at this KB

http://support.microsoft.com/kb/969690
0
riverbankAuthor Commented:
That refers to SP1 rollup 7 though, they have SP2 installed already version 08.02.0301.000
0
RadweldCommented:
This guid refers to the Exchange Recipient,

The Microsoft Exchange recipient is a special Microsoft Exchange Server 2007 recipient object that provides a unified and well-known message sender that differentiates system-generated messages from other messages. The Microsoft Exchange recipient is functionally equivalent to an internal postmaster. The Microsoft Exchange recipient replaces the “System Administrator” sender that was used for system-generated messages in earlier versions of Microsoft Exchange Server. Messages from the Microsoft Exchange recipient display "Microsoft Exchange" as the sender. The types of messages that are sent by the Microsoft Exchange recipient include the following:

DSN messages
Journal reports
Quota messages
Agent-generated messages

http://technet.microsoft.com/en-us/library/bb430759(EXCHG.80).aspx

0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

RadweldCommented:
Sorry forgot to add if journaling is enabled, I would try switching it off. I would also check your mailboxes to see if anyone is over their quota.
0
riverbankAuthor Commented:
Journaling is switched off.
There are some fairly large mailboxes but as far as I'm aware, none over their quota, we've not set quotas. Largest is around 10GB


0
steforCommented:
Do you have any auto-forwarding/auto-reply rules enabled on your mailboxes that can cause this? I've seen similar issues when a user had an autoforward on all received e-mails to an external e-mail that got closed down.

Which mailbox is using journaling@domain.com? Could it be that your are beeing spammed by someone with NDRs sent "from" journaling@domain.com that's causing this?

Try to determine which people are trying to send e-mails to and from this address:

Get-MessageTrackingLog | where {$_.Recipients -like "*journaling@domain.com*"}
Get-MessageTrackingLog | where {$_.Sender -like "*journaling@domain.com*"}

Open in new window


0

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
RadweldCommented:
So are we to understand there is no mailbox in your organisation with the journaling@domain.com proxy address? if not and you have switched off NDRs then this explains why messages are sitting around in the queue waiting to expire being unable to be be delivered to this address. What I would do is to add the address to a mailbox and establish what the messages are, once you know what the message are, you can take steps to resolve the issue.
0
riverbankAuthor Commented:
Hi Guys,

Thanks for your help regarding this, it was finally solved by Microsoft who got onto the server. Seems it was a spam email in the end.
0
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.