Re: [exim] Delivery Status Notification (Failure)

Top Page
Delete this message
Reply to this message
Author: paul cooper
Date:  
To: exim-users
Subject: Re: [exim] Delivery Status Notification (Failure)
im giving up on the cpanel hosting and going to try and run this off my
ubuntu LAN server with multiple smtp authentication and rate-limited to
the relevant ISP smarthost
I (well, my wife) can then send from the email client on the LAN, it can
be queued on
my server and then send 1 every 30 secs.
Im not sure which of the ACLs listed here
http://www.exim.org/exim-html-current/doc/html/spec_html/ch40.html
i need to configure (? EHLO for when exim talks to the smarthost ? )
or which of the debian/ubuntu files id need to edit to add the ACL
# ls -l /etc/exim4/acl
total 32
-rw-r--r-- 1 root root 297 2011-01-06 09:47 00_exim4-config_header
-rw-r--r-- 1 root root 1759 2011-01-06 09:47
20_exim4-config_local_deny_
exceptions
-rw-r--r-- 1 root root 414 2011-01-06 09:47 30_exim4-config_check_mail
-rw-r--r-- 1 root root 14706 2011-01-06 09:47 30_exim4-config_check_rcpt
-rw-r--r-- 1 root root 2533 2011-01-06 09:47 40_exim4-config_check_data

or do I add my own eg 25_exim4-config_local_delay ?

On 15 November 2011 09:06, W B Hacker <wbh@???> wrote:
>
> > paul cooper wrote:
> >
> >> My ISP limits me to 150 emails/hr (even through their cpanel mailman
> >> application!)
> >> i would like to add a delay =30 secs to my own exim config so i can deal
> >> with the mailing list 'in house'
> >> Im using ubuntu server + exim.
> >>
> >> Its not clear (to me) where and how to configure the delay ACL
> >> Anyone able to offer any pointers
> >>
> >>
> >> thanks
> >>
> >>
> > So long as you can ID the sending MLM/app, all you need is the clause
> that
> > detects it and a line with:
> >
> > 'delay = 30s'
> >
> > Doesn't much matter what 'phase' of the smtp session it is hung onto, but
> > in general earlier is better.
> >
> > If the invocation does NOT travel by, or is not exclusively by, way-of a
> > proper smtp 'session', eg; the binary is called from on same-box - then
> it
> > will either/also have to appear in an acl_not_smtp construct, which may
> not
> > yet exist in any form at present in your config.
> >
>
>