Jeremy Harris | 30 Jul 20:41 2014

[Bug 1513] New: mime handling broken

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

http://bugs.exim.org/show_bug.cgi?id=1513
           Summary: mime handling broken
           Product: Exim
           Version: 4.83
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: bug
          Priority: high
         Component: ACLs
        AssignedTo: jgh146exb <at> wizmail.org
        ReportedBy: jgh146exb <at> wizmail.org
                CC: exim-dev <at> exim.org

Seems like 4.83 breaks the mime ACL:

1)  "I've logged $mime_filename for all attachments.  I see that it is now
quoted but looking back through older logs, it wasn't before."

https://lists.exim.org/lurker/message/20140729.150921.14661476.en.html

2) "mainlog shows that acl_check_mime was called only once"

https://lists.exim.org/lurker/message/20140730.142622.5f693c48.en.html

--

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

Andreas Metzler | 30 Jul 19:28 2014
Picon

[Bug 1512] New: dovecot authenticator waits for server's DONE before sending DATA

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

http://bugs.exim.org/show_bug.cgi?id=1512
           Summary: dovecot authenticator waits for server's DONE before
                    sending DATA
           Product: Exim
           Version: 4.83
          Platform: Other
               URL: http://bugs.debian.org/756258
        OS/Version: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: SMTP Authentication
        AssignedTo: pdp <at> exim.org
        ReportedBy: eximusers <at> bebt.de
                CC: exim-dev <at> exim.org

Hello,

this is <http://bugs.debian.org/756258> as submitted by Mildred Ki'Lya:

<Quote>
When exim4 is configured with dovecot authenticator, it blocks at some
point, apparently expecting some information from dovecot. Dovecot on its
side is expecting additional information from exim. None of the two
parties move forward and exim do not respond to the SMTp client. After
some unspecified time, the MUA terminates the connection, because no
response is sent from the server.
(Continue reading)

Martin Nicholas | 30 Jul 16:59 2014
Picon

[Bug 1511] New: Need to run code (string expansion) for AUTH failures

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

http://bugs.exim.org/show_bug.cgi?id=1511
           Summary: Need to run code (string expansion) for AUTH failures
           Product: Exim
           Version: N/A
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: wishlist
          Priority: medium
         Component: SMTP Authentication
        AssignedTo: pdp <at> exim.org
        ReportedBy: exim_bugs-throw <at> mgn.org.uk
                CC: exim-dev <at> exim.org

Seeing more and more attempts to login with bogus criteria so a "message"
modifier for all the authenticators would be useful. Thus the IPs concerned can
be placed in a blacklist.

--

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

Clouds | 30 Jul 09:33 2014
Picon

[Bug 1510] New: Alleged out of bounds read in filter

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

http://bugs.exim.org/show_bug.cgi?id=1510
           Summary: Alleged out of bounds read in filter
           Product: Exim
           Version: 4.83
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: security
          Priority: medium
         Component: Filters
        AssignedTo: nigel <at> exim.org
        ReportedBy: clouds <at> riseup.net
                CC: exim-dev <at> exim.org

To whom it may concern;

I apologize for communicating to bugreports but I am unable to find
Exim's public-facing vulnerability communication mechanism.

It looks like there is a out of bound read within Exim - 4.83 (as
pulled from
http://ftp.univie.ac.at/applications/exim/exim/exim4/exim-4.83.tar.gz
)

Within filter.c - line 39, union argtypes args[1] is declared.  Which results
in argtypes args having an allocated size of 8 bytes.  
So further along, within filter.c - line 2335, interpret_commands(), args
(Continue reading)

Wolfgang Breyha | 29 Jul 16:43 2014
Picon
Picon

[Bug 1509] New: Mssing support for EXPERIMENTAL_DSN spool file extension

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

http://bugs.exim.org/show_bug.cgi?id=1509
           Summary: Mssing support for EXPERIMENTAL_DSN spool file extension
           Product: Exim
           Version: 4.83
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Exipick
        AssignedTo: nigel <at> exim.org
        ReportedBy: wbreyha <at> gmx.net
                CC: exim-dev <at> exim.org

