November 2002 - Smartlist - lists.rwth-aachen.de

Re: Help interpreting two error messages: NOQUEUE:SYSERR andAuthentication-Warning
by KEVIN ZEMBOWER 14 Nov '02

14 Nov '02

Martin, thanks for your suggestion. On the SuSE 8.0 system I'm running, /etc/sendmail.cf is built automatically from /etc/sysconfig/mail and /etc/sysconfig/sendmail. Neither of these seems to have any variable with regard to Max Recipients Per Message. However, the MaxRecipientsPerMessage line in my /etc/sendmail.cf is identical to the one you quoted. Thanks for your suggestion. I have to wait until Monday to see if the changes I made to rc.init will prevent my problem or not. I changed minnames to 16 from the default 32, and maxnames from 64 to 32. I suspect that I only had to change maxnames, but there seemed to be a relationship between these numbers that I wanted to preserve. This is a once-weekly post, going out to only 1188 subscribers, so this change shouldn't put too much additional load on the machine. -Kevin >>> Martin MOKREJŠ <mmokrejs(a)natur.cuni.cz> 11/14/02 05:25AM >>> 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(a)natur.cuni.cz>, <m.mokrejs(a)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 _______________________________________________ Smartlist mailing list Smartlist(a)lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist

1 0

Help interpreting two error messages: NOQUEUE:SYSERR and Authentication-Warning
by KEVIN ZEMBOWER 14 Nov '02

14 Nov '02

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(a)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

4 3

multigram fuzzy matching
by Werner Reisberger 05 Nov '02

05 Nov '02

It seems to me there is no way to get a 100% match with multigram. Example if the dist file contains the address "user(a)some.domain": echo 'user(a)some.domain'|/var/list/.bin/multigram -b1 dist gives "user(a)some.domain 32760 user(a)some.domain" and echo '=user(a)some.domain'|/var/list/.bin/multigram -b1 -l32760 dist gives the same result although the addresses are different and =user(a)some.domain is a valid address. That's rather a bug than a feture and makes it impossible to use multigram if you want to have exact matches. Werner

1 0

new confirm addon
by Werner Reisberger 03 Nov '02

03 Nov '02

The new confirm addon for SmartList is available at ftp://ftp.pure.ch/smartlist/confirm-1.2.7.tar.gz confirm is used to confirm un/subscriptions to a SmartList list therefore preventing the malicious un/subscription of email addresses and ensuring that only working addresses are added to the list. The new addon was necessary to fix a bug in the unsubscription feature. A non member was able to unsubscribe a list member without his consent. Without the confirm addon (non) list members are also able to unsubscribe list members but confirm should prevent this of course. You are strongly encouraged to upgrade if you use confirm for the control of unsubscriptions. Werner

1 0