gmane.mail.exim.user

Exim 4.80 RC5 uploaded

Phil Pennock — 2012-05-24T05:32:45

I have uploaded Exim 4.80 RC5 to:
        ftp://ftp.exim.org/pub/exim/exim4/test/

There is an attempt to resolve the compiler issues on some versions of
Linux, a fix for OpenBSD's resolver library not having an expected
typedef, and fixes to work on older OpenSSL libraries which lack SNI
support.  Everything else changed is documentation and test suite, so
I'm going to permit myself a little optimism that this will be the last
RC and that the final release can be cut late in the weekend, to await
people on Monday morning.

As an experiment, this time there are three versions of each file;
bzip2, gzip and lzip.  If you like lzip and want it to stay, please let
us know.  The main distribution is only 8% smaller than bzip2 (28%
smaller than gzip), but perhaps this will really add up.  I'm inclined
to put out the 4.80 release with lzip and see what the reaction is.

I'm also thinking that 4.80 might be the last release with SHA1
checksums in the release mails and that afterwards we'll stick to just
SHA256.  If there's a reason this would cause you problems, please do
let me know; the decision isn't by any means fixed yet.

The ChangeLog/NewStuff/README.UPDATING can be reviewed at:

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

The files are signed with the PGP key 0x3903637F, which has a uid
"Phil Pennock <pdp< 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 in reply to this email, on exim-users.

Thank you for your testing and feedback,
-Phil Pennock, pp The Exim Maintainers.

SHA256(exim-4.80_RC5.tar.bz2)= d0cb88172a3aff24873c82116f9d649e736ae211c4341b3ed4b13fde1eeb98f5
SHA256(exim-4.80_RC5.tar.gz)= ba059ed0416451dadfa887a4f5e083744fa86300a2d6b44be7900ba461747e50
SHA256(exim-4.80_RC5.tar.lz)= 0f7d0310e378ccbafce4e44572b6baf81f7117f78c565b72eb3f0f6a9e9c7d1e
SHA256(exim-html-4.80_RC5.tar.bz2)= ad8705dc69c50fec684a3196ecf1447466f40432216fe92970a47a62757d1030
SHA256(exim-html-4.80_RC5.tar.gz)= fc8a758a93c60bfbdeca3b79509e9345d9f1370d596b19c73ffc659b1d29cd48
SHA256(exim-html-4.80_RC5.tar.lz)= e301b5b914ffc14a6da22a5225016e769b0fecdf6f6c0b7a727222c6bc7b9c25
SHA256(exim-pdf-4.80_RC5.tar.bz2)= ad42d1ecd7a70d31dada5421397bb06fe4d5815c24b78ba5a746f8ba6b6bcb92
SHA256(exim-pdf-4.80_RC5.tar.gz)= fc1823df99e85a5c100adf72fa4aa43cc850fa44596ee2add03e192ffb206e4d
SHA256(exim-pdf-4.80_RC5.tar.lz)= 67fdccd90b8d34520803ccecd6868944b611937a64a1bbd4dbfbf2302faf2672
SHA256(exim-postscript-4.80_RC5.tar.bz2)= a562a1090a4ef8b996f823c6322b36a2308ac1842aa64c4320966b668f2aa172
SHA256(exim-postscript-4.80_RC5.tar.gz)= 1ba82befe5694d87bae43e71c7e253fcb18ba4ae903963674abeb8e8cf7d0b9e
SHA256(exim-postscript-4.80_RC5.tar.lz)= 7f362aacccf4226efe84f0b1c6d0d421eb164f9398b8257aca79b53eb7e6b7ed

SHA1(exim-4.80_RC5.tar.bz2)= 9e080663ac5586e6a6422f8717acceab6343fa8a
SHA1(exim-4.80_RC5.tar.gz)= 30f9741f0b9317cdac3e201539cbd0e88ac9839b
SHA1(exim-4.80_RC5.tar.lz)= 6878d8825027d39e257d6c3c42a29ca03e21590e
SHA1(exim-html-4.80_RC5.tar.bz2)= 64c2f1ad74f48a2ec4bb59b0fc5c126ba52f605d
SHA1(exim-html-4.80_RC5.tar.gz)= 78ec85986c941420e9aa4bfef1008c1fa8797b22
SHA1(exim-html-4.80_RC5.tar.lz)= 8f8eaadaa9a638eb660a4daa9f8269c99bf829f2
SHA1(exim-pdf-4.80_RC5.tar.bz2)= f077da301168f3114adb524d7a0c0c6782f5f2d4
SHA1(exim-pdf-4.80_RC5.tar.gz)= 3f981957a4e26b174fd6fbadc56f789d3badbdab
SHA1(exim-pdf-4.80_RC5.tar.lz)= 6d4d430e2f52dad30a861d22ace2b21d37ba2149
SHA1(exim-postscript-4.80_RC5.tar.bz2)= 543bb6cf8880e92bbf02696f0ab0fc1b3d64a3d1
SHA1(exim-postscript-4.80_RC5.tar.gz)= 6c9c1dbd547b22a4975f42b7e46e2d98b8404e2f
SHA1(exim-postscript-4.80_RC5.tar.lz)= 3d0f14a99275a513a270d5517dd39abc7f6e6735

