headers
Nigel Metheringham | 7 Apr 2011 09:35
Favicon
Gravatar

[Bug 1101] Adding email address to whitelist does not exclude it from Message ID header check

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

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Nigel Metheringham <nigel <at> exim.org>  2011-04-07 08:35:30 ---
Your exclusion is in the RCPT ACL, but the header checks will have to be done
in an entirely different ACL at message receive time.

This is a configuration issue, not an exim bug.

If you need assistance with the configuration then this should be taken up on
the exim-users mailing list.

The exim version is also rather old.

--

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
Permalink | Reply | 0 comments |
headers
Glen | 7 Apr 2011 08:45
Picon
Favicon

[Bug 1101] New: Adding email address to whitelist does not exclude it from Message ID header check

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

http://bugs.exim.org/show_bug.cgi?id=1101
           Summary: Adding email address to whitelist does not exclude it
                    from Message ID header check
           Product: Exim
           Version: 4.63
          Platform: Other
        OS/Version: Windows
            Status: NEW
          Severity: bug
          Priority: medium
         Component: ACLs
        AssignedTo: nigel <at> exim.org
        ReportedBy: gpecats <at> hotmail.com
                CC: exim-dev <at> exim.org

Hi

We currently run Exim in combination with SpamAssasin on a RHEL4 server.

The way it is setup with the ACL is that it initially performs a check of a
specified file which contains "Safe Sender email addresses", and automatically
should allow these emails in without performing all of the ACL sender checks.

However we have tried adding an address to this safe sender list but the emails
from this sender still get rejected for not containing a Message ID header

This is the start of the ACL:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Todd Lyons | 7 Apr 2011 17:32
Gravatar

Re: [Bug 1101] New: Adding email address to whitelist does not exclude it from Message ID header check

On Wed, Apr 6, 2011 at 11:45 PM, Glen <gpecats <at> hotmail.com> wrote:

Glen, it's not a bug in exim.  It's a limitation in the way that you
have exim configured.

>  # Put simple tests first. A good one is to check for the presence of a
>  # Message-Id: header, which RFC2822 says SHOULD be present. Some broken
>  # or misconfigured mailer software occasionally omits this from genuine
>  # messages too, though -- although it's not hard for the offender to fix
>  # after they receive a bounce because of it.
>  #
>  deny    condition  = ${if !def:h_Message-ID: {1}}

               !hosts  = nwildsearch;/path/to/msgid_exclusions.txt

>          message    = RFC2822 says that all mail SHOULD have a Message-ID
> header.\n\
>                       Most messages without it are spam, so your mail has been
> rejected.

> Is there any way around this - we do not want to disable this check entirely ?
> A bugfix perhaps or any suggestions for recoding the ACL ?

It's not a bugfix, add the line above, modifying the path to suit your
environment, then in that msgid_exclusions.txt, put the ip addreses
you do not want this check to be done for.  For example:

192.168.*    # this is all your internal hosts
10.*            # more internal hosts
*.gpecats.com  # All of the machines you control
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marc Perkel | 11 Apr 2011 20:49

[Bug 1102] New: Divide by zero in eval/acl not reported in logs

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

http://bugs.exim.org/show_bug.cgi?id=1102
           Summary: Divide by zero in eval/acl not reported in logs
           Product: Exim
           Version: 4.75
          Platform: Other
        OS/Version: Windows
            Status: NEW
          Severity: bug
          Priority: high
         Component: ACLs
        AssignedTo: nigel <at> exim.org
        ReportedBy: marc <at> perkel.com
                CC: exim-dev <at> exim.org

This piece of code

set acl_c_ratio = ${eval:$acl_c_bad_rcpt_count_60 * 100 /
$acl_c_out_sender_rate_60}

Fails when the variable $acl_c_out_sender_rate_60 = 0

as it should - but ....

It fails to show and kind of error in the logs. Should log a divide by zero
error.

--

--
(Continue reading)

Permalink | Reply | 4 comments |
headers
Phil Pennock | 12 Apr 2011 10:15
Favicon
Gravatar

[Bug 1102] Exim should not abort on divide-by-zero

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

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

Phil Pennock <pdp <at> exim.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pdp <at> exim.org
         AssignedTo|nigel <at> exim.org              |pdp <at> exim.org
            Summary|Divide by zero in eval/acl  |Exim should not abort on
                   |not reported in logs        |divide-by-zero
   Target Milestone|Exim 4.75                   |Exim 4.76

--- Comment #1 from Phil Pennock <pdp <at> exim.org>  2011-04-12 09:15:55 ---
Exim 4.75:

% exim -be
> ${eval:10/0}
zsh: floating point exception  exim -be

Well crap.

