riverbank
asked on
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.
MicrosoftExchange329e71ec8 8ae4615bbc 36ab6ce411 09e@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, MicrosoftExchange329e71ec8 8ae4615bbc 36ab6ce411 09e@domain .com carried on spamming/clogging up the queue and therefore mailboxes on the exchange.
Any help much appreciated.
We are having problems with our client's exchange 2007 server - 08.02.0301.000
on a 2008 64bit server.
MicrosoftExchange329e71ec8
NDR is switched off on the server.
I've tried renaming the queue file but this did not solve the issue, MicrosoftExchange329e71ec8
Any help much appreciated.
ASKER
That refers to SP1 rollup 7 though, they have SP2 installed already version 08.02.0301.000
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
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
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.
ASKER
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
ASKER
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.
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.
http://support.microsoft.com/kb/969690