Mercurial > masqmail
annotate docs/howto-static-linking @ 246:4cff8638dd9b
SMTP client: tries EHLO now always first
Changed the behavior of the SMTP client. Now always an EHLO greeting
is sent, no matter what kind of greeting text the server had sent. If
the EHLO failed, an HELO greeting is tried as fall back. This is the
behavior RFC 2821 requires (section 3.2).
This change will fix setups that were not possible to sent to a
server because that requires AUTH but hadn't said ``ESMTP'' in its
greeting message.
See also: Debian bug #349211
Thanks to Steffen (inne)
| author | markus schnalke <meillo@marmaro.de> |
|---|---|
| date | Thu, 28 Oct 2010 16:40:02 -0300 |
| parents | 5cecc214afc9 |
| children |
| rev | line source |
|---|---|
| 202 | 1 Howto link masqmail statically? |
| 2 ------------------------------- | |
| 3 | |
| 4 With gcc (don't know anything about other compilers), you simply | |
| 5 build masqmail with: | |
| 6 | |
| 7 LDFLAGS=-static make -e | |
| 8 | |
| 9 | |
| 10 On Debian GNU/Linux, I received a bunch warnings of that kind: | |
| 11 | |
| 12 interface.o: In function `init_sockaddr': | |
| 13 interface.c:55: warning: Using 'gethostbyname' in statically | |
| 14 linked applications requires at runtime the shared libraries | |
| 15 from the glibc version used for linking | |
| 16 | |
| 17 On NetBSD I no warnings were printed. | |
| 18 | |
| 19 I don't have enough knowledge to tell the reasons and implications. | |
| 20 Maybe you can. | |
| 21 | |
| 22 | |
| 23 | |
| 24 meillo |