> -----Messaggio originale----- > Da: Stefano Bagnara [mailto:[EMAIL PROTECTED] > Inviato: martedì 9 maggio 2006 10.41 > A: James Users List > Oggetto: Re: Re: Threads, connection pools and many recipients > > Marcello Marangio wrote: > > Cool. > > I set the max to 100 and it seems fine now, Thanks a million. > > About the bug, I am pretty sure it is related to the size of the > > "recipients" column. > > I didn't try with filesystem repositories. > > As the rfc2822 doesn't put any limit to the size of the > mail address, > > this is pretty bad: the only way to support EVERY > recipients size is > > to build the table as a clob and handle it in the > JDBCSpoolManager class. > > Do you agree? > > We should probably use the 1000 chars limit while accepting > connections via SMTPServer and reject further recipients. > > If we want to suppport >1000 bytes recipients we could change > the JDBCMailRepository to store the recipient collection in > the attributes field and retrieve it from there. We won't > have the plain-text recipients in a field but we'll skip the > 1000 char limit. > > This is not a difficult task but would introduce a backward > compatibility issue, so we should talk about this and > alternative solutions, first.
I see your point, but any size limit to the recipients lenght would be not standard. In any case, at the moment the bug makes only the smtpmanager refuse the mail, giving an error to the client and logging a stacktrace into the log file, that's all: the difference between the current behavoir and the future one would be to log a proper error message instead of the stacktrace. How about modifying the sqlResource.xml file to create a varchar2(4000), to support a bigger length? Marcello --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
