DKIM-related failures should not end up in the panic log

Bug #721320 reported by ward
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
exim
Confirmed
Unknown
exim4 (Debian)
Fix Released
Unknown
exim4 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: exim4

Applies to: Lucid Lynx (10.04)

See Debian bug #567876 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567876).

Can we please have a backport of this fix for Lucid - it makes running an Exim mailserver painful on that release.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi there

Thank you for reporting bugs and trying to make Ubuntu better.

Could you please provide the following information:

1. Better explanation of the issue and how it is affecting the package in Ubuntu.
2. Provide a step-by-step to be able to reproduce this bug.

I'm marking this bug as incomplete until the information requested is provide.

Thank you again!

Changed in exim4 (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
ward (ward-pong) wrote :

1. Better explanation of the issue and how it is affecting the package in Ubuntu.

The debian bug report explains it quite nicely, but let me summarize...

Without this patch, the Exim4 package on Lucid will generate warnings like this

2010-01-31 21:41:16 1Nbga6-0005ZL-FH DKIM: Error while running this message through validation, disabling signature verification.

in /var/log/exim4/paniclog.

These are not 'real' errors, they are just warnings. They can not be disabled. They do not belong in the paniclog, which should always be empty.

2. Provide a step-by-step to be able to reproduce this bug.

Run a semi-busy mailserver on Lucid, and you will collect these warnings in your paniclog - on one of our machines, I'm seeing a couple a day on an average mail volume of 100,000 accepted messages.

The patch is trivial, it's been applied to the Debian package, and it would be really nice to not have to manually patch Exim4 on Lucid for this.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi again,

Thank you for providing the information. I'll take a look at it as soon.

Thanks again!

Changed in exim4 (Ubuntu):
assignee: nobody → Andres Rodriguez (andreserl)
status: Incomplete → Confirmed
Revision history for this message
vandebo (vandebo-launchpad) wrote :

If you don't have any custom logic for panic log (i.e. /usr/local/lib/exim4/nonzero_paniclog_hook), you can work around this issue by editing /etc/cron.daily/exim4-base and changing line 18 from:

    E4BCD_PANICLOG_NOISE=""

to

    E4BCD_PANICLOG_NOISE="DKIM: Error while running this message through validation, disabling signature verification.$"

--
Steve

Revision history for this message
Andreas Metzler (k-launchpad-downhill-at-eu-org) wrote :

This was fixed upstream in 4.73. (Debian: 4.72-2).

Changed in exim4 (Ubuntu):
assignee: Andres Rodriguez (andreserl) → nobody
Revision history for this message
Niko Ehrenfeuchter (he1ix) wrote :

Ok, so what's the plan regarding the "long term" in LTS? There is a fix released upstream, but nothing happened with the exim4 package in lucid.

To quote the inital reporter of this bug: "Can we please have a backport of this fix for Lucid - it makes running an Exim mailserver painful on that release."

Changed in exim:
status: Unknown → Confirmed
Changed in exim4 (Debian):
status: Unknown → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

Closing per comment #5.

Changed in exim4 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.