[exim-dev] [Bug 2016] DKIM bodyhash mismatch on Gmail > 64kB

2017-01-15 Thread admin 
https://bugs.exim.org/show_bug.cgi?id=2016

--- Comment #2 from Ivo Truxa  ---
I found the problem 

When debugging with "exim -d-all+acl -bh ", I did not find a way to get rid
of the SMTP data terminating dot, which Exim always includes into the body hash
in -bh mode. In result, DKIM body hash never matches in -bh mode - both at
saved messages that arrived with good and failed DKIM. However, when
crosschecked with shell sha256 and with Perl Mail:DKIM:Verify, after appedning
the dot to the data too, I could confirm that the hashes are identical to those
of Exim. That means that both the hashing algorithm and the canonalization are
working properly in Exim.

Therefore, I decided to debug in daemon mode, and there it is where I could see
the problem. It is caused by BDAT (https://tools.ietf.org/html/rfc1830). 

Gmail uses CHUNKING, and the BDAT command sent after each chunk of data (around
63kB in Goggle's case), the command gets inserted into the canonalized string.
The data stream remains clean, so the attachments remain intact. It only
influences the canonalizing buffer string.

I think you do not need my configuration or logs. You can easily reproduce the
problem by sending yourself an email from Gmail, containing a binary file over
65kB. When you run Exim in daemon mode with debugging output redirected to a
file, you'll see the string "BDAT 34182 LAST" after some 63kB of data (the
number may differ). You'll spot it easily, since it mostly breaks down the
otherwise uniform data column of the base64 data. An example from my debug file
is below:

voFq5zaCir2h86qtRTxOujxMvOuRqDGUaQpgDYEwF5nU1fFOXrrMYpdl21qXgH05XPqZ8S5lK1fM^M
hhkmDssWITGWTtqIY0bEHhVmGSJZK3pOeRpbsB1KtTStnu+deo1jx9As9FG6JnZ3x7K+AuxfO9jV^M
LCads43D9v5gkfjC9Nwa1mvmns8h9IL/AC2pp8vb69M8IICAgICAgICAgICAgICAgICAgICAgICA^M
gIMKPittVME7BBKgSFIkjdRgSAmBITsJkyFAgydkkhLCBtBDAT 34182 LAST^M
81B1SCSdkyJBMbiEFplBY7gBBIO6Jh^M
fnZRhG6QSVVaFxHVJAAAkjZR2FoBInooEVaradNzydgJKRGR0/nXFRd31QNfIadET9VNU7slMNWD^M
BI4IB6qq8LPaNMAb8jsolaHzDvMLhpOkbxChMI8kVfdIEkyES6z8c8J8/LltdeX7lCq6k7fjUNvx^M
aufxCjmt5dbhNzluTT5eWbqk61vnsMgA7Ly96l661VlkbYhzgXbwJhcy5S6FqqXN009Y9O60bmYb^M

And this is the true data (not canonalized):

voFq5zaCir2h86qtRTxOujxMvOuRqDGUaQpgDYEwF5nU1fFOXrrMYpdl21qXgH05XPqZ8S5lK1fM^M
hhkmDssWITGWTtqIY0bEHhVmGSJZK3pOeRpbsB1KtTStnu+deo1jx9As9FG6JnZ3x7K+AuxfO9jV^M
LCads43D9v5gkfjC9Nwa1mvmns8h9IL/AC2pp8vb69M8IICAgICAgICAgICAgICAgICAgICAgICA^M
gIMKPittVME7BBKgSFIkjdRgSAmBITsJkyFAgydkkhLCBt81B1SCSdkyJBMbiEFplBY7gBBIO6Jh^M
fnZRhG6QSVVaFxHVJAAAkjZR2FoBInooEVaradNzydgJKRGR0/nXFRd31QNfIadET9VNU7slMNWD^M
BI4IB6qq8LPaNMAb8jsolaHzDvMLhpOkbxChMI8kVfdIEkyES6z8c8J8/LltdeX7lCq6k7fjUNvx^M
aufxCjmt5dbhNzluTT5eWbqk61vnsMgA7Ly96l661VlkbYhzgXbwJhcy5S6FqqXN009Y9O60bmYb^M

I verified with sha256() that Exim indeed calculates the body hash including
the BDAT command, which it definitely should not.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 2016] DKIM bodyhash mismatch on Gmail > 64kB

2017-01-15 Thread admin 
https://bugs.exim.org/show_bug.cgi?id=2016

--- Comment #1 from Jeremy Harris  ---
Could you give "exim -d-all+acl -bV" output from the system, and a sample
acceptance (<=) log line for an affected message?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 2015] Unable to start Exim Daemon using Exim in Cygwin

2017-01-15 Thread admin 
https://bugs.exim.org/show_bug.cgi?id=2015

Graeme Fowler  changed:

   What|Removed |Added

 CC||gra...@graemef.net

--- Comment #1 from Graeme Fowler  ---
See this thread:

https://www.mail-archive.com/cygwin@cygwin.com/msg149746.html

