Phil Pennock | 28 Aug 05:20 2015

exim .editorconfig -- any objections?

In closing an old review PR on GitHub, I saw that I'd suggested that
rather than add vim directives to files in Exim's tree, we should
consider using EditorConfig.  And that was two years ago.

So, uh, let's try that?

Anyone object to my merging in this `.editorconfig` file in the
top-level of the Exim tree?

  http://git.exim.org/users/pdp/exim.git/commitdiff/bf5ffbb0aff762cd4640141a76a3afebad02ad89
  https://github.com/Exim/exim/compare/editorconfig

I _think_ that it reflects what's as close to common practice as we
come.

Thanks,
-Phil

--

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at
http://www.exim.org/ ##
Iti Monitor | 27 Aug 13:34 2015
Picon

Bug in smtp_banner?

EXIM smtp_banner field configuration not working

Hello,

Issue: I wanted to hide the EXIM version number in order to avoid malicious
email scanners to get information from EXIM.

Bug: I removed the ${version_number} part on WHM>EXIM Configuration
Manager>Advanced Editor>smtp_banner and rebooted EXIM. Funilly enough, the
sent emails [u]were still showing EXIM's version in their headers[/u].

Solution: remove the line ESMTP Exim \#${compile_number} ${tod_full} from
the EXIM configuration file. That did the trick and now sent emails have
not anymore information about EXIM's version.

Please, could you check if this is a bug, or perhaps I am missing
something? Ideally, when we change the smtp_banner field, it must change
the sent emails' headers, without need to delete anything in the EXIM
configuration file.

rgs

IM
--

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at
http://www.exim.org/ ##
admin | 23 Aug 10:25 2015

[Bug 1678] New: retry rules are confused by different static interface settings.

https://bugs.exim.org/show_bug.cgi?id=1678

            Bug ID: 1678
           Summary: retry rules are confused by different static interface
                    settings.
           Product: Exim
           Version: N/A
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Transports
          Assignee: nigel <at> exim.org
          Reporter: eximbugzilla <at> revmaps.no-ip.org
                CC: exim-dev <at> exim.org

if I have two SMTP tranports with different constant (not expanded) interface
settings retry hints for the two transports are shared.  

so if transport_bulk get rate-limited by example.com exim will see this when
choosing mail for on the tranport_transactional

a cooment from transports/smtp.c (around line 3352)

 /* Select IPv4 or IPv6, and choose an outgoing interface. If the interface
string changes upon expansion, we must add it to the key that is used for
retries, because connections to the same host from a different interface
should be treated separately. */

(Continue reading)

admin | 23 Aug 10:07 2015

[Bug 1677] New: transports should check setup parameters when continuing.

https://bugs.exim.org/show_bug.cgi?id=1677

            Bug ID: 1677
           Summary: transports should check setup parameters when
                    continuing.
           Product: Exim
           Version: N/A
          Hardware: All
                OS: All
            Status: NEW
          Severity: wishlist
          Priority: medium
         Component: Transports
          Assignee: nigel <at> exim.org
          Reporter: eximbugzilla <at> revmaps.no-ip.org
                CC: exim-dev <at> exim.org

spec 30.1.2 says

When a message has been successfully delivered over a TCP/IP connection, Exim
looks in its hints database to see if there are any other messages awaiting a
connection to the same host. If there are, a new delivery process is started
for one of them, and the current TCP/IP connection is passed on to it. The new
process may in turn send multiple copies and possibly create yet another
process. 

And thats is an accurate description.

 However this behaviour is problematic when one desires to route different
