Help interpreting two error messages: NOQUEUE:SYSERR and Authentication-Warning
Recently one of my SmartList mailinglists behaved strangely. On a weekly, announcement-type list, one posting did not get sent to my own organization. Subscribers at my organization make up 24 of the 1188 total subscribers to the list. I can't find any evidence in the mail log that the posting was even attempted to my organization. However, bounce messages got through normally to the list's owner at this same address. One unusual entry in the mail logs came just after the posting was received at the mailinglist's address: Nov 11 12:37:39 mailinglists sendmail[511]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[510]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[509]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[512]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[513]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[514]: gABHbd2w000514: Authentication-Warning: mailinglists.jhuccp.org: slist set sender to popreporter-request@mailinglists.jhuccp.org using -f Can anyone help me understand these two different error messages, and whether they could be connected to this problem? Are there any ways to modify SmartList or sendmail to correct this problem? I searched my sendmail book, the SmartList FAQ and Google on these terms, but came up empty. Thanks for your help. -Kevin Zembower ----- E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Zitat von KEVIN ZEMBOWER <KZEMBOWER@jhuccp.org>:
Recently one of my SmartList mailinglists behaved strangely. On a weekly, announcement-type list, one posting did not get sent to my own organization. Subscribers at my organization make up 24 of the 1188 total subscribers to the list. I can't find any evidence in the mail log that the posting was even attempted to my organization. However, bounce messages got through normally to the list's owner at this same address.
One unusual entry in the mail logs came just after the posting was received at the mailinglist's address: Nov 11 12:37:39 mailinglists sendmail[511]: NOQUEUE: SYSERR(slist): Arguments too long
That's a sendmail problem. It seems that the number of addresses multigram gives to sendmail for local delivery is too high. Try to set maxnames value in rc.init to a lower value. Just a guess. Werner
On Wed, 2002-11-13 at 09:29, KEVIN ZEMBOWER wrote:
Recently one of my SmartList mailinglists behaved strangely. On a weekly, announcement-type list, one posting did not get sent to my own organization. Subscribers at my organization make up 24 of the 1188 total subscribers to the list. I can't find any evidence in the mail log that the posting was even attempted to my organization. However, bounce messages got through normally to the list's owner at this same address.
One unusual entry in the mail logs came just after the posting was received at the mailinglist's address: Nov 11 12:37:39 mailinglists sendmail[511]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[510]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[509]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[512]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[513]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[514]: gABHbd2w000514: Authentication-Warning: mailinglists.jhuccp.org: slist set sender to popreporter-request@mailinglists.jhuccp.org using -f
Can anyone help me understand these two different error messages, and whether they could be connected to this problem? Are there any ways to modify SmartList or sendmail to correct this problem? I searched my sendmail book, the SmartList FAQ and Google on these terms, but came up empty.
Hey Kevin, First, I can't say about the Arguments too long issue, I have never seen that, however the Authentication-Warning we see on a daily basis. Typically it won't cause any problems to have this Authentication-Warning (it adds an X-Authentication-Warning header with the same information that you see in the error log though). To remove this you can add 'slist' to the Trusted users of sendmail... I'm only familiar with the version of sendmail we run so I cannot say if this will work without modification. In the file /etc/mail/sendmail.cf (or equivilent on your box) and search for "Trusted users" (You may have to adjust your search based on how your sendmail.cf is formatted) and you should see a block similar to the following: ##################### # Trusted users # ##################### # this is equivalent to setting class "t" Ft/etc/mail/trusted-users %[^\#] Troot Tdaemon Tuucp Add the user 'slist' by adding the following line: Tslist Or, if you do have the Ft/etc/mail/trusted-users line you can also just place the username in that file to remove the warning (Note: If you use the file specified by the Ft entry for trusted users just the username is necessary, not the T prefix) Thanks, Tim Yohn Jr. System Administrator Alabanza Corporation
On 13 Nov 2002, Tim Yohn wrote:
On Wed, 2002-11-13 at 09:29, KEVIN ZEMBOWER wrote:
One unusual entry in the mail logs came just after the posting was received at the mailinglist's address: Nov 11 12:37:39 mailinglists sendmail[511]: NOQUEUE: SYSERR(slist): Arguments too long Nov 11 12:37:39 mailinglists sendmail[510]: NOQUEUE: SYSERR(slist): Arguments too long
Hi, you've set # maximum number of recipients per SMTP envelope #O MaxRecipientsPerMessage=100 to very low value. Leave default value 100 in. Setting this value low doesn't help you against the spam anyway. ;) -- Martin Mokrejs <mmokrejs@natur.cuni.cz>, <m.mokrejs@gsf.de> PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs MIPS / Institute for Bioinformatics <http://mips.gsf.de> GSF - National Research Center for Environment and Health Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany tel.: +49-89-3187 3683 , fax: +49-89-3187 3585
participants (4)
-
KEVIN ZEMBOWER
-
Martin MOKREJŠ
-
Tim Yohn
-
Werner Reisberger