Re: Exim's rewriting of headers

2003-02-24 Thread Johann Spies
On Fri, Feb 21, 2003 at 01:44:19PM -0500, Derrick 'dman' Hudson wrote:
 
 The mail sent with mail(1) doesn't have any headers that match the
 pattern in exim's rule.
 
 One solutin is to change the pattern so it matches the FQDN as well as
 the hostname only.  The other solution is to find out why the two
 programs come up with different names for your machine, and adjust the
 lookup (and maybe the pattern) so they all match.

Thanks.  Adding another rule matching the FQDN made the difference.

Regards.
Johann
-- 
Johann Spies  Telefoon: 021-808 4036
Informasietegnologie, Universiteit van Stellenbosch

 Thy word is a lamp unto my feet, and a light unto my 
  path.   Psalms 119:105 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Exim's rewriting of headers

2003-02-24 Thread Johann Spies
On Fri, Feb 21, 2003 at 06:16:38PM -0600, Shyamal Prasad wrote:
 Byt I am very curious about why you chose not to use the
 /etc/email-addresses file with the default rule that Debian provides?
 That would not have resulted in the hostname resolution problem above
 (right?).

At that stage I had problems with wrong Sender headings in my mail.
In the end I solved that by putting this specific rewrite rule in
/etc/exim/exim.conf and removing the original one in
/etc/email-addresses. 

Maybe it was not necessary but I saw that other exim users on Redhat
systems did not have the same problem I had.  And they did not use
/etc/email-addresses.

Regards.
Johann
-- 
Johann Spies  Telefoon: 021-808 4036
Informasietegnologie, Universiteit van Stellenbosch

 Thy word is a lamp unto my feet, and a light unto my 
  path.   Psalms 119:105 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Exim's rewriting of headers

2003-02-21 Thread Derrick 'dman' Hudson
On Fri, Feb 21, 2003 at 02:52:39PM +0200, Johann Spies wrote:
| I am user js on my computer and user jspies with email address
| [EMAIL PROTECTED] on our network.
| 
| I have the following in my /etc/exim/exim.conf
| 
| *@bywoner [EMAIL PROTECTED] Ffrs   
^^
| 
| Running exim -brw shows this:
| 
| zsh % sudo exim -brw root@bywoner
|   sender: [EMAIL PROTECTED]
| from: [EMAIL PROTECTED]
|   to: root@bywoner
|   cc: root@bywoner
|  bcc: root@bywoner
| reply-to: [EMAIL PROTECTED]
| env-from: [EMAIL PROTECTED]
|   env-to: root@bywoner
| 
| So why do the headers look like this I send mail from the unix
| commandline (mail [EMAIL PROTECTED])?:
| 
| To: [EMAIL PROTECTED]
| Subject: Toets mail
| Message-Id: E18mB0Q-0003Hh-00@bywoner
| From: Johann Spies [EMAIL PROTECTED]
 ^

The mail sent with mail(1) doesn't have any headers that match the
pattern in exim's rule.

One solutin is to change the pattern so it matches the FQDN as well as
the hostname only.  The other solution is to find out why the two
programs come up with different names for your machine, and adjust the
lookup (and maybe the pattern) so they all match.

| Date: Fri, 21 Feb 2003 13:06:14 +0200
| Return-Path: [EMAIL PROTECTED]
| 
| I suspect this is why my efforts to subscribe on some mailing lists
| which request one to send an empty email so the list server failed in
| the past because I did most of them from the command line.

Probably.

-D

-- 
If we claim to be without sin, we deceive ourselves and the truth is not
in us.
I John 1:8
 
http://dman.ddts.net/~dman/



msg32180/pgp0.pgp
Description: PGP signature


Re: Exim's rewriting of headers

2003-02-21 Thread Shyamal Prasad
Johann == Johann Spies [EMAIL PROTECTED] writes:

Johann I am user js on my computer and user jspies with email
Johann address [EMAIL PROTECTED] on our network.

Johann I have the following in my /etc/exim/exim.conf

Johann [EMAIL PROTECTED] [EMAIL PROTECTED] Ffrs

dman already pointed out what I think is the fault, so I'm probably
not helping here. 

Byt I am very curious about why you chose not to use the
/etc/email-addresses file with the default rule that Debian provides?
That would not have resulted in the hostname resolution problem above
(right?).

Cheers!
Shyamal


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]