From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <82c890d00708030324m2dcaea33q8098d46842401b4b@mail.gmail.com> Date: Fri, 3 Aug 2007 12:24:08 +0200 From: "Gabriel Diaz" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] can't send mail, sometimes In-Reply-To: <4f2b90c643ddd96bea6f89a75cfdda2b@csplan9.rit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <82c890d00708030304w2e5d9c10u7c8daf3f70854de6@mail.gmail.com> <4f2b90c643ddd96bea6f89a75cfdda2b@csplan9.rit.edu> Topicbox-Message-UUID: 9bb18ebc-ead2-11e9-9d60-3106f5b1d025 hello what's exactly your setup? a vmware terminal on your dsl at home sending mail through your plan9 server elsewhere? may be your vmware is trying to send email directly instead of contacting your other server? gabi On 8/3/07, john@csplan9.rit.edu wrote: > > Strangely, though, I don't seem to get the reject when I send > the exact same message from drawterm, which is why I thought it might > be on my end. > > John > > > hello > > > > I suppose thats a google reject, use the smtp relay from your provider > > in smtpd configuration (see /mail/lib/smtpd.direct and smtpd.gateway > > iirc) > > > > gabi > > > > > > On 8/3/07, john@csplan9.rit.edu wrote: > >> Well, this is incidental to the "google.com job search" thread... > >> In my efforts to see what exactly they have to offer anyway, I'm > >> trying to send an email from my vmware Plan 9 terminal. However, > >> when I try to send the reply, I get this back: > >> > >> Your request "smtp net@google.com alicec" failed (code smtp 663: Permanent Failure). > >> The symptom was: > >> > >> Thu Aug 2 17:19:49 HST 2007 connect to net!google.com: > >> 553 5.3.0 REJECT # home users == spam relays > >> > >> > >> Is this my own mail system rejecting me, or what? I'm not very > >> well-versed in smtp-foo. > >> > >> Also, what's the deal with the utterly and completely broken snarfing > >> and pasting under vmware? I run aux/vmware in my lib/profile, which > >> I thought was supposed to fix it, but I had to hand-type the above > >> error because the damn thing is too broken to actually copy and > >> paste it. > >> > >> > >> John > >> > >> > >