Am I right that no_more has no effect within the includedsimple routers?

Regid Ichira — 2012-05-23T10:03:47

  Consider the following two routers:

1) nonlocal:
      driver = redirect
      domains = ! +local_domains
      allow_fail
      data = :fail: Mailing to remote domains not supported
      no_more

2) dnslookup_relay_to_domains:
      driver = dnslookup
      domains = ! +local_domains : +relay_to_domains
      transport = remote_smtp
      same_domain_copy_routing = yes
      no_more

  Am I right that, in both cases, if the router run, it can not decline?
Therefore, the no_more has no effect.  It can be omitted without any
consequences.
  I think spec.txt mentions a similar situation in a discussion about the manualroute.
(Note that the following spec.txt discussion is about two other routers, not those
I showed above.) 

    $ grep -A34 '* The manualroute router' spec.txt | tail -10

    There is no difference in behaviour between these two routers as they
    stand. However, they behave differently if no_more is added to them. In the
    first example, the router is skipped if the domain does not match the
    domains precondition; the following router is always tried. If the router
    runs, it always matches the domain and so can never decline. Therefore,
    no_more would have no effect. In the second case, the router is never
    skipped; it always runs. However, if it doesn't match the domain, it
    declines. In this case no_more would prevent subsequent routers from
    running.

    $

hash{20}{62}

Ron White — 2012-05-22T16:42:22

Good afternoon,

I came across this:

warn set acl_m4 = ${hash{20}{62}{$sender_address$recipients
$h_message-id:}}

...and realised I'd never seen it before.

My Googling to find out what the figures symbolise is getting me
nowhere, has anyone got a link to an explanation?

Kind regards
Ron

SPF, DKIM and DomainKeys activation for signout

2012-05-21T20:44:50

 Hello everyone.
 I've just got into this following issue with versions 4.69 and 4.77.
 How can I activate SPF, DKIM and DomainKeys (if possible the three at
the same time) in exim and to signout each sent mail and check each
incoming mail.
 Thanks.

Exim 4.80 RC4 uploaded

Phil Pennock — 2012-05-21T05:00:32

I have uploaded Exim 4.80 RC4 to:
        ftp://ftp.exim.org/pub/exim/exim4/test/

There was no RC3; there are some changes since RC2 worthy of note.

There is a new option "tls_dh_max_bits" which affects TLS; with OpenSSL,
it may cause a "tls_dhparams" file to be ignored.  With GnuTLS, the
number of bits GnuTLS recommends be used for Diffie-Hellman generation
will be clamped to at most this value.  The default "tls_dh_max_bits" is
the current maximum allowed by the NSS security library used by Mozilla
products such as Thunderbird.  This resolves a GnuTLS vs NSS
interoperability problem.

Exim will now check the configured value of "tls_require_ciphers" at
startup; what was an error that would cause Exim to fail STARTTLS will
instead cause Exim to fail to start.  This exposes latent
misconfiguration and makes it clearer that something is going wrong.
This also avoids the risk of crashes while talking to a remote server,
if there are library linkage problems, reducing the chances of anything
being exploitable.

The ChangeLog/NewStuff/README.UPDATING can be reviewed at:

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

The files are signed with the PGP key 0x3903637F, which has a uid
"Phil Pennock <pdp< 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 in reply to this email, on exim-users.

Thank you for your testing and feedback,
-Phil Pennock, pp The Exim Maintainers.

