We originate the mail on the behave of customers, but replies go directly to them so we are not relaying. The notification to us (postmaster) is not occurring, as per Serge's description (this is happening inside another mailet so the normal postmaster notify in error transport does not get a chance), so we cannot be notified w/out doing something like what Serge suggested. The service we provide cannot tolerate "java error" emails to clients, we handle these issues in a special way, that is part of our business.
Jason ----- Original Message ----- From: "Danny Angus" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Wednesday, January 16, 2002 3:32 PM Subject: RE: notify sender > Harsh words indeed, > I can't understand why it would be "unfiltered mail going out to customers > without us knowing about it" unless it is your customers who's mail cannot > be delivered (I.E. you are relaying) and as the mail is simply a bounce of > the mail they sent *and* you can be notified too, it strikes me that you are > overreacting. > I can understand that you'd rather not have this mail sent, but not why > you're *so* concerned about it. > > d. > > > -----Original Message----- > > From: jason sackett [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, January 16, 2002 8:06 PM > > To: James Users List > > Subject: Re: notify sender > > > > > > Thank you for the quick and clear response. > > > > Unfortunately this may be the anvil that breaks the camel's back. > > For some reason, to my company, it is fairly important (read: > > critical) that > > the conf be obeyed (no 'notify sender'). > > To have unfiltered mail going out to customers without us knowing about it > > like this (in any case) is hard to swallow. > > I cannot disagree with them. > > > > Thanks, > > Jason > > > > ----- Original Message ----- > > From: "Serge Knystautas" <[EMAIL PROTECTED]> > > To: "James Users List" <[EMAIL PROTECTED]> > > Sent: Tuesday, January 15, 2002 6:02 PM > > Subject: Re: notify sender > > > > > > > This email is generated by the RemoteDelivery mailet. As the remote > > > delivery mailet has multiple, more involved failure conditions, it is > > > generating it's messages itself for now. It would be nice to have it > > > support an optional "processor" setting so you could have it send errors > > > delivering to a processor rather than generating the messages > > itself, but > > > this hasn't been done yet either. > > > > > > Serge Knystautas > > > Loki Technologies - Unstoppable Websites > > > http://www.lokitech.com/ > > > ----- Original Message ----- > > > From: "jason sackett" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Tuesday, January 15, 2002 4:28 PM > > > Subject: notify sender > > > > > > > > > > Hello all, > > > > > > > > I have all 'notify sender' blocks in the JAMES 2.0a2 nightly build > > > commented > > > > out. > > > > I still get this email sent from the postmaster to the user: > > > > ------------------------------------------------ > > > > Hi. This is the James mail server at chupacabra. > > > > I'm afraid I wasn't able to deliver your message to the following > > > addresses. > > > > This is a permanent error; I've given up. Sorry it didn't work out. > > > > > > > > [EMAIL PROTECTED] > > > > Invalid Addresses; > > > > nested exception is: > > > > javax.mail.SendFailedException: 550 unknown user > > > > <[EMAIL PROTECTED]> > > > > > > > > The original message is attached. > > > > > > > > ------------------------------------------------ > > > > I am trying to prevent this email from reaching the user. Is there a > > > known > > > > issue involved here, or is there something more to do than make sure > > there > > > > are no live 'notify sender' blocks in james.conf? Also, I have the > > > 'notify > > > > postmaster' in the error transport active (and the spam one inactive), > > but > > > > the postmaster does not receive the notice. > > > > > > > > Thank you for any help, > > > > Jason > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