--

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
Permalink | Reply | 0 comments |
headers
Phil Pennock | 12 Apr 2011 10:26
Favicon
Gravatar

[Bug 1102] Exim should not abort on divide-by-zero

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

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

Phil Pennock <pdp <at> exim.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Phil Pennock <pdp <at> exim.org>  2011-04-12 09:26:57 ---
This should now result in error messages in the log from the expansion failure.

http://git.exim.org/exim.git/commit/54e7ce4ad20a6977ee895a358259122bf3630090

% ./build-FreeBSD-amd64/exim -be
> ${eval:42/0}
Failed: error in expression evaluation: divide by zero (after processing
"42/0")

It will be up to the postmaster of a given install to construct their
arithmetic expressions to avoid trying to divide by zero, but Exim will no
longer die on FPE for this case.

--

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

Permalink | Reply | 0 comments |
headers
Git Commit | 12 Apr 2011 11:17
Favicon

[Bug 1102] Exim should not abort on divide-by-zero

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

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

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

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

--- Comment #3 from Git Commit <git <at> exim.org>  2011-04-12 10:17:05 ---
Git commit:
http://git.exim.org/exim.git/commitdiff/54e7ce4ad20a6977ee895a358259122bf3630090

commit 54e7ce4ad20a6977ee895a358259122bf3630090
Author:     Phil Pennock <pdp <at> exim.org>
AuthorDate: Tue Apr 12 04:24:12 2011 -0400
Commit:     Phil Pennock <pdp <at> exim.org>
CommitDate: Tue Apr 12 04:24:12 2011 -0400

    Catch divide-by-zero in ${eval:...}.

    Fixes 1102
---
 doc/doc-txt/ChangeLog |    3 +++
 src/src/expand.c      |   11 ++++++++++-
 2 files changed, 13 insertions(+), 1 deletions(-)

diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
(Continue reading)

Permalink | Reply | 0 comments |
headers
Phil Pennock | 12 Apr 2011 22:31
Favicon
Gravatar

[Bug 1102] Exim should not abort on divide-by-zero

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

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

--- Comment #4 from Phil Pennock <pdp <at> exim.org>  2011-04-12 21:31:06 ---
Steven A. Reisman pointed out that % 0 is also problematic.

Fixed.

Didn't tag the commit with the bug number, so:
  http://git.exim.org/exim.git/commit/a5b5269546e02d1f2e90000e79df8409d4f269db

--

-- 
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
Permalink | Reply | 0 comments |
headers
Heiko Schlittermann | 13 Apr 2011 12:38
Picon

patch suggested: add a /no_check option to quota and quota_filecount

Hello,

I patched my copy of exim to have a /no_check option to the quota and
quota_filecount config items:

    
    …
        driver = appendfile
        quota = 10G/no_check
                   ~~~~~~~~~ optionally 

Why? What is it good for?

In a staged mailserver setup the outermost box is responsible for
accepting/deferring/rejecting the incoming messages based on the quota
usage for the destination account. It does so by asking a database about
the current limits and current usage of the account in question.

The inner mailserver *has* to deliver the message, it has no authority
to defer/reject just because the destination account is overquota.
*BUT* this inner mailserver has to maintain the "maildirsize" file, since
other maildir clients (POP3/IMAP) use it for their quota decisions and
maintain this file too.

If Exim maintains this file depends on the config item
"maildir_use_sizefile". But if Exim does not know about the current
limits, the first line (the "limits" line) becomes "0S,0C". If we want
to see there the real limits, we have to set the quota, resp.
quota_filecount config options. As soon as these values are not zero,
Exim would start checking for the overquota condition and rejects mail.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Oliver Brandmueller | 14 Apr 2011 11:54

[Bug 1103] New: 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
           Summary: exiqgrep fails on messages smaller 1K
           Product: Exim
           Version: 4.75
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: bug
          Priority: low
         Component: Exigrep
        AssignedTo: nigel <at> exim.org
        ReportedBy: ob <at> e-gitt.net
                CC: exim-dev <at> exim.org

exiqgrep gets a parse error ("Line mismatch") on mails smaller than 1K: exim
lists those messages with only the number of bytes and no unit, the regex
reading the line expects a unit in every case:

The original line is in function collect:

if ($line =~
/^\s*(\w+)\s+((?:\d+(?:\.\d+)?[A-Z])?)\s*(\w{6}-\w{6}-\w{2})\s+(<.*?>)/) {

I propose the following change:

if ($line =~
/^\s*(\w+)\s+((?:\d+(?:\.\d+)?[A-Z]{0,1})?)\s*(\w{6}-\w{6}-\w{2})\s+(<.*?>)/) {
(Continue reading)

Permalink | Reply | 2 comments |

Gmane