Re: sender_was_rejected./Remote_host_said:____/
On Wed, Jun 27, 2001 at 10:33:32AM -0600, Charles Cazabon wrote: > Alfonso Armenta <[EMAIL PROTECTED]> wrote: > > > > Although in my log quote I used fake addresses those were just slightly > > changed. The usual protect the innocent (not from the regulars from this > > list, of course). > > > > Actually I do remember obtaining one of those messages and log entries when > > I tried to subscribe to this list. Which would mean that q-mail smtp daemons > > do give this Remote_host_said: response. > > "sender was rejected" usually means that the remote SMTP server issued a 5xx > or 4xx code after the MAIL FROM: command. This can be due to DNS problems > when remote sites use bogus anti-spam measures. (or) badmailfrom. (you could consider that bogus too :) > You'll also see this with some sites that reject empty envelope senders (i.e., > you can't send a bounce to them). http://www.rfc-ignorant.org/ Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: sender_was_rejected./Remote_host_said:____/
Alfonso Armenta <[EMAIL PROTECTED]> wrote: > > Although in my log quote I used fake addresses those were just slightly > changed. The usual protect the innocent (not from the regulars from this > list, of course). > > Actually I do remember obtaining one of those messages and log entries when > I tried to subscribe to this list. Which would mean that q-mail smtp daemons > do give this Remote_host_said: response. "sender was rejected" usually means that the remote SMTP server issued a 5xx or 4xx code after the MAIL FROM: command. This can be due to DNS problems when remote sites use bogus anti-spam measures. You'll also see this with some sites that reject empty envelope senders (i.e., you can't send a bounce to them). In general, sites that use either of these strategies aren't worth sending mail to. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: sender_was_rejected./Remote_host_said:____/
That didn't seem to do, apparently, I checked the correct functionality of our DNS and so on. Although in my log quote I used fake addresses those were just slightly changed. The usual protect the innocent (not from the regulars from this list, of course). Actually I do remember obtaining one of those messages and log entries when I tried to subscribe to this list. Which would mean that q-mail smtp daemons do give this Remote_host_said: response. Anyone has any pointers? The weirdest thing is that we have another qmail installation in here that does not receive any of those messages at all. Although I could re-route all outgoing e-mail to it, I rather not as it is a customer system. I am trying to figure out what is the reason for _our_ server to fail, rather than just patch it using another one that works... Yet again, thanks for your time. -Original Message- From: Ahmad Ridha [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 21, 2001 3:46 PM To: [EMAIL PROTECTED] Subject: Re: sender_was_rejected./Remote_host_said:/ Alfonso Armenta writes: >>> new msg 2703468 >>> info msg 2703468: bytes 4430 from <[EMAIL PROTECTED]> qp 28506 uid 502 >>> starting delivery 106109: msg 2703468 to remote [EMAIL PROTECTED] >>> status: local 0/100 remote 1/100 >>> delivery 106109: failure: >Connected_to_195.98.97.5_but_sender_was_rejected./Remote_host_said:/ >>> status: local 0/100 remote 0/100 >>> bounce msg 2703468 qp 28512 >>> end msg 2703468 > > Apparently this is 'random' error. > > The user then gets a bounce like this: > > Connected to 195.98.97.5 but sender was rejected. > Remote host said: > > --- Below this line is a copy of the message. > > Any clues/hints? > Is your fqdn valid (known to the Internet)? I experienced the error when experimenting with my first qmail installation using unknown fqdn and the destination host did domain checking. I noticed usa.net and stupid.com were some of such ones. Regards, Ahmad Ridha
Re: sender_was_rejected./Remote_host_said:____/
Alfonso Armenta writes: >>> new msg 2703468 >>> info msg 2703468: bytes 4430 from <[EMAIL PROTECTED]> qp 28506 uid 502 >>> starting delivery 106109: msg 2703468 to remote [EMAIL PROTECTED] >>> status: local 0/100 remote 1/100 >>> delivery 106109: failure: >Connected_to_195.98.97.5_but_sender_was_rejected./Remote_host_said:/ >>> status: local 0/100 remote 0/100 >>> bounce msg 2703468 qp 28512 >>> end msg 2703468 > > Apparently this is 'random' error. > > The user then gets a bounce like this: > > Connected to 195.98.97.5 but sender was rejected. > Remote host said: > > --- Below this line is a copy of the message. > > Any clues/hints? > Is your fqdn valid (known to the Internet)? I experienced the error when experimenting with my first qmail installation using unknown fqdn and the destination host did domain checking. I noticed usa.net and stupid.com were some of such ones. Regards, Ahmad Ridha
sender_was_rejected./Remote_host_said:____/
Hi! I've been searching through the list without any luck in finding what this error actually means. See some slightly tweaked extract from our qmail logs: >> new msg 2703468 >> info msg 2703468: bytes 4430 from <[EMAIL PROTECTED]> qp 28506 uid 502 >> starting delivery 106109: msg 2703468 to remote [EMAIL PROTECTED] >> status: local 0/100 remote 1/100 >> delivery 106109: failure: >Connected_to_195.98.97.5_but_sender_was_rejected./Remote_host_said:/ >> status: local 0/100 remote 0/100 >> bounce msg 2703468 qp 28512 >> end msg 2703468 Apparently this is 'random' error. The user then gets a bounce like this: Connected to 195.98.97.5 but sender was rejected. Remote host said: --- Below this line is a copy of the message. Any clues/hints? Thanks in advance, Alfonso Armenta.