That isn't strictly speaking an error, and shouldn't block anything on the back end application. it's more of an informational message within surgemail to say it's queueing a message internally until it as less channels open to that destination.  You can safely increase it usually the limit of 2 is very conservative.  Try 5.

But, like I say, it doesn't explain a backlog on the application end? that error shouldn't be seen by a sending server.

I would check for another error at the sending end, or in the logs...

    ChriSP

Hi all,

I'm suddenly having a terrible time with outbound messages generated by a back end application being stopped by Surgemail with "G_SEND_MAX_PERDOM exceeded 2>2 example.com" errors being logged. (The back end application server uses Surgemail as its smart host.) It's happening for multiple outbound domains, and there is nothing unusual about today in terms of mail volume. Surgemail's mail queue has only a few entries, with none of them going to the domains I'm having trouble sending to. I've even tried restarting Surgemail to no avail. Can't say I've ever run into this before. I've had mail stuck on my back end application server for hours...

Does anyone have any ideas? Am I missing something?

(I'm kind of behind on Surgemail updates, unfortunately -- SurgeMail Version 7.2i-1)

Thanks,

Bob

--

Bob Fera
I.T. Manager
Zenith Information Group
18757 Burbank Blvd., Suite 116
Tarzana, CA 91356
Phone: 818-206-8634 Ext. 160
Fax: 818-345-2605
www.zis.com

Members of NACHA
The Electronic Payments Association