headers
Ian Eiloart | 4 Jul 2011 16:10
Picon
Favicon
Gravatar

[Bug 1103] exiqgrep fails on messages smaller 1K

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1103

Nigel Metheringham <nigel <at> exim.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|Exim 4.76                   |Exim 4.77

Ian Eiloart <iane <at> sussex.ac.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |iane <at> sussex.ac.uk

--- Comment #1 from Ian Eiloart <iane <at> sussex.ac.uk>  2011-07-04 15:10:23 ---
The change works for me, though [KMG]{0,1} is arguably a bit safer.

--

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
Permalink | Reply | 0 comments |
headers
Holger Weiß | 12 Jul 2011 16:04
Picon
Picon

[Bug 1131] New: Command executed via ${run} hangs when pipe buffer is filled

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1131
           Summary: Command executed via ${run} hangs when pipe buffer is
                    filled
           Product: Exim
           Version: 4.76
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: bug
          Priority: medium
         Component: String expansion
        AssignedTo: nigel <at> exim.org
        ReportedBy: holger <at> CIS.FU-Berlin.DE
                CC: exim-dev <at> exim.org, heiko <at> fu-berlin.de

Created an attachment (id=490)
 --> (http://bugs.exim.org/attachment.cgi?id=490)
Read pipe during execution

When the amount of output created by a command executed via ${run} exceeds the
operating system's pipe buffer size (e.g., 64k on Linux 2.6), the command's
output functions will (usually) block, so that the command will run into Exim's
timeout.  This happens because Exim waits for the command to exit before
attempting to read its output.  The attached patch fixes this problem.

--

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
(Continue reading)

Permalink | Reply | 2 comments |
headers
Gedalya | 12 Jul 2011 21:19

[Bug 1031] Implement database logging of completed remote delivery

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1031

Nigel Metheringham <nigel <at> exim.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|Exim 4.73                   |Exim 4.77

Gedalya <gedalya <at> gedalya.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gedalya <at> gedalya.net

--- Comment #4 from Gedalya <gedalya <at> gedalya.net>  2011-07-12 20:19:15 ---
Hi,

This feature would be very useful for me. Would it be possible to add a query
to be executed for failed deliveries? Something like dbl_deliveryfailed_query?
The purpose for me would be to keep track of when remote hosts are down, so
that they can be automatically prioritized based on their performance. I'm
talking about data similar to what is kept in exim's retry db, but I could use
more complete and detailed records of successful and failed delivery attempts,
stored in a SQL database where cool things can be done with it.
The negative counterpart of dbl_delivery_query would be perfect.

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Axel Rau | 14 Jul 2011 00:10
Picon

[Bug 1031] Implement database logging of completed remote delivery

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1031

--- Comment #5 from Axel Rau <axel.rau <at> chaos1.de>  2011-07-13 23:10:28 ---
Am 12.07.2011 um 21:19 schrieb gedalya <at> gedalya.net:

> Would it be possible to add a query
> to be executed for failed deliveries? Something like dbl_deliveryfailed_query?
Sure. Based on what's available in deliver.c, it may be possible to set the
following variables:
        dbl_delivery_ip             IP of host, which has accepted delivery
        dbl_delivery_fqdn           FQDN of host, which has accepted delivery
        dbl_delivery_local_part     local part of address being delivered
        dbl_delivery_domain         domain part of address being delivered
        dbl_delivery_failure_reason a reason code

My knowledge of the retry mechanism is very limited.
Do we need to put the hook into retry.c to get all delivery attempts?

--

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
Permalink | Reply | 0 comments |
headers
Gedalya | 14 Jul 2011 01:58

[Bug 1031] Implement database logging of completed remote delivery

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1031

--- Comment #6 from Gedalya <gedalya <at> gedalya.net>  2011-07-14 00:58:30 ---
On 7/13/2011 6:10 PM, Axel Rau wrote:
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
>
> http://bugs.exim.org/show_bug.cgi?id=1031
>
>
>
>
> --- Comment #5 from Axel Rau<axel.rau <at> chaos1.de>   2011-07-13 23:10:28 ---
> Am 12.07.2011 um 21:19 schrieb gedalya <at> gedalya.net:
>
>> Would it be possible to add a query
>> to be executed for failed deliveries? Something like dbl_deliveryfailed_query?
> Sure. Based on what's available in deliver.c, it may be possible to set the
> following variables:
>          dbl_delivery_ip             IP of host, which has accepted delivery
>          dbl_delivery_fqdn           FQDN of host, which has accepted delivery
>          dbl_delivery_local_part     local part of address being delivered
>          dbl_delivery_domain         domain part of address being delivered
>          dbl_delivery_failure_reason a reason code
>
> My knowledge of the retry mechanism is very limited.
> Do we need to put the hook into retry.c to get all delivery attempts?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Isaac | 18 Jul 2011 19:13
Favicon

[Bug 1132] New: #define'ing USE_TCP_WRAPPERS when USE_TCP_WRAPPERS=no

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1132
           Summary: #define'ing USE_TCP_WRAPPERS when USE_TCP_WRAPPERS=no
           Product: Exim
           Version: 4.76
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Unfiled
        AssignedTo: nigel <at> exim.org
        ReportedBy: zexim <at> isaacgood.com
                CC: exim-dev <at> exim.org

In Local/Makefile line 887 I have: 
  USE_TCP_WRAPPERS=no

Running make, I find in build-Linux-i386/config.h line 132:
  #define USE_TCP_WRAPPERS      no

Unfortunately, defining `USE_TCP_WRAPPERS` triggers the `#ifdef
USE_TCP_WRAPPERS` blocks and exim tries to compile against tcp_wrappers,
failing when it fails to find tcpd.h

Rather than defining USE_TCP_WRAPPERS as no, it should not be defined at all,
allowing `#ifdef USE_TCP_WRAPPERS` and a tcp_wrappers-less build.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ted Cooper | 19 Jul 2011 14:17
Favicon

[Bug 1132] #define'ing USE_TCP_WRAPPERS when USE_TCP_WRAPPERS=no

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1132

Ted Cooper <eximX0902w <at> linuxwan.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eximX0902w <at> linuxwan.net
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Ted Cooper <eximX0902w <at> linuxwan.net>  2011-07-19 13:17:20 ---
This is the original content from the Makefile

# TCP wrappers: If you want to use tcpwrappers from within Exim, uncomment
# this setting. See the manual section entitled "Use of tcpwrappers" in the
# chapter on building and installing Exim.
#
# USE_TCP_WRAPPERS=yes

This is fairly common of all #ifdef style Makefiles - to enable it, uncomment
it; to disable it, comment it. There is no direction to define it as "no", it
just needs to be defined as something for it to be enabled.

It's seems the bug resolution you have provided is exactly how it is designed
to work.

--

--
(Continue reading)

Permalink | Reply | 0 comments |

Gmane