> > would folks like me to nag to this list (to practice/resolve) or to > > nag directly to me [and me forward if I need assistance?] > > +1 to this list
Ok, to the list it is. I tried. The LSD result seems representative, i.e. typical (strictly managed) SMTP servers don't allow spam relaying/spoofing. http://lsd.student.utwente.nl/gump/gumpy.html send: u'mail FROM:<[EMAIL PROTECTED]>\r\n' reply: '250 ok\r\n' reply: retcode (250); Msg: ok send: 'rcpt TO:<[EMAIL PROTECTED]>\r\n' reply: "553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)\r\n" reply: retcode (553); Msg: sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) I think most strictly managed servers will disallow this spoofing. [Maybe apache's was configured differently for a reason, I'm not judging, just stating I don't think we'll find many that are so configured.] I think we need to accept this and move on. I suspect that e-mails were "spoofed" in case the recipient was a closed mailing list. I think we need to send the e-mail from [EMAIL PROTECTED] [or similar] and if folks want the gump input they allow that as a publisher. I will code/configure accordingly. Other thoughts/inputs/opinions? > > > If nagging works, and if Gumpy is close to reporting facts (not just > > errors in itself) I'd like to start nagging to the end users. > > *If* Darn, ok -- if I *must*. ;-) regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
