Sending mail to FreeBSD.org (was: FreeBSD lockup accessing serial port on Thinkpad)
wal...@digger.net
On Tue, 13 Nov 2001 10:38:56 +0000, Greg Lehey <gr...@FreeBSD.ORG> wrote:
> [Format recovered--see http://www.lemis.com/email/email-format.html]
>
> Your message was all on one line.
Yeah, well, that happens when one is forced to send email via a web form to avoid being blocked.
> On Saturday, 10 November 2001 at 4:00:01 -0500, wal...@digger.net wrote:
> >
> > Yes, they are definitely more paranoid lately. I'm not seeing the
> > problem you describe, but they refuse to accept email from a server
> > whose HELO hostname doesn't resolve.
>
> That's been in place for a long time.
I've been able to send without a problem up until very recently. But now I just get things like this:
mob...@freebsd.org: smtp;450 <pltn13.pbi.net>: Helo command rejected: Host not found
I've tried to contact postm...@pbi.net, without response.
> > Which appears to nicely block all of us unsavory Pacific Bell
> > Internet customers...
>
> Are you trying to send direct, or via PacBell's mail server?
I send to mail.pacbell.net (aka mta7.pltn13.pbi.net, mta5.snfc21.pbi.net, mta6.snfc21.pbi.net). From the look of the bounce messages, they are leaving off the hostname and sending just the domain (pltn13.pbi.net or snfc21.pbi.net). Which is good and proper:
RFC 821: "HELO <SP> <domain> <CRLF>"
(Though it goes on to contradict itself with "The argument field contains the host name of the sender-SMTP", ALL examples given use a domain name.)
RFC 1123: "The sender-SMTP MUST ensure that the <domain> parameter in a HELO command is a valid principal host domain name for the client host. [...] The HELO receiver MAY verify that the HELO parameter really corresponds to the IP address of the sender. However, the receiver MUST NOT refuse to accept a message, even if the sender's HELO command fails verification."
RFC 2821: "The argument field contains the fully-qualified domain name of the SMTP client if one is available."
...and others.
> They may
> have policy reasons for requiring the latter. If their mail server
> doesn't have reverse DNS, you have a reason for complaint.
Their mail servers DO have reverse DNS. As far as I can tell, they are doing nothing wrong.
This is, of course, completely off-topic for -mobile, but I'm not sure what the proper forum is.
> Given the
> fact that a large number of ISPs seem to be staffed with trained
> monkeys nowadays, it might not be so easy to find a good alternative.
That, or the real workers are hidden behind an impenetrable wall of trained monkeys at the phone banks. Either way, it's just as bad.
Dave
--
----------------------------------------------------------------------
Dave Walton dwa...@acm.org
----------------------------------------------------------------------
.
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Chris Shenton
SMTP discussion; perhaps I'm too late. If not...
Happened to me last night. FreeBSD-4.4 running on a thinkpad 560x. I
had disabled COM1 and COM2 from the IBM software running under <ick> Windows </ick>.
I then did a ./MAKEDEV cuaa4 for a PCMCIA modem card. But when I went
to use "tip", instead of typing
set device /dev/cuaa4
I wrote
set device /dev/cuaa0
When I connected to it with "term" and it locked the machine
hard. Not only was that console screen locked, but ALT-F2 and other
console switching was also hung. I couldn't get any response from the
box and had to power-down to recover.
PS: Is there a way to enable/disable serial ports and the other
features that the IBM Windows software does, without having to go into
Windoze? I'd hate to think I'm gonna have to keep Windoze on that
laptop forever, just so I can fiddle ports and devices. I don't see
a way to do it in any BIOS, like I would expect on a desktop system.