Created an attachment (id=744)
 --> (http://bugs.exim.org/attachment.cgi?id=744)
EXPERIMENTAL_DSN support

exipick lacks of a generic way to interpret the exim4 spool file format and
fails to read recipient lines written by the EXPERIMENTAL_DSN extensions (see
#118). This results in misleading output containing mails with no recipients at
all.

I added support for DSN, but no generic code.

--

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

Kirill Miazine | 23 Jul 15:21 2014

[Bug 1507] New: ":" expected after "def" inside "and{...}" condition

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

http://bugs.exim.org/show_bug.cgi?id=1507
           Summary: ":" expected after "def" inside "and{...}" condition
           Product: Exim
           Version: 4.83
          Platform: Other
        OS/Version: OpenBSD
            Status: NEW
          Severity: bug
          Priority: medium
         Component: String expansion
        AssignedTo: nigel <at> exim.org
        ReportedBy: km <at> krot.org
                CC: exim-dev <at> exim.org

Hi

I have had the following options on my remote smtp transport for ages:

    headers_add = ${if and{\
                           {def:sender_host_authenticated}\
                           {def:authenticated_id}\
                          }\
                    {X-Anonymized-by: $smtp_active_hostname
($tod_log)\nADD_HEADERS}\
                    {ADD_HEADERS}}
    headers_remove = ${if and{\
                              {def:sender_host_authenticated}\
(Continue reading)

Lars Müller | 23 Jul 15:08 2014
Picon

[Bug 1506] New: expand.c:1882 compile fails with no-return-in-nonvoid-function

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

http://bugs.exim.org/show_bug.cgi?id=1506
           Summary: expand.c:1882 compile fails with no-return-in-nonvoid-
                    function
           Product: Exim
           Version: 4.83
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: bug
          Priority: high
         Component: Unfiled
        AssignedTo: nigel <at> exim.org
        ReportedBy: lars <at> samba.org
                CC: exim-dev <at> exim.org, jgh146exb <at> wizmail.org

commit 9d1c15ef45fcc8809349378922de20ae9a774c75 removed

  return NULL;          /* Unknown variable name */

from the end of find_variable() in src/expand.c  This results in

[   83s] E: exim no-return-in-nonvoid-function expand.c:1882

while building exim.

Cf. https://build.opensuse.org/package/show/server:mail/exim project.

(Continue reading)

Miro | 22 Jul 14:53 2014
Picon

[Bug 1505] New: Misleading message "clamd: failed to connect to 127.0.0.1: couldn't connect to any host: Connection refused"

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

http://bugs.exim.org/show_bug.cgi?id=1505
           Summary: Misleading message "clamd: failed to connect to
                    127.0.0.1: couldn't connect to any host: Connection
                    refused"
           Product: Exim
           Version: 4.82
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: bug
          Priority: low
         Component: Logging
        AssignedTo: nigel <at> exim.org
        ReportedBy: bug <at> mejor.pl
                CC: exim-dev <at> exim.org

I have defined connection to av_scanner as below:
av_scanner  = clamd:127.0.0.1 3310 : 192.168.254.10 3310

On localhost clamav is turned off. When I sent eicar test I got in
exim_main.log:

# exigrep 1X1cPB-0001CM-E1 /var/log/exim/exim_main.log
+++ 1X1cPB-0001CM-E1 has not completed +++
2014-06-30 16:18:01 1X1cPB-0001CM-E1 DKIM: d=cibet.pl s=120625
c=relaxed/relaxed a=rsa-sha256 [verification succeeded]
2014-06-30 16:18:01 1X1cPB-0001CM-E1 malware acl condition: clamd:
(Continue reading)

Darren M | 8 Jul 14:52 2014
Picon

[Bug 1501] New: Transport uses IPv6 route to deliver mail eventhough IPv4 address specified as "interface"

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

http://bugs.exim.org/show_bug.cgi?id=1501
           Summary: Transport uses IPv6 route to deliver mail eventhough
                    IPv4 address specified as "interface"
           Product: Exim
           Version: 4.82
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Transports
        AssignedTo: nigel <at> exim.org
        ReportedBy: darren <at> cpanel.net
                CC: exim-dev <at> exim.org

Created an attachment (id=738)
 --> (http://bugs.exim.org/attachment.cgi?id=738)
Debug log and transport

From a server with both IPv4/IPv6 support, to another server with both
IPv4/IPv6 support, the "interface" option appears to be partially ignored when
choosing how to send the mail. If an IPv6 address is in the list for the
interface, it will be used, however if it is an IPv4 address, exim will select
the default IPv6 address of the sending server instead.

I'm attaching a debug log and the transport I was using. The transport is at
the bottom of the log. You can see the other commented out options I was trying
(Continue reading)

Todd Lyons | 8 Jul 18:28 2014

Exim 4.83 RC3 uploaded


I have uploaded Exim 4.83 RC3 to
ftp://ftp.exim.org/pub/exim/exim4/test/ 

Compared to the RC2 release, this RC3 release contains only small fixes:
reinstate SNI variables under GnuTLS,enhancing documentation and fixing
typos, fix build dependencies, fix test suite cases, tidying the coding
style, taking more care with time types.

The ChangeLog/NewStuff/README.Updating for 4.83 can be viewed at:

http://git.exim.org/exim.git/blob/exim-4_83_RC3:/doc/doc-txt/ChangeLog
http://git.exim.org/exim.git/blob/exim-4_83_RC3:/doc/doc-txt/NewStuff
http://git.exim.org/exim.git/blob/exim-4_83_RC3:/src/README.UPDATING 

The files are signed with the PGP key 0x04D29EBA, which has a uid
"Todd Lyons (Exim Maintainer) <tlyons <at> exim.org>". Please use your own
discretion in assessing what trust paths you might have to this uid.

Checksums below. Detached PGP signatures in .asc files are available
alongside the tarballs.

Please report issues by replying to this email on exim-users or exim-dev
mailing lists. Please include the OS, distro, version, and any other
build information including specific build features enabled in your
correspondence. If you have feedback and need to keep your organization
confidential, you may reply directly to me or any other Exim developer
with your success story or concerns. All feedback is appreciated right
before a release, even if it's just says "It built fine on $OS/$DISTRO"!

(Continue reading)

Matthias-Christian Ott | 5 Jul 00:07 2014

[Bug 1499] New: $tls_sni, $tls_in_sni and $tls_out_sni are not available when compiled against GnuTLS

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

http://bugs.exim.org/show_bug.cgi?id=1499
           Summary: $tls_sni, $tls_in_sni and $tls_out_sni are not available
                    when compiled against GnuTLS
           Product: Exim
           Version: 4.82
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: bug
          Priority: medium
         Component: TLS
        AssignedTo: pdp <at> exim.org
        ReportedBy: ott <at> mirix.org
                CC: exim-dev <at> exim.org

Exim compiled against GnuTLS, $tls_sni, $tls_in_sni and $tls_out_sni are not
available. In 4.80 $tls_sni was available.

It seems the this bug was introduced in commit
d9b2312be1c63d0bf94dfaea9c82c6def6b45884. It removed the preprocessor
conditions and made the variables available, but they were always empty. I
don't have a test system for the system that is affected by this bug, so I
couldn't do any further testing or development.

--

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

(Continue reading)


Gmane