SHA256(exim-4.80_RC4.tar.bz2)= 35a9f026bbc609a05bad99f19f11372e9cd84534aad3b4420751a026ee4a320a
SHA256(exim-4.80_RC4.tar.gz)= fbc4154a7cb6763022eb79b91d4ce1d891b2c9583bd4b40407ea536c77ea68c2
SHA256(exim-html-4.80_RC4.tar.bz2)= a5eefe4a2ae04354eecfbc4848c65918b7667e4abc84ca10ed8c46ddc5a25977
SHA256(exim-html-4.80_RC4.tar.gz)= db2c641caa389e940324ca7d07d0bdc1c62a13950878deeb589e9f16aef1869e
SHA256(exim-pdf-4.80_RC4.tar.bz2)= 4af728a14aa070d4e06fb141670f789d6b34fe9f2864a854d12ce17fa31446fa
SHA256(exim-pdf-4.80_RC4.tar.gz)= b70fa8e2842102b7e280a9ea2d0083ba2ea2ca8d6f71e771ccb77f089c9246ba
SHA256(exim-postscript-4.80_RC4.tar.bz2)= 63fbeb59a6d208ffd8f8c82bbbc8e5cf31f92331d15c05762035f536fc4fcd3c
SHA256(exim-postscript-4.80_RC4.tar.gz)= b4cf268f15f70bf3945df400c3e6fd0d5d7c401329cfb169a028bbaf2f6ce171

SHA1(exim-4.80_RC4.tar.bz2)= 50424c8272312e1bd081b3adaf7e2cc5a0a5c725
SHA1(exim-4.80_RC4.tar.gz)= 214735555fda62562ecfad11c50da75dec11ebb6
SHA1(exim-html-4.80_RC4.tar.bz2)= 1ca13c68850c0043cb1031d7a8f64481b1643bfb
SHA1(exim-html-4.80_RC4.tar.gz)= 5754ec52d6338dee941f29ca09c77820c5f9b8f0
SHA1(exim-pdf-4.80_RC4.tar.bz2)= ba77cb571603fae068b47c619f82bcb912e134e8
SHA1(exim-pdf-4.80_RC4.tar.gz)= fd3f0c618549a4ff04d3e2614da5ad7afe12246a
SHA1(exim-postscript-4.80_RC4.tar.bz2)= 7406c012416d1767b85821c0fa9c6d0f1cb42745
SHA1(exim-postscript-4.80_RC4.tar.gz)= cdccb3a6bdd3502d7b620e6d70f24748281ba3cf

Weird Characters

eximmail — 2012-05-20T01:34:23

I have started seeing these weird characters in a couple of emails. On 
this list anything W B Hacker sends I can't read his mail at all! I have 
to go to the board to read them. This just started in the last week or 
so and I am at a loss as to why it is happening at all. This also 
happened on an online purchase and every email they sent me was the same 
weird characters.


can anyone explain why this is happening?