classes of message trough different source IP addresses (using an expansion
(Continue reading)

admin | 21 Aug 19:27 2015

[Bug 264] A variable containing the error for verify = header_syntax

https://bugs.exim.org/show_bug.cgi?id=264

Git Commit <git <at> exim.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |git <at> exim.org

--- Comment #3 from Git Commit <git <at> exim.org> ---
Git commit:
http://git.exim.org/exim.git/commitdiff/3703d8187af01d13ca71f7918c7ef78529bb784d

commit 3703d8187af01d13ca71f7918c7ef78529bb784d
Author:     Jeremy Harris <jgh146exb <at> wizmail.org>
AuthorDate: Fri Aug 21 18:08:39 2015 +0100
Commit:     Jeremy Harris <jgh146exb <at> wizmail.org>
CommitDate: Fri Aug 21 18:08:39 2015 +0100

    remember the fail reason for verify=headers_syntax.  bug 264
----
 src/src/acl.c    | 30 ++++++++++++++++------------
 test/confs/0086  |  3 ++-
 test/stderr/0086 | 61 +++++++++++++++++++++++++++++++++++---------------------
 3 files changed, 57 insertions(+), 37 deletions(-)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
--

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at
(Continue reading)

admin | 21 Aug 19:11 2015

[Bug 264] A variable containing the error for verify = header_syntax

https://bugs.exim.org/show_bug.cgi?id=264

Jeremy Harris <jgh146exb <at> wizmail.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
   Target Milestone|Exim 4.77                   |Exim 4.87
           Assignee|nigel <at> exim.org              |jgh146exb <at> wizmail.org

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
--

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at
http://www.exim.org/ ##
admin | 19 Aug 11:23 2015

[Bug 264] A variable containing the error for verify = header_syntax

https://bugs.exim.org/show_bug.cgi?id=264

Jeremy Harris <jgh146exb <at> wizmail.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jgh146exb <at> wizmail.org

--- Comment #2 from Jeremy Harris <jgh146exb <at> wizmail.org> ---
$acl_verify_message would seem obvious, but it's not filled in for
header_syntax.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
--

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at
http://www.exim.org/ ##
admin | 17 Aug 19:24 2015

[Bug 1671] New: segfault after delivery

https://bugs.exim.org/show_bug.cgi?id=1671

            Bug ID: 1671
           Summary: segfault after delivery
           Product: Exim
           Version: 4.86
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Delivery in general
          Assignee: nigel <at> exim.org
          Reporter: jgh146exb <at> wizmail.org
                CC: exim-dev <at> exim.org

GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
[...]
Reading symbols from /opt/exim/bin/exim-4.86-7...(no debugging symbols
found)...done.
(gdb) core /tmp/exim.core.1439805965.29112
warning: core file may not match specified executable file.
[New LWP 29112]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/opt/exim/bin/exim -Mc 1ZRHIo-0007ZK-V3'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000475eda in string_copy ()
(gdb) where
#0  0x0000000000475eda in string_copy ()
(Continue reading)

admin | 6 Aug 17:25 2015

[Bug 1668] New: RFE: sasl_user_exists condition

https://bugs.exim.org/show_bug.cgi?id=1668

            Bug ID: 1668
           Summary: RFE: sasl_user_exists condition
           Product: Exim
           Version: 4.85+ HEAD
          Hardware: All
                OS: All
            Status: NEW
          Severity: wishlist
          Priority: medium
         Component: String expansion
          Assignee: nigel <at> exim.org
          Reporter: bob <at> lorez.org
                CC: exim-dev <at> exim.org

Created attachment 827
  --> https://bugs.exim.org/attachment.cgi?id=827&action=edit
Patch to implement cyrus_sasl_user_exists expansion

Exim currently has support to perform authentication tests using libsasl2, for
the purposes of SMTP authentication. It's missing the ability to query whether
a local user exists, for the purpose of determining whether to reject a RCPT.

In general, the thing to do in this case is to perform an LMTP callout in order
to determine whether there is a mailbox that exists for the given recipient.

However, Cyrus IMAP now has a feature that allows mailboxes to be automatically
created upon successful login, or a delivery is made to a mailbox that doesn't
exist yet.
(Continue reading)

Bob Richmond | 6 Aug 02:57 2015

PATCH: sasl_user_exists condition

Exim currently has support to perform authentication tests using 
libsasl2, for the purposes of SMTP authentication. It's missing the 
ability to query whether a local user exists, for the purpose of 
determining whether to reject a RCPT.

In general, the thing to do in this case is to perform an LMTP callout 
in order to determine whether there is a mailbox that exists for the 
given recipient.

However, Cyrus IMAP now has a feature that allows mailboxes to be 
automatically created upon successful login, or a delivery is made to a 
mailbox that doesn't exist yet.

It would be exceedingly convenient to test for the existence of a local 
user in the same SASL DB that Cyrus looks for users, rather than via 
LMTP so that we can turn this automatic mailbox creation feature on 
without arbitrarily creating a new mailbox for addresses no one will 
ever log into. This patch for your consideration, allows for that by 
introducing a new string expansion called "cyrus_sasl_user_exists", that 
expects a username, optional service, and optional realm. Adding the 
condition to your LMTP router will let you specify:

acl_check_rcpt:

accept domains = +local_domains
verify = recipient

begin routers

cyrus:
(Continue reading)

admin | 3 Aug 11:04 2015

[Bug 1666] New: exim should log unexpanded queries

https://bugs.exim.org/show_bug.cgi?id=1666

            Bug ID: 1666
           Summary: exim should log unexpanded queries
           Product: Exim
           Version: 4.86
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Logging
          Assignee: nigel <at> exim.org
          Reporter: arekm <at> maven.pl
                CC: exim-dev <at> exim.org

If you use authenticator query like this:

server_condition = ${lookup mysql{SELECT .... WHERE
ENCRYPT('${quote_mysql:$auth2}')...}

then in case of sql db problems exim will happily log expanded query revealing
auth2 in plain text for example. Depending on user queries such logging my
reveal many things.

Like:

2015-08-03 10:21:36 login authenticator failed for ...: 435 Unable to
authenticate at present ...: lookup of "SELECT
...ENCRYPT('my-secret-pass-1234'...gave DEFER: MYSQL connection failed: Access
(Continue reading)


Gmane