You may need to update Cygwin and see if that matches. You didn’t say which
version you were running, and it appears to have been addressed last week.

Graeme

-- 
You are receiving this mail because:
You are on the CC list for the bug.-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 2016] New: DKIM bodyhash mismatch on Gmail > 64kB

2017-01-15 Thread admin 
https://bugs.exim.org/show_bug.cgi?id=2016

Bug ID: 2016
   Summary: DKIM bodyhash mismatch on Gmail > 64kB
   Product: Exim
   Version: 4.88
  Hardware: x86
OS: FreeBSD
Status: NEW
  Severity: bug
  Priority: medium
 Component: DKIM
  Assignee: t...@duncanthrax.net
  Reporter: tr...@truxoft.com
CC: exim-dev@exim.org

All Gmail messages with body length exceeding the size of 65536 bytes (the size
of an unsingned short int, or a 16 bit int) trigger DKIM signature failure with
'bodyhash mismatch'. DMARC does not align on DKIM either at the message, but on
the other hand, the received message passes an offline test with Perl
Mail::DKIM::Verify perfectly (dkimverify.pl).

The problem is perfectly reproducible (at least on my server) with any 64kB+
message from Gmail, but I did not see the same DKIM errors on 64kB+ messages
from another domain, yet.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 2013] Bounce message missing Diagnositic-Code for unrouteable addresses

2017-01-15 Thread admin 
https://bugs.exim.org/show_bug.cgi?id=2013

Jeremy Harris  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Jeremy Harris  ---
I agree that a disgnostic-type of "smtp" would not be appropriate, since the
processing in Exim has not gotten as far as an SMTP connection. I just checked
the registry (at https://www.ietf.org/assignments/dsn-types/dsn-types.txt) and
there is no other type defined.  We could define an experimental type (X-foo
style), though I think I've see that practice deprecated in some other context,
recently.  I don't know what O365 would do with such.

You could try building with EXPERIMENTAL_DSN_INFO to see if O365 make any of
the
additional information then added to the DSN visible.

In the meantime, rejected.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 2015] New: Unable to start Exim Daemon using Exim in Cygwin

2017-01-15 Thread admin 
https://bugs.exim.org/show_bug.cgi?id=2015

Bug ID: 2015
   Summary: Unable to start Exim Daemon using Exim in Cygwin
   Product: Exim
   Version: 4.86
  Hardware: x86-64
OS: Windows
Status: NEW
  Severity: bug
  Priority: medium
 Component: Unfiled
  Assignee: ni...@exim.org
  Reporter: wallace.for...@gmail.com
CC: exim-dev@exim.org

I've been unable to start the Exim daemon after installing Exim with Cygwin in
Windows 10. I've posted a question here on Superuser:

http://superuser.com/questions/1167319/cannot-start-exim-daemon-on-cygwin

I'll repost the text below:

At the end of the exim-config setup, the daemon fails with this message:

Do you want to start the exim daemon as a service now? (yes/no) yes
cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
The service has not been started.

ERROR: Could not start the daemon.

INFO: The exim log files are in /var/log/exim.

WARNING: The default permissions are only suitable for a casual environment.
See /usr/share/doc/Cygwin/exim-X-Y.README for how to adjust them.

When everything else fails,
read /usr/share/doc/Cygwin/exim-X-Y.README,
or look up the documentation on www.exim.org.
Many happy mailings :)
The following log files exist at /var/log/exim:

$ dir -l /var/log/exim
total 4
-rw-rw-r-- 1 cyg_server Administrators0 Jan 13 16:48 cygrunsrv_err.log
-rw-rw-r-- 1 cyg_server Administrators0 Jan 13 16:48 cygrunsrv_out.log
-rw-rw-rw- 1 User1  User1  1499 Jan 14 09:49 exim_main.log
The first two are empty, and the third has no relevant information.

Further attempts to start the service after running the config fail with this
message:

$ net start exim
The exim service is starting.
The exim service could not be started.

The service did not report an error.

More help is available by typing NET HELPMSG 3534.

$ NET HELPMSG 3534

The service did not report an error.
The windows event viewer has this message in its application logs:

The description for Event ID 0 from source exim cannot be found. Either the
component that raises this event is not installed on your local computer or the
installation is corrupted. You can install or repair the component on the local
computer.

If the event originated on another computer, the display information had to be
saved with the event.

The following information was included with the event: 

exim: PID 2708: service `exim' failed: signal 6 raised

Any thoughts on what this error might be or what further diagnostics to run?
Thank you!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 2012] Crash at DKIM pdkim_finish_bodyhash

2017-01-15 Thread admin 
https://bugs.exim.org/show_bug.cgi?id=2012

--- Comment #1 from Jeremy Harris  ---
We'll need some more evidence... How about a sample mail that causes a
crash when received?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 2004] CHUNKING without PIPELINING can get synch-fail

2017-01-15 Thread admin 
https://bugs.exim.org/show_bug.cgi?id=2004

Jeremy Harris  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Jeremy Harris  ---
Nobody commented

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##