��z{i���{ 
�1��1��=��z\+�׈���i���v'^j�,��^r�aj�Z��Z�Z'�ȧq��z{Z��ڲ�b��Z��B�{^�֧j 
\���^�����v�����v�ꮊ����+�W�jg�z�+��b�}t�D�D�V��,�� 
�&i�kz�"�)��z�0�+^�+-��< at >`D���`�z�)jjk����X��+8��:��(��9�MV*�'�)Z�t��׏w��z�ޭ�lr(��ܢe� 
2��ԭj۬P)!��5�Ɍ�()5�Ɍ�A�ɭ����ɽє�(�$���ٔ�����܁ݕ�ɐ������()$������Ёѡ�Ё��Ё��́�����ͥ���������х�����̀��ѥ�ձ�ѕ������((촤 
((��ݽձ���������͵��Ё9L�͕�ٕȁ���ͽ���ͽ��(�Ѽ��ձ���Ё����� �ͥ����䁱 
���������ȁ���ɽ�Ʌ���������������ѡ�Ё�����(� 
9L�������́��͕���(�(�!�ɔ�́����ͥ�����ᅵ����Q��ɔ��ɔ�͕�ٕ�́��Ёѡ�ɔ�ѡ�Ёɕ��ɸ(�չ�� 
䁍���́���%< at >����ɕ�̸͕� �Ёݡ�Ё����Ё����չ��䁍 
������ȁ������(���e�ԁݽձ����ٔ�Ѽ�������%< at >����������ѡ�����Ё����ѡ����͔�ѡ��%< at >(�Ѽ���Ё����չ�� 
䁍����(�(�M�����́ѡ�ɔ�ͽ�ɍ���������ȁͽ��ѡ���������ѡ�́�ȁ��9L�͕�ٕȁݥѠ��(�͍ɥ�ѥ�������Յ���(�()����́���ݡ�Ё�ɍ��х�������Ʌ������ԁ�����݅�ЁѼ�ɕ͕�ɍ���������܀)��ѕ���Ё�́������Ѽ��������() 
�ͥ����䰁�ԁ�ɽ����䁑���Ё��������ɕ���� 
9L��ɥ�ѕȰ���ȁ�ɕ�Օ�Ѐ)������������̰��Ё�����ٽ�����������丁 
ٽ��������ٕɡ����Ѽ�����Ѐ)���ѡ�ȁ݅�()��Q��ѡ����ѕ�Ё���5Q���ȁ��䁽 
ѡ�ȁ����ɕ���́���ѡ��=L���Ȁ)ɕͽ��ѥ��̰���������ȁ 
����������ٕ��ѽ����ѡ��������������ɥ�ɥ�䁥 
��)ѡ��ɕͽ�ٕȁ����������ь�ɕͽ�ع�����������ѹ��́�ȁ��եم���Ф�()Q��Ё������������������а��� 
䁭 
��ݸ��������ѽ�̜����������ٕ��ݽѕٕȀ)ɕ��ɸ��ԁ����͔�Ѽ������ѡ�ɔ�()Q�����ɽ�ͥ����́����ᅵ���5������̀́�ȀЁѡ��ͅ������ɥ�́ѡ�Ѐ)��ٕ�Ё 
�������Qݥ�͡�а����������̰�ݕѽ���������ѡ�ȁͽ�����)��͕�͕̰��Ʌ����́������ٕ�ѥͥ���ͥѕ́$���ٔ�����������Ѽ�%��Ȁ)��ݹ����� 
́���Ѽ���������и()%=\��e�ԁ�����Ё��ЁQ!I��ɽ��!I��() 
��ѕȰ�������Ȱ����́����她���ɽ�ͥ������Օ̸�5U
����ѕȸ�M���ȁ�̀)ݕ������������̸͕() ����Ѽ����5Q�()�1 
0�������́ѡ��ͅ������MU 5%QQ��Ʌ������M����ȁ$���ٕ��Ё�������)�Ս�����ѡ��݅䁽 
���ɕٕ�ѥ��������щ�չ��͕���() �Ё�Ё͡�ձ���Ё�������ѡ�Ё�����ɕ�ЁѼ�͕�Օ�ѕȁ5Q 
�́�ԁ����Ё݅�Ѐ)Ѽ������ݥѠ����幅 �������ɥٕ��1 0��������Ё��� 
9L���х�������ͼ�)������́�ԁ��ٔ������ѕɹ����������ʹ������Յ���ȁ��ѽ��ѕ����Ѽ�������и() 
́Ѽ���չ��䁍�������� 
=%< at >�()5�ɔ�չ�ɕ���х��������́���ѡ�͔�ѡ�������������ȁ������������ѡ����ɬ�)� 
䁄���չ�����ѽ���Ս�������ѽ�����ѱ�������Ѽ���ѡ�ȁݥѠ��и()1 
0������ѥɔ��ѱ���M�ɔ����ذ�����������ѡ�������() 
�Ё����Ʌ���9=P������ѥɔ���չ��䁍����� 
����ȁѡ����ɕ���́���ݽɬ�)��Ʌѽȝ́��ͥ����������̰���Ёѡ��ȁ����ѥ���()$���ՉЁ$���ٔ��ٕȀ������ѡ��ݽ��е��͔���ɵ�ȁ��Ё 
�����ȁ Ʌ饱����)���ݽɭ́���������������Ё�ٕ��������
������-�ɕ���Q��݅��)9�Ё�ɵ����ѱ䁅��݅丁 �Ё$���ٔ�ѡ��ȁݽ��Ѐ��������̜�1 0��() 
���(���+�~O��ۚ�d((���(���1��Ё��х��́�Ё�����輽 
����̹�ᥴ��ɜ������������ѥ�����ᥴ��͕��(���ᥴ���х��́�Ё����輽 
��ܹ�ᥴ��ɜ�(���A���͔��͔�ѡ��]����ݥѠ�ѡ�́���Ѐ������輽ݥ����ᥴ��ɜ�


Thanks

Log Spamassassin Rejects

Brian Spraker — 2012-05-19T21:33:49

Hi all -

Another question for the group.

I've increasingly been rejecting good messages and am trying to find out why.  However, when looking at the rejectlog, it mentions why it was rejected (spam points) - but it doesn't show me how the e-mail qualified with that many points.

Is there a way in Exim to set it so that it will log all of the rules that matched the e-mail into the rejectlog - indicating how the message got to that point level?

Trying to look up information from the spamassassin website - and they mention a logging module to add to the local.cf file - but it doesn't seem to do anything different.

Thank you!

Brian S.

Tricky DNS servers [OT]

Marc Perkel — 2012-05-18T21:59:09

I have a few weird ideas and would need a smart DNS server of some sort 
to pull it off. Basically looking for a programmable backend that might 
do DNS lookups itself.

Here's a possible example. There are servers out there that return 
country codes of IP addresses. But what about a country code for a host 
name? You would have to do an IP lookup on the host and then use the IP 
to get a country code.

So - is there source code for something like this or a DNS server with a 
scripting language?

Exim 4.80 RC1 uploaded

Phil Pennock — 2012-05-18T03:55:34

I have uploaded Exim 4.80 RC1 to:
ftp://ftp.exim.org/pub/exim/exim4/test/

This release contains a number of backwards-incompatible changes, for
both OpenSSL and GnuTLS, in the name of security (about the only reason
we normally accept for being backwards incompatible).  Please read over
README.UPDATING carefully!  We have jumped from 4.77 to 4.80 for this
reason.

This is the first release of Exim to support OpenSSL 1.0.1+.  This
release of Exim abandons maintaining hard-coded lists of ciphers for
GnuTLS in favour of honouring GnuTLS library policy, so MD5-based
certificates will no longer work and are not supported.  The GnuTLS
support has been re-written and there is the possibility of bugs.

When building, please do not just recycle your previous Local/Makefile;
there are a number of new possibilities in this release which may make
your life easier, as support for using pkg-config to query CFLAGS/LIBS
for various pieces of software has been added.

Please join me in welcoming Jeremy Harris and Todd Lyons to the Exim
Maintainers team.

The ChangeLog/NewStuff/README.UPDATING can be reviewed at:

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

The files are signed with the PGP key 0x3903637F, which has a uid
"Phil Pennock <pdp< 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 in reply to this email, on exim-users.

Thank you for your testing and feedback,
-Phil Pennock, pp The Exim Maintainers.


SHA256(exim-4.80_RC1.tar.bz2)= c2b67b6baea743fc73dcf9d2e298d1eef9a79f2172958fba8fd9b3025c328bba
SHA256(exim-4.80_RC1.tar.gz)= c5a4d1402cf7eff4b4b9ced3fcee8d195f0ff1f335d13c68d58206f4f72215b9
SHA256(exim-html-4.80_RC1.tar.bz2)= fb1189bd1a053e06390d6cee3ad5bd6b508a806c0d143c4a9fc70822605d63ec
SHA256(exim-html-4.80_RC1.tar.gz)= 45fe3b2f3d6f431b010b9c665cd5bdfdd8388f08819d814ecf70b179eccccdc2
SHA256(exim-pdf-4.80_RC1.tar.bz2)= 343599159461b47156d613041cb62afb549f6286f320f9cf62eb856dd95811bc
SHA256(exim-pdf-4.80_RC1.tar.gz)= 1eb6afdfa5fd35d4130e6d305baa285d03007e456e4e4e5baf884c7608ddc287
SHA256(exim-postscript-4.80_RC1.tar.bz2)= 7867c6aba62fbeae46342bc40f384f5abaee8fb2553ceb0a7c25a1ff68b7226b
SHA256(exim-postscript-4.80_RC1.tar.gz)= c7a6a92e4f74e9afad7f702ed703d6b19a285e814d77090a2d02d21fb2b0ca4c

SHA1(exim-4.80_RC1.tar.bz2)= eb92b4b220ec5c0161d6c90503f3d0b0aea9f1f3
SHA1(exim-4.80_RC1.tar.gz)= 53f9add7baf2bf5361695cf2ff6f75e2a24f61c9
SHA1(exim-html-4.80_RC1.tar.bz2)= 0bb5a391fb22d606edf8f16263bdc45426c8ab89
SHA1(exim-html-4.80_RC1.tar.gz)= a0baf96dd903dd4e1a1c86da465b70e633009991
SHA1(exim-pdf-4.80_RC1.tar.bz2)= 961151a4fefc84b6e76ee1fceac54a0c321fe2c4
SHA1(exim-pdf-4.80_RC1.tar.gz)= 858711456ce822d9cc4464b01f419bcbe8daa2e6
SHA1(exim-postscript-4.80_RC1.tar.bz2)= 924f9cece857057e75a23e1e8d556f25ab99a353
SHA1(exim-postscript-4.80_RC1.tar.gz)= 7283d5c762264e00e6102265a8f1eaf65048c0b6

Quota Limits - Setting Greater Amounts

Brian Spraker — 2012-05-17T23:28:16

Hello all,

Been using Exim for several years.

I have a setup that checks a file for the quote size and I then use a MySQL backend with virtual users.  Here is a snippet of what I currently have:

maildir_format
maildir_tag = ,S=message_size
maildir_use_size_file = true
maildir_quota_directory_regex = ^(?:cur|new|\..*)$
current_directory = /
quota = ${lookup mysql{SELECT quota FROM horde_users WHERE user_uid="${local_part}< at >${domain}"}{${value}999}}
quota_warn_threshold = 90%
quota_is_inclusive = false
quota_warn_message = "\
To: $local_part< at >$domain\n\
Subject: Mailbox Approaching Size Limit (90% Usage)\n\n\
Please note that your mailbox is approaching its limit.  Upon receiving this message, your mailbox was at 90% of capacity.\n"

However, please note that the "quota_warn_threshold" is set to an equal number as noted above.

Sometimes a user receives a very large e-mail that puts them over their quota limit.  Does anyone know of a way to set it so that if the value is at 90% or GREATER, the message is sent out?

In addition, once the individual has reached their quota limit, is there a way that a message saying "your mailbox is now closed" can be sent out?  I know that in an Exchange environment, that is possible.

I just have a few users that complain that they don't get the notice their mailbox is at 90% capacity and don't know that e-mails are bouncing because they have reached their limit.

Thank you!

Error compiling 4.77 Exim on Solaris

2012-05-16T09:45:45

Can anyone help with the following error, I am trying to compile the 4.77
EXIM on version 10 Solaris.:-

`Makefile' is up to date.

Missing CFLAGS_DYNAMIC inhibits building dynamic module lookup

gcc -DCOMPILE_UTILITY spool_in.c
In file included
from /usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/sys/signal.h:44,
                 from /usr/include/signal.h:26,
                 from exim.h:61,
                 from spool_in.c:12:

**********************************************************************
This e-mail is intended solely for the addressee and is strictly confidential. If you are not the intended addressee, please do not read, print, retransmit, store or act in reliance on it or any attachments. Instead please notify us immediately, e-mail it back to the sender and delete the message from your computer.

E-mail transmission cannot be guaranteed to be secure or error free and we accept no liability for changes made to this e-mail (and any attachments) after it was sent or for viruses arising as a result of this e-mail transmission.

Any unauthorised disclosure, reproduction, dissemination, copying, modification, distribution and/or publication of this e-mail message is strictly prohibited. 

We reserve the right to intercept any e-mails or other communication for permitted purposes in accordance with the current legislation which you send to, or receive from, any of the employees or agents of ours via its telecommunication systems. By so corresponding you also give your consent to us monitoring and recording of any correspondence using these systems.

Unless stated otherwise by an authorised individual, nothing contained in this e-mail is intended to create binding legal obligations between us and opinions expressed are those of the individual author.

This e-mail is sent on behalf of The Co-operative Banking Group
and/or one or more of its subsidiaries detailed below, as the context may require.

The Co-operative Banking Group registered number IP29379R  and CFS Management Services Limited registered number 5564787 are registered in England and Wales and have their registered office at New Century House, Manchester, M60 4ES.

The Co-operative Banking Group includes the following members which are authorised and regulated by the Financial Services Authority:
Co-operative Insurance Society Limited registered number 3615R
CIS General Insurance Limited registered number 29999R
CIS Unit Managers Limited registered number 2369965
CIS Policyholder Services Limited registered number 3390839
The Co-operative Asset Management Limited registered number 03858994.
The Co-operative Bank p.l.c. registered number 990937

Each member of The Co-operative Banking Group listed above is registered in England and Wales and has its registered office at  Miller Street, Manchester M60 0AL other than The Co-operative Bank p.l.c. whose registered office is at PO Box 101, 1, Balloon Street, Manchester, M60 4EP.


**********************************************************************

check for no Content-Type header?

Oliver Howe — 2012-05-15T09:24:32

Hi,

I installed a RAID monitor software and it sent some notification
emails through my mail server that had no Content-Type header so they
got stuck on the mail queue.
I've added this check for non Content-Type in a system-filter.mf file
but is there a better way?

Thanks,

Oliver

# Exim filter

if $message_body does not contains "Content-Type:"
then
 logfile /var/log/exim4/no_content_type_log.txt
 logwrite "$tod_log:$message_id:no content-type"
 headers add "Content-Type: text/plain"
endif

Migrating from qmail to exim question

Miguel Lanz — 2012-05-14T18:59:53

Hello everyone,

1st of all thanks for taking the time to read and reply to my inquiry here.

I am very in-experienced when it comes to mail server administration,
however I was assigned a task to migrate an existing qmail server running
on a ubuntu 8.0 server to a new  opensource mail server that will be
install and setup on a fresh redhat enterprise version 6 server.

doing a bit of research I came across exim and it seems a really good MTA
choice for our purpose specially being open source. ( we can't afford to
have any commercial products )

Is there any good documentation out there that can help me, guide me
through migrating 300 mail boxes from qmail server to exim server? our
current qmail server uses the Maildir format and we would like to keep the
new one that way, also runs courier-imap for IMAP on ports 143 & 993, we
don't use POP3, and all users in qmail server authenticate to their e-mail
accounts through an openldap server that is hosted on the qmail server as
well. Our current qmail server does not have any aliases setup nor virtual
domains.

One option I was looking at for IMAP service on the new server is dovecot.

I would like to test this procedure on a VM that I have setup but am
planning on deploying to a production environment in the next 2 weeks.

Any help would be greatly appreciate it.

Limit No. of recipients in email client

Muhammad Irfan — 2012-05-14T10:40:21

Hello,

I have couple of requirements.

1- I need to restrict no. of recipients in email client
(outlook/thunderbird). Let say a user can't send email if he has no. of
recipients greater than 100 regardless in To, CC, BCC.
Also. Sender should get an bouce back with customized message.

2- I need to block sender email address temporarily if no. of emails sent
from his email address on specific threshold per hour. And sender email
address should get an customized bounce back message. e.g. No user can send
emails if 50 mails/hour send already from his account.

NOTE: emails should be count as if 10 emails sent in one email. Overall 10
emails should be counted.

I am using Exim 4.

Thank you.

Executing $run command ???

Always Learning — 2012-05-12T21:18:03

I use Exim 4.63 with Centos 5.8

I wanted to send an email from within Exim's ACLs.

Googling I found the recent posting from Lena
http://www.exim.org/lurker/message/20100323.122536.8fe8af1a.en.html


and found I could get Exim to run a shell. For example this works:-

warn message = ${run{/bin/bash -c "echo $sender_helo_name

However all my attempts to feed the Exim Binary with an email message
failed:-

EXBINARY       = /usr/sbin/exim
MAILME         = user< at >domain.com
SHELL          = /bin/bash

${run{SHELL -c "\N{\N echo Subject: Test Msg; echo; echo Un Deux \
      Drie Vier; \N}\N | EXBINARY MAILME"}}

I found success with PHP:-

warn message = ${run{SHELL -c "/usr/bin/php /dx/php/exim01 'SSSSS' 'test
msg AZC'"}}

<?php
$subj = $argv[1];
$mess = $argv[2];
$headers = 'From: Exim Server <.....< at >......com>'."\n".
           'Content-Type: text/plain; charset=ISO-8859-1'."\n";
$to      = 'Exim Warning <.....< at >......com>';
mail($to,$subj,$mess,$headers,'-f .....< at >......com');
?>

and a nice email was produced and successfully processed by Exim.

HOWEVER, I would like to be able to use the Exim Binary as Lena did. All
ideas gratefully welcome.

Exim maximum line length limit

Janne Snabb — 2012-05-10T09:12:22

It appears that Exim core does not impose any limits on line lengths of
message bodies.

However, some optional Exim components have arbitrarily set limits:

src/src/pdkim/pdkim.c:
        #define PDKIM_MAX_BODY_LINE_LEN     16384

src/src/mime.h:
        #define MIME_MAX_LINE_LENGTH 32768

src/src/demime.h:
        #define MIME_SANITY_MAX_LINE_LENGTH 131071

I encountered a strange DKIM problem after I received a spam mail which
contained an embedded JPG image file, all encoded on a single long line.
The spam mail was received successfully, but when I tried to forward it
for further processing, the message got stuck in the queue and caused
the following log messages on each delivery attempt:

message delivery.

It appears that DKIM signing failed because the message contained a line
longer than 16384 characters and I had "dkim_strict = true". After
unsetting "dkim_strict" the delivery succeeded (without DKIM signature).

The problem can be repeated by setting DKIM signing policy to strict and
running the following command:

  perl -e 'print("x" x 60000 . "\n");' | mail foobar< at >example.com

According to RFC 5321 and RFC 5322 the maximum line length is 998
characters + CRLF, thus this is not really a bug. I am writing about
this just to make a note for people who might encounter the same issue
in future.


It appears that the line length topic has been discussed previously on
this list:

http://www.gossamer-threads.com/lists/exim/users/39793


Potential future enhancements:

 - Fix MIME and DKIM code to handle arbitrarily long lines.

 - Harmonize maximum line lengths (now Exim has three different
arbitrary limits for no particular reason).


My solution:

I can limit the line length of incoming messages in the DATA ACL by
adding the following:

deny    condition = ${if > {$max_received_linelength}{1024}}
        message = Maximum line length here is 1024 characters.

With this ACL in place I should not encounter this problem any more.


Best Regards,
--
Janne Snabb / EPIPE Communications
snabb< at >epipe.com - http://epipe.com/

exim-users ML a bit slow

Frank Elsner — 2012-05-09T13:03:07

Hi,
    is this normal or a teporary problem:

| Received: from tahini.csx.cam.ac.uk ([131.111.8.192])
| by mail.tu-berlin.de (exim-4.75/mailfrontend-3) with esmtp 
| for <Frank.Elsner< at >tu-berlin.de>
| id 1SRnz1-0004ag-E0; Tue, 08 May 2012 19:13:55 +0200
|                                             ^^^^^^^^^^^^^^
| Received: from localhost ([127.0.0.1]:35144 helo=tahini.csx.cam.ac.uk)
| by tahini.csx.cam.ac.uk with esmtp (Exim 4.76)
| (envelope-from <exim-users-bounces+frank.elsner=tu-berlin.de< at >exim.org>)
| id 1SRnz0-0004Ll-Fx
| for Frank.Elsner< at >tu-berlin.de; Tue, 08 May 2012 18:13:54 +0100
|                                                       ^^^^^^^^^^^^^^
| Received: from c64.shuttle.de ([194.95.226.64]:54266)
| by tahini.csx.cam.ac.uk with esmtp (Exim 4.76)
| (envelope-from <frank< at >moltke28.B.Shuttle.DE>) id 1SRkMo-0002gB-CJ
| for exim-users< at >exim.org; Tue, 08 May 2012 14:22:19 +0100
                                        ^^^^^^^^^^^^^^

Nearly 4 hours in Cambridge?


Just curious, Frank Elsner

[+]: Exim / Dovecot and AUTH LOGIN

Frank Elsner — 2012-05-08T13:34:26

Forgot to mention the versions :-(

exim 4.77
dovecot 2.1.6

self compiled under Fedora 14.


--Frank Elsner

Exim / Dovecot and AUTH LOGIN

Frank Elsner — 2012-05-08T13:22:11

Hi to both adressed mailing lists,

I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL

exim.conf:

|   plain:
|     driver = dovecot
|     public_name = PLAIN
|     server_socket = /var/run/dovecot/auth-client
|     server_set_id = $auth1
|   
|   login:
|     driver = dovecot
|     public_name = LOGIN
|     server_socket = /var/run/dovecot/auth-client
|     server_set_id = $auth1


10-master.conf for dovecot:

|   service auth {
|     # auth_socket_path points to this userdb socket by default. It's typically
|     # used by dovecot-lda, doveadm, possibly imap process, etc. Its default
|     # permissions make it readable only by root, but you may need to relax these
|     # permissions. Users that have access to this socket are able to get a list
|     # of all usernames and get results of everyone's userdb lookups.
|     # unix_listener auth-userdb {
|       #mode = 0600
|       #user =
|       #group =
|     # }
|   
|     # Exim SMTP AUTH
|     unix_listener auth-client {
|       mode = 0660
|       user = exim
|       group = exim
|     }


PLAIN Authentication works perfect, LOGIN gives 

2012-05-08 15:08:43 login authenticator failed for xxxxxx.tu-berlin.de [130.149.X.YY]: 435 Unable to authenticate at present: authentication socket protocol error


Where is the problem? 



Kind regards,
Frank Elsner

DKIM $dkim_signers

Wolfgang Breyha — 2012-05-08T15:46:14

Hi!

The current dkim implementation adds the d= parameter and the i= parameter to
the list of $dkim_signers. Both are added as found. That leads to a mix of
domains with an < at > in front as found in i= and domains without the < at > as found
in d=. RFC says that if i= missing < at >d= should be used.

In case that a sig contains
i=< at >domain.tld
and
d=domain.tld
both are added and the acl is run twice for the "same" entry.

I think d= should always be added with < at > prefix to $dkim_signers. Exim does
the rest already not running duplicate entries twice. Maybe the documentation
should contain a note that domains should always be prefixed with < at > if added
manually to dkim_verify_signers.

Greetings, Wolfgang

Using Exim to SMTP check Google Apps users?

Andrew White — 2012-05-07T21:52:55

Hi there,

I am researching if there is a way to create a check in Exim to query
Google Apps for valid destination email boxes and if so deliver the email,
is this possible and if so how could that be done?

Thanks,
Andrew