MS Outlook 2003 send problem

RickB · 17 May 2007 at 09:59

I have a problem..well more of an annoyance at work with Outlook 2003 and sending an email to a lot of people.

I usually have to send reports to a number of people but when I try to do it, I get an error saying 554 bulk sends not permitted.

I tried to create a mailing list but the same error occurs.

Is there any way to get around needing to send 4-5 copys of the same email out?

cheers

Rick

katana6434 · 17 May 2007 at 10:07

That sounds like a restriction placed on the exchange server by your IT department rather than an Outlook problem.

I would speak to your IT department to see if they can help.

mr.bond · 17 May 2007 at 15:26

Your Exchange (if that's what you use) administrator has set a restiction on the SMTP Virtual server that limits the maximum amount of recipients per message.

I'm not aware of a setting in Outlook that does the same, doesn't mean one doesn't exist of course.

Matt-Page · 17 May 2007 at 19:26

mr.bond said:
Your Exchange (if that's what you use) administrator has set a restiction on the SMTP Virtual server that limits the maximum amount of recipients per message.

I'm not aware of a setting in Outlook that does the same, doesn't mean one doesn't exist of course.

Yep. It's a security setting, to stop viruses throwing out hundreds of emails or exchange kill attacks.

It's a setting on the exchange server. Not sure if the policy applies to all users, or if you can allow a group of users access to do this?

RickB · 17 May 2007 at 21:03

Ahh right cool. I'll have a word with the IT guy and see what I can do.

Thx ppl!!

mr.bond · 17 May 2007 at 22:38

Matt-Page said:
Yep. It's a security setting, to stop viruses throwing out hundreds of emails or exchange kill attacks.

It's a setting on the exchange server. Not sure if the policy applies to all users, or if you can allow a group of users access to do this?

*Normaly* this setting is for all. However, you can have more than one virtual server. Multiple ones are generaly required when there is a need for different authentication methods on the same Exchange server. I've not worked anywhere yet though where this has been implemented.

Not sure if that answers your question or not