re: localhost prefixing problem

2008-02-12 Thread Jude DaShiell
I modified some configurations and updated exim4 and when I try sending get the error message: [error sending: no such host as localhostoutgoing.verizon.net] I edited /etc/hostname on the local system to have localhost in it rather than debian too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED

Re: localhost prefixing problem

2008-02-11 Thread Chris Bannister
On Sat, Feb 09, 2008 at 09:26:27AM -0600, Jude DaShiell wrote: > sample email message cut here: >> From [EMAIL PROTECTED]/POP3 Sat Feb 9 10:18:16 2008 > Newsgroups: Date: Sat, 9 Feb 2008 10:18:16 -0500 (EST) > From: Jude DaShiell <[EMAIL PROTECTED]/POP3> > X-X-Sender: [EMAIL PROTECTED] > To: [EMAI

re: localhost prefixing problem

2008-02-09 Thread Jude DaShiell
Kevin, The /etc/email-addresses wasn't set up properly but whatever is causing these malformed addresses is overwriting mail user agent headers and is unaffected by the contents of /etc/email-addresses apparently. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe"

Re: localhost prefixing problem

2008-02-09 Thread Kevin Mark
On Sat, Feb 09, 2008 at 09:26:27AM -0600, Jude DaShiell wrote: > sample email message cut here: >> From [EMAIL PROTECTED]/POP3 Sat Feb 9 10:18:16 2008 > Newsgroups: Date: Sat, 9 Feb 2008 10:18:16 -0500 (EST) > From: Jude DaShiell <[EMAIL PROTECTED]/POP3> > X-X-Sender: [EMAIL PROTECTED] > To: [EMAI

re: localhost prefixing problem

2008-02-09 Thread Jude DaShiell
sample email message cut here: From [EMAIL PROTECTED]/POP3 Sat Feb 9 10:18:16 2008 Newsgroups: Date: Sat, 9 Feb 2008 10:18:16 -0500 (EST) From: Jude DaShiell <[EMAIL PROTECTED]/POP3> X-X-Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: test message Fcc: sent-mail Message-ID: <[EMAIL PR

Re: localhost prefixing problem

2008-02-08 Thread Chris Bannister
On Sun, Feb 03, 2008 at 10:40:27AM -0600, Jude DaShiell wrote: > I tried using exim4 and alpine to send a piece of email from one account to > another. I suppose I ought to have given this machine the same domain name > as verizon.net rather than left it at localhost since even with address > h