Thanks Johann Spies and Peter Bowyer your replies set me up the right
track.. the config file /etc/exim4.conf had only one line but was used as
configfile for exim
if that file exists the real config file
/var/lib/exim4/config.autogenerated is neither updated nore used in this
debian setup and saidly no warnings or errors.. wierd that exim4 can run
with a empty config without warnings
anyways i know now exactly why all my config changes en effort didnt fix the
problem.. thanks for pointing me in the right direction... im clueless
though how that conf file got there.in the first place..:S maybe it was
generated when i was installing some exim-courier debian packages
Regards Alexander
2010/12/23 <exim-users-request@???>
> Send Exim-users mailing list submissions to
> exim-users@???
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.exim.org/mailman/listinfo/exim-users
> or, via email, send a message with subject or body 'help' to
> exim-users-request@???
>
> You can reach the person managing the list at
> exim-users-owner@???
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Exim-users digest..."
>
> Today's Topics:
>
> 1. Re: address rewrite not working (Nigel Metheringham)
> 2. Re: address rewrite not working (Johann Spies)
> 3. Re: address rewrite not working (Nigel Metheringham)
> 4. Re: address rewrite not working (Always Learning)
> 5. Re: address rewrite not working (Jeremy Harris)
> 6. Re: address rewrite not working (W B Hacker)
> 7. delivery not succesfull (Alexander Curvers)
> 8. Re: address rewrite not working (Graeme Fowler)
> 9. Re: delivery not succesfull (Johann Spies)
> 10. Re: delivery not succesfull (Peter Bowyer)
> 11. filter "mail" and envelope "from" (WJCarpenter)
> 12. Re: filter "mail" and envelope "from" (Phil Pennock)
>
>
> ---------- Doorgestuurd bericht ----------
> From: Nigel Metheringham <nigel.metheringham@???>
> To: Always Learning <exim@???>
> Date: Wed, 22 Dec 2010 12:00:25 +0000
> Subject: Re: [exim] address rewrite not working
> On 22 Dec 2010, at 11:33, Always Learning wrote:
>
> > Perhaps it is time to play with the SYSTEM FILTER.
>
> STEP AWAY FROM THE KEYBOARD!!!!
>
> Two definitive exim rules:-
>
> - If you are talking about getting mail to a destination, you do
> not want to be considering rewriting - that is trying to bring
> a sendmail (everything done by rewrites) mindset into exim
>
> - Never do mail routing in a system filter
>
> [Second rule is more generally specified as never use a system filter
> unless there really is no other way of doing it - the generalisation of
> which is don't do system filters]
>
> Nigel.
> --
> [ Nigel Metheringham Nigel.Metheringham@??? ]
> [ - Comments in this message are my own and not ITO opinion/policy - ]
>
>
>
>
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Johann Spies <jspies@???>
> To: exim-users@???, Always Learning <exim@???>
> Date: Wed, 22 Dec 2010 14:31:12 +0200
> Subject: Re: [exim] address rewrite not working
> Hallo Nigel,
>
> >
> > STEP AWAY FROM THE KEYBOARD!!!!
> >
> > Two definitive exim rules:-
> >
> > - If you are talking about getting mail to a destination, you do
> > not want to be considering rewriting - that is trying to bring
> > a sendmail (everything done by rewrites) mindset into exim
> >
> > - Never do mail routing in a system filter
>
> Please help me to understand and maybe a practical situation will make
> it clear.
>
> On our campus there several mailservers for which we relayed mail. Then
> it happens that one or more of them cease to exist and the mail have to
> be delivered at another place (e.g. exchange).
>
> How would you, without rewriting the email, handle that situation. What
> we did was to rewrite it:
>
> Say the mail serves akad and addresses had the pattern:
> user@???
>
> We rewrote it to user@???.
>
> Regards
> Johann
> --
> Johann Spies Telefoon: 021-808 4699
> Databestuurder / Data manager
>
> Sentrum vir Navorsing oor Evaluasie, Wetenskap en Tegnologie
> Centre for Research on Evaluation, Science and Technology
> Universiteit Stellenbosch.
>
> "And there were in the same country shepherds abiding
> in the field, keeping watch over their flock by night.
> And, lo, the angel of the Lord came upon them, and the
> glory of the Lord shone round about them: and they were
> sore afraid. And the angel said unto them, Fear not:
> for behold I bring you good tidings of great joy, which
> shall be to all people. For unto you is born this day
> in the city of David a Saviour, which is Christ the
> Lord." Luke 2:8-11
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Nigel Metheringham <nigel.metheringham@???>
> To: Johann Spies <jspies@???>
> Date: Wed, 22 Dec 2010 13:08:59 +0000
> Subject: Re: [exim] address rewrite not working
> On 22 Dec 2010, at 12:31, Johann Spies wrote:
>
> > Please help me to understand and maybe a practical situation will make
> > it clear.
> >
> > On our campus there several mailservers for which we relayed mail. Then
> > it happens that one or more of them cease to exist and the mail have to
> > be delivered at another place (e.g. exchange).
> >
> > How would you, without rewriting the email, handle that situation. What
> > we did was to rewrite it:
>
> There is no need to rewrite in this case. Standard routing would get the
> email there OK - router given below.
>
> However there might be a case to rewrite to ensure that replies (if the
> sender addresses were in the deprecated domain), or reply-alls go direct
> to their destination rather than via the deprecated domain.
>
> This does have other disadvantages - it is changing mail (which may well
> have legal implications) and may break digital signatures. Rewriting is
> generally best avoided for these reasons.
>
> > Say the mail serves akad and addresses had the pattern:
> > user@???
> >
> > We rewrote it to user@???.
>
> You could have a router like:-
>
> redirect_deprecated:
> driver = redirect
> domains = akad.sun.ac.za
> data = ${quote_local_part:$local_part}@???<local_part%7D@???>
>
> That would handle the delivery. Any rewriting is cosmetic to that.
>
> Nigel.
>
>
>
>
> --
> [ Nigel Metheringham Nigel.Metheringham@??? ]
> [ - Comments in this message are my own and not ITO opinion/policy - ]
>
>
>
>
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Always Learning <exim@???>
> To: exim-users@???
> Date: Wed, 22 Dec 2010 14:33:52 +0000
> Subject: Re: [exim] address rewrite not working
>
> On Wed, 2010-12-22 at 12:00 +0000, Nigel Metheringham wrote:
>
>
> > Two definitive exim rules:-
> >
> > - Never do mail routing in a system filter
>
> Why not ?
>
> Exim has been designed, programmed and released to the world to do
> exactly that ......
>
> > if $h_to: contains mail@???
> > then
> > deliver general.mailbox@???
> > finish
> > endif
>
> ... please will you kindly enlighten me why it might be advantageous to
> Exim admins to ignore the system filter facilities (which use a
> noticeably different syntax from the rest of Exim).
>
> Your suggestion ....
>
> > redirect_deprecated:
> > driver = redirect
> > domains = akad.sun.ac.za
> > data = ${quote_local_part:$local_part}@???<local_part%7D@???>
>
> ..... certainly is interesting. Would this forward mail for
> user1@??? to new.box@??? ?
>
> divert_mail
> driver = redirect
> domains = old-domain.com
> local_part = user1
> data = new.box@???
>
>
>
> Happy Christmas,
>
> Paul.
>
>
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Jeremy Harris <jgh@???>
> To: exim-users@???
> Date: Wed, 22 Dec 2010 14:50:09 +0000
> Subject: Re: [exim] address rewrite not working
> On 2010-12-22 14:33, Always Learning wrote:
>
>>
>> On Wed, 2010-12-22 at 12:00 +0000, Nigel Metheringham wrote:
>>
>>
>> Two definitive exim rules:-
>>>
>>> - Never do mail routing in a system filter
>>>
>>
>> Why not ?
>>
>
> Because that's what routers are for, do well, and integrate best
> with the rest of exim's operations?
>
> - Jeremy
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: W B Hacker <wbh@???>
> To: exim users <exim-users@???>
> Date: Wed, 22 Dec 2010 09:20:56 -0500
> Subject: Re: [exim] address rewrite not working
> Nigel Metheringham wrote:
>
>> On 22 Dec 2010, at 12:31, Johann Spies wrote:
>>
>> Please help me to understand and maybe a practical situation will make
>>> it clear.
>>>
>>> On our campus there several mailservers for which we relayed mail. Then
>>> it happens that one or more of them cease to exist and the mail have to
>>> be delivered at another place (e.g. exchange).
>>>
>>> How would you, without rewriting the email, handle that situation. What
>>> we did was to rewrite it:
>>>
>>
>> There is no need to rewrite in this case. Standard routing would get the
>> email there OK - router given below.
>>
>> However there might be a case to rewrite to ensure that replies (if the
>> sender addresses were in the deprecated domain), or reply-alls go direct
>> to their destination rather than via the deprecated domain.
>>
>> This does have other disadvantages - it is changing mail (which may well
>> have legal implications) and may break digital signatures. Rewriting is
>> generally best avoided for these reasons.
>>
>> Say the mail serves akad and addresses had the pattern:
>>> user@???
>>>
>>> We rewrote it to user@???.
>>>
>>
>> You could have a router like:-
>>
>> redirect_deprecated:
>> driver = redirect
>> domains = akad.sun.ac.za
>> data = ${quote_local_part:$local_part}@???<local_part%7D@???>
>>
>> That would handle the delivery. Any rewriting is cosmetic to that.
>>
>> Nigel.
>>
>
> ACK. That router should JFW, and can be expanded to handle longer lists or
> lookups, eg: 'universal' going forward.
>
> OTOH - '....legal implications'......
>
> IF/AS/WHEN there is a strong(er) need to get the new address or other info
> onto the screen of the senders AND NOT transparently redirect?
>
> One can 'force' the change back upstream by rejecting with a custom error
> message:
>
> # RCPT_4A: IF for former old_example.com THEN advise of change
> #
> deny
> message = Change domain from old_example.com to new_example.com, try
> again
> condition = ${if eq{$domain}{old_example.com}}
> log_message = Caller for old_example.com advised of new_example.com
>
> Multiple-line messages, or even a URI with detailed explanation,
> disclaimer, and per-user custom messages from $local_part lookups also
> possible.
>
> Taken as given that no all Luser will read and heed a DSN / error message,
> os 'best effort' only.
>
> Bill
>
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Alexander Curvers <acurvers@???>
> To: exim-users@???
> Date: Wed, 22 Dec 2010 16:53:51 +0100
> Subject: [exim] delivery not succesfull
> Router logging
>
> im a exim newbie, screwed up my exim reinstalled it same problem persists:
>
> sympton:
> vps123:~# exim4 -d+route -bt info@???
> Exim version 4.69 uid=0 gid=0 pid=21338 D=fbb95cfd
> Berkeley DB: Berkeley DB 4.6.21: (September 27, 2007)
> Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages
> Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb
> dsearch nis nis0 passwd
> Authenticators: cram_md5 plaintext
> Routers: accept dnslookup ipliteral manualroute queryprogram redirect
> Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
> Fixed never_users: 0
> Size of off_t: 8
> changed uid/gid: forcing real = effective
> uid=0 gid=0 pid=21338
> auxiliary group list: <none>
> configuration file is /etc/exim4/exim4.conf
> log selectors = ffffffff 7fffdfff
> trusted user
> admin user
> originator: uid=0 gid=0 login=root name=root
> sender address = root@???
> Address testing: uid=0 gid=106 euid=0 egid=106
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Testing info@???
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Considering info@???
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> routing info@???
> no more routers
> info@??? is undeliverable: Unrouteable address
> search_tidyup called
>
>
> in /etc/aliases i have something like
>
> info : extern@???
>
> =============================
> im on debian my config file:
>
> dc_eximconfig_configtype='internet'
> dc_other_hostnames='vps123.directvps.nl
> ;vps123;localhost;91.214.45.106;194.145.200.153;mailserver.son.nl'
> dc_local_interfaces='*'
> dc_readhost=''
> dc_relay_domains='*'
> dc_minimaldns='false'
> dc_relay_nets='*'
> dc_smarthost=''
> CFILEMODE='644'
> dc_use_split_config='false'
> dc_hide_mailname=''
> dc_mailname_in_oh='true'
> dc_localdelivery='maildir_home'
>
> if anyone has some advice or knows the cause of this problem..
> i also wonder why i dont get any debug messages from the routers ... are
> the
> routers even processed cant find info how to make them give debug info
> other
> then the command im already using:
>
> exim4 -d+route -bt info@???
>
> other question i have is the output shows.. that i use config
> /etc/exim4/exim4.conf
> which has only one line
> log_selector = +-rejected_header
>
> is that normal (on debian)????
> in any case i use the command update-exim4.conf to update the config (but
> where is the final config)
>
>
> Regards Alexander
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Graeme Fowler <graeme@???>
> To: exim-users@???
> Date: Wed, 22 Dec 2010 17:06:10 +0000
> Subject: Re: [exim] address rewrite not working
> On Wed, 2010-12-22 at 14:33 +0000, Always Learning wrote:
> > Why not ?
>
> Well... because it's using a sledgehammer to crack a nut, it's
> inflexible, and it works at the wrong point in the mail flow.
>
> > Exim has been designed, programmed and released to the world to do
> > exactly that ......
>
> To be utterly pedantic about it, the design of Exim is to do
> significantly more than just run the system filter.
>
> > ... please will you kindly enlighten me why it might be advantageous to
> > Exim admins to ignore the system filter facilities (which use a
> > noticeably different syntax from the rest of Exim).
>
> Because using a specific router is more flexible and can be put in an
> appropriate place in the mail flow. The key to this is in the
> documentation:
>
> http://www.exim.org/exim-html-current/doc/html/spec_html/ch43.html
>
> "The system filter operates in a similar manner to users’ filter files,
> but it is run just once per message (however many recipients the message
> has). It should not normally be used as a substitute for routing,
> because deliver commands in a system router provide new envelope
> recipient addresses."
>
> So there you have it - use a redirect router instead.
>
> > Would this forward mail for
> > user1@??? to new.box@??? ?
> >
> > divert_mail
> > driver = redirect
> > domains = old-domain.com
> > local_part = user1
> > data = new.box@???
>
> That looks sane and reasonable, yes. For extra points, save yourself the
> legwork of having additional routers in future by abstracting the
> domains/local_part/data parts out into a lookup. Then next time you need
> to divert mail, you can add an entry to your lookup table.
>
> Graeme
>
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Johann Spies <jspies@???>
> To: exim-users@???
> Date: Thu, 23 Dec 2010 08:51:54 +0200
> Subject: Re: [exim] delivery not succesfull
> On Wed, Dec 22, 2010 at 05:53:51PM +0200, Alexander Curvers wrote:
> >
> > im a exim newbie, screwed up my exim reinstalled it same problem
> persists:
> > configuration file is /etc/exim4/exim4.conf
>
> I have never seen this on a Debian system. I am using the I use the
> divided
> config placed in /etc/exim4/conf.d.
>
> The only files in my /etc/exim4 is :
> conf.d exim4.conf.template exim-ldap-client-v4.conf
> exim-ldap-server-v4.conf passwd.client update-exim4.conf.conf
>
> > =============================
> > im on debian my config file:
> >
> > dc_eximconfig_configtype='internet'
>
>
> > dc_other_hostnames='vps123.directvps.nl
> > ;vps123;localhost;91.214.45.106;194.145.200.153;mailserver.son.nl'
>
> Maybe the debian-exim mailing list would be a better place to ask about
> this
> Debian-specific file. Can you explain why you put these hosts together
> there?
>
> > is that normal (on debian)????
> > in any case i use the command update-exim4.conf to update the config (but
> > where is the final config)
>
> If you use update-exim4.conf the config file is
> /var/lib/exim4/config.autogenerated.
>
> Regards
> Johann
>
> --
> Johann Spies Telefoon: 021-808 4699
> Databestuurder / Data manager
>
> Sentrum vir Navorsing oor Evaluasie, Wetenskap en Tegnologie
> Centre for Research on Evaluation, Science and Technology
> Universiteit Stellenbosch.
>
> "And there were in the same country shepherds abiding
> in the field, keeping watch over their flock by night.
> And, lo, the angel of the Lord came upon them, and the
> glory of the Lord shone round about them: and they were
> sore afraid. And the angel said unto them, Fear not:
> for behold I bring you good tidings of great joy, which
> shall be to all people. For unto you is born this day
> in the city of David a Saviour, which is Christ the
> Lord." Luke 2:8-11
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Peter Bowyer <peter@???>
> To: exim-users@???
> Date: Thu, 23 Dec 2010 06:55:55 +0000
> Subject: Re: [exim] delivery not succesfull
> On 22 December 2010 15:53, Alexander Curvers <acurvers@???> wrote:
> > im on debian my config file:
>
> Debian config support is done on the mailing list mentioned in your
> Debian Exim docs, not here.
>
> > other question i have is the output shows.. that i use config
> > /etc/exim4/exim4.conf
> > which has only one line
> > log_selector = +-rejected_header
> >
> > is that normal (on debian)????
>
> That would explain why mail isn't getting routed - you've got no
> config, Seems you might have taken the sticking-plaster security fix
> and messed your config up with it.
>
> > in any case i use the command update-exim4.conf to update the config (but
> > where is the final config)
>
> Again, a Debian config question which will better be answered on the
> Debian list.
>
> Peter
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: WJCarpenter <bill-exim@???>
> To: exim-users@???
> Date: Thu, 23 Dec 2010 00:47:47 -0800
> Subject: [exim] filter "mail" and envelope "from"
> For the first time (I think), I'm putting some "mail" commands into an exim
> filter file (personal, not system). Until now, I've always used "deliver".
> Whenever I do "mail", the envelope sender is empty. This matters because
> the place I'm trying to "mail" to discards them (I reckon because it assumes
> they are bounce notifications).
>
> Have I overlooked something? I've been thumbing through the Exim book and
> the filter spec for a while. I think the envelope sender address is empty
> because that's what the autoreply transport does. Is there any way around
> that? Or, do others handle this a different way?
>
> BTW, the reason I want to use "mail" instead of "deliver" is because I want
> to send only the beginning of the message body.
>
>
>
>
>
> ---------- Doorgestuurd bericht ----------
> From: Phil Pennock <exim-users@???>
> To: WJCarpenter <bill-exim@???>
> Date: Thu, 23 Dec 2010 05:54:23 -0500
> Subject: Re: [exim] filter "mail" and envelope "from"
> On 2010-12-23 at 00:47 -0800, WJCarpenter wrote:
> > For the first time (I think), I'm putting some "mail" commands into an
> > exim filter file (personal, not system). Until now, I've always used
> > "deliver". Whenever I do "mail", the envelope sender is empty. This
> > matters because the place I'm trying to "mail" to discards them (I
> > reckon because it assumes they are bounce notifications).
> >
> > Have I overlooked something? I've been thumbing through the Exim book
> > and the filter spec for a while. I think the envelope sender address is
> > empty because that's what the autoreply transport does. Is there any
> > way around that? Or, do others handle this a different way?
>
> filter.txt, 3.14:
> ----------------------------8< cut here >8------------------------------
> To help prevent runaway message sequences, these commands have no effect
> when
> the incoming message is a bounce (delivery error) message, and messages
> sent by
> this means are treated as if they were reporting delivery errors. Thus,
> they
> should never themselves cause a bounce message to be returned. The basic
> mail-sending command is
> ----------------------------8< cut here >8------------------------------
>
> You haven't overlooked anything, this is hard-coded and doesn't have an
> option to change it. There's another approach though.
>
> How about a Sieve script with a "redirect" and another action too?
> Probably "keep".
>
> -Phil
>
>
>
> --
>
> ## List details at http://lists.exim.org/mailman/listinfo/exim-users Exim
> details at http://www.exim.org/ ##
>
>
