Error On Output Channel Sending
We're occurred same messages on our customer site, Is that any possible reason why this problem occur ? "Gigi Leung"
when I check my mail log file, I see a lot of the following error messages: SYSERR: putoutmsg (url): error on output channel (will queue)": Broken pipe I have searched through the mailing list and found quite a number of users posted the same questions. However, I did not see a solution that can really solve it. This is causing a lot of problem for the mail server. Any help is appreciated. Thank you. __________________________________________________ Do You Yahoo!? Yahoo! Greetings - Send Mom a mother's day greeting. http://greetings.yahoo.com.sg/ Top error http://marc.info/?l=sendmail&m=98989590802186&w=2 on output channel sending "250 ..." Broken pipe by ??? » Wed, 16 May 2001 11:50:38 Hello, We're occurred same messages on our customer site, Is that any possible reason why this problem occur ? > Hi, > I am running Sendmail 8.11.3 on Solaris 2.6. However, > when I check my mail log file, I see a lot of the > following error messages: > SYSERR: putoutmsg http://www.verycomputer.com/4_3a335c1b286478ba_1.htm (url): error on output channel > (will queue)": Broken pipe > I have searched through the mailing list and found > quite a number of users posted the same questions. > However, I did not see a solution that can really > solve it. This is causing a lot of problem for the > mail server. > Any help is appreciated. Thank you. > __________________________________________________ > Do You Yahoo!? > Yahoo! Greetings - Send Mom a mother's day greeting. > http://greetings.yahoo.com.sg/ Top error on output channel sending "250 ..." Broken pipe by MailMem » Fri, 18 May 2001 12:03:02 Hi, Finally, I have manage to solve the problem at my site. The error only occurs for hosts that do not have MX record or does not exist. When they try to connect to port 25 of my machine, it takes about 75secs for the DNS to response fail. By that time, the requesting hosts already timeout, so sendmail gets "Broken pipe" as it is not able to send back the "250 ..." message. As such, all I did is to change /etc/resolv.conf to add in the entry "options retrans:3". Do a "man resolv.conf" for more information o
03 Mar 1999 04:00:00 I'm running 8.9.1 on a SunOS 4.1.3 system. There seems to be a class of spammer such as the Telstra spamhaus at [203.37.180.6] which runs some sort of spamware program that appears to http://www.verycomputer.com/4_0db03694f94748b9_1.htm open an SMTP port, close its reader side, and attempt to cram the spam down the connection without listening to SMTP replies. 203.37.180.6 is listed in my access.db as being refused (with a custom http://docs.spring.io/spring-integration/reference/html/messaging-routing-chapter.html message in the LHS of the database entry.) The behavior on this end of the TCP connection is that I'll get many dozens of the error message one after another: NOQUEUE: SYSERR: putoutmsg ([203.37.180.6]): error error on on output channel sending "550 ...": Broken pipe repeated in /var/log/syslog. (I assume I'm getting one log entry for every line they're sending.) A "ps" run against the sendmail instance while the spammer is connected displays a line of the spam as sendmail's arguments. (As you run "ps" repeatedly, different lines appear.) I'm not familiar with sendmail 8.9.x's behavior on other, perhaps more modern, platforms, but error on output I was wondering if sendmail 8.9.[23...] is better equipped to handle this. Of course, the spam isn't going anywhere, and it's a minor CPU hog while it's connected, but if a spamming SMTP client doesn't respond appropriately to sendmail's SMTP replies (indeed, if the client makes it impossible to reply at all), it would seem to me that keeping the connection open after the first attempt to send a fatal rejection message fails is counterproductive and could be abused. I'm not sure how much of this is platform-specific behavior, since this machine is running fairly old, crufty software. I'm assuming that the reason sendmail is getting a "broken pipe" when attempting to reply is that the far end has performed a shutdown on its reader side (sendmail's writer side) of the TCP connection. Anyone have any observations on the behavior of later versions of sendmail 8.9.x (x >1) when confronted with this? Or its behavior on other platforms such as Solaris 2.x or FreeBSD? And have others seen this same behavior with certain spammers? I'm reluctant to start mucking with sendmail's source code
one or more different Message Channel depending on a set of conditions. Spring Integration provides the following routers out-of-the-box: Payload Type Router Header Value Router Recipient List Router XPath Router (Part of the XML Module) Error Message Exception Type Router (Generic) Router Router implementations share many configuration parameters. Yet, certain differences exist between routers. Furthermore, the availability of configuration parameters depends on whether Routers are used inside or outside of a chain. In order to provide a quick overview, all available attributes are listed in the 2 tables below. Table6.1.Routers Outside of a Chain Attributerouterheader value routerxpath routerpayload type routerrecipient list routerexception type routerapply-sequence default-output-channel resolution-required ignore-send-failures timeout id auto-startup input-channel order method ref expression header-name evaluate-as-string xpath-expression-ref converter Table6.2.Routers Inside of a Chain Attributerouterheader value routerxpath routerpayload type routerrecipient list routerexception type routerapply-sequence default-output-channel resolution-required ignore-send-failures timeout idauto-startupinput-channelordermethod ref expression header-name evaluate-as-string xpath-expression-ref converter Important Router parameters have been more standardized across all router implementations with Spring Integration 2.1. Consequently, there are a few minor changes that leave the possibility of breaking older Spring Integration based applications. Since Spring Integration 2.1 the ignore-channel-name-resolution-failures attribute is removed in favor of consolidating its behavior with the resolution-required attribute. Also, the resolution-required attribute now defaults to true. Prior to these changes, the resolution-required attribute defaulted to false causing messages to be silently dropped when no channel was resolved and no default-output-channel was set. The new behavior will require at least one resolved channel and by default will throw an MessageDeliveryException if no channel was determined (or an attempt to send was not successful). If you do desire to drop messages silently simply set default-output-channel="nullChannel". 6.1.2Common Router Parameters Inside and Outside of a Chain The following parameters are valid for all routers inside and outside of chains. apply-sequence This attribute specifies whether sequence number and size headers should be added to each Message. This optional attribute defaults to false. default-outp