I'll be looking at the references supplied by others a bit later this evening. But, in the mean time...
Wednesday, July 23, 2003, 7:29:37 PM, Rodolfo wrote: > Did you recreate the sendmail.cf file and restart sendmail? Yes. > What happens if you "telnet mailserver 25" and issue a "ehlo localhost"? "ehlo localhost" gives an error about it being an invalid domain name. Getting past that, after the "pleased to meet you" message, I get: 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-AUTH LOGIN PLAIN 250-DELIVERBY 250 HELP This would also seem to indicate that I should be able to use PLAIN authentication to tell sendmail that I'm an OK person. > Check to make sure that The Bat! is not trying to use encrypted > authentication (which right now will not work, you need to do more stuff to > set it up with SASL). Right now you have PLAIN and LOGIN authentication > available, that is, unencrypted. It is not set up to attempt encryption. I've looked at setting up the encryption stuff a couple of times, but have always been stymied by how to merge such configuration with The Bat! configuration. I have the option to do RFC 2554 authentication (which I have checked). Within that, I get to specify a login name and password (which I have), as well as the option to use Secure MD5 Authentication (which I have NOT checked). That is all in the "Authentication" config menu. Within the superior "Transport" config menu, I have my choice of connections / ports: Regular; Secure to regular port (STARTTLS); and Secure to dedicated port (TLS). Unfortunately, The Bat! documentation does not seem to help me match these up with how one might configure Sendmail to match. As I recall, when I last tried going down the path to encryption based authentication, I was stuck trying to figure out how to come up with a common key format that would be acceptable both on the Linux side and on the The Bat! side. sigh. > This sounds like a configuration issue with The Bat! Same configuration of the same install of The Bat! on the same notebook computer. When sitting at my home, it works. When sitting at my client this afternoon, it would not. One other detail that may be important -- I have my home network set up to use IP addresses in the same range as the network at my office. I can't think how that would matter, since I wouldn't think that those internal IP addresses would be propagated out through the SMTP session. But, it is a difference between my home's and my client's networks. Ron. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
