On Thu, 24 Dec 2009, Francesco Vertova wrote: > At 19.26 24/12/09, you wrote: > > > The bug was introduced in one of the 1.27-pre?? releases. 1.26 is infe. > > Nope, the bug is in 1.26.
We talking about different issues? Let me replay that for you: ---- On Thu, 24 Dec 2009, Chen Shihai wrote: > Hi Davide, > > Testing xmail 1.27 pre05 (on RHEL 5.3 box) and found a problem. > > I've enabled NoSenderBounce, NotifySendLogToSender and AllowNullSender > in server.tab, and NotifyMsgLinesExtra is set to 20. But when a mail is > unable to send, the system generated notification message cannot be sent > to the sender and admin. It is frozen in spool and marked as invalid > spool file so that it can not be listed via frozlist. I found the frozen > messages by XMail Queue Manager. > > The same frozen messages can be properly processed by XMail 1.26. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ---- Savvy? > > I know exactly what happened. The "is this email path correct?" check done > > at SMTP level and at SMAIL level, were not symmetric. > > The check was (not?) done at the *** LMAIL *** level. SMTP was not involved in > my scenario. LMAIL gives you a straight plug into XMail spool. If you drop shit in, you get shit out. Same thing if your filters break the message structure. - Davide _______________________________________________ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
