But this isn't a problem with the SMTP headers having bad info. This is a problem with the HELO SMTP "handshake" having bad info. Mutt sends the message to my local sendmail, my local sendmail attempts to send the mail, it connects to the destination mail server and begins the conversation with 'HELO intranet.fssi-ca.com' to identify itself before it begins sending the message. The problem is that many mail servers take that 'HELO' information and test the host name to see if it's a "real" resolvable internet address. "intranet.fssi-ca.com" is not a resolvable address because it's internal. If I could get my process to connect to my public SMTP server instead of trying to send it through my local sendmail, that would solve my problem. It was suggested that I look at ssmtp but I don't see much documentation or user following on the web for it, so I'm a little hesitant to use it.
Knute wrote: > On Wed, 27 Feb 2002, Bob McLaren wrote: > > > Please help a mutt newbie out. > > I have searched through archives and I am still not able to find the > > answer to this. > > > I am using Mutt inside our network to send emails out to the internet. > > Because it is an internal PC hidden behind a firewall, it does not have > > a resolvable hostname. > > This causes problems because many mail system refuse the email if the > > hostname used in HELO is not resolvable. > > > What can I do to force the HELO generated by mutt to use my outside SMTP > > hostname? > > I ran into this same thing. > Here's the line from my .muttrc file: > set from="[EMAIL PROTECTED]" > # From: address (see send-hook my_hdr From) > > I don't have a my_hdr line but that can easily be set for addresses > outside your network. > > HTH > > -- > Knute > > You live, You die. Enjoy the interval! > -- Clarence > > ------------------------------------------------------------------------ > Part 1.2Type: application/pgp-signature
