<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/smtp-dummy.c, branch master</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=master</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2019-06-29T19:18:15Z</updated>
<entry>
<title>test: run uncrustify</title>
<updated>2019-06-29T19:18:15Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-06-25T17:55:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bdc87f0d3ec41dd4744a89d1d19b2186d0647a56'/>
<id>urn:sha1:bdc87f0d3ec41dd4744a89d1d19b2186d0647a56</id>
<content type='text'>
This is the result of running:

    $ uncrustify --replace --config ../devel/uncrustify.cfg *.cc *.c *.h

in the test directory.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>test: let the OS choose a port for smtp-dummy</title>
<updated>2019-05-10T09:56:22Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-05-07T10:20:49Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f2425a11a3735a726bab60d4942ce82f77c47950'/>
<id>urn:sha1:f2425a11a3735a726bab60d4942ce82f77c47950</id>
<content type='text'>
This should avoid potential collisions if we start running multiple
smtp-dummy processes in parallel.
</content>
</entry>
<entry>
<title>test/smtp-dummy: convert to 'goto DONE' style</title>
<updated>2017-08-30T10:16:24Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-08-26T14:41:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=536d695a3151f78a0aed0a902298ac53826c46d6'/>
<id>urn:sha1:536d695a3151f78a0aed0a902298ac53826c46d6</id>
<content type='text'>
Clean up several cppcheck warnings of the form

      - test/smtp-dummy.c:170: error: Resource leak: output

Conform to overall notmuch code style.
</content>
</entry>
<entry>
<title>test/smtp-dummy: uncrustify</title>
<updated>2017-08-30T10:14:18Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-08-26T14:41:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1fa5bd282e37f71abcadb2c46750ba29273b6288'/>
<id>urn:sha1:1fa5bd282e37f71abcadb2c46750ba29273b6288</id>
<content type='text'>
For some reason lost in the mists of time this code was indented 8 spaces.
</content>
</entry>
<entry>
<title>Use https instead of http where possible</title>
<updated>2016-06-05T11:32:17Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-06-02T16:26:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6a833a6e83865f6999707cc30768d07e1351c2cb'/>
<id>urn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb</id>
<content type='text'>
Many of the external links found in the notmuch source can be resolved
using https instead of http.  This changeset addresses as many as i
could find, without touching the e-mail corpus or expected outputs
found in tests.
</content>
</entry>
<entry>
<title>test/smtp-dummy: add --background option and functionality</title>
<updated>2012-10-20T20:45:52Z</updated>
<author>
<name>Tomi Ollila</name>
<email>too@iki.fi</email>
</author>
<published>2012-09-18T14:23:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d894887c94c67860af817239bb1ce3b0360ec3e0'/>
<id>urn:sha1:d894887c94c67860af817239bb1ce3b0360ec3e0</id>
<content type='text'>
When shell executes background process using '&amp;' the scheduling of
that new process is arbitrary. It could be that smtp-dummy doesn't
get execution time to listen() it's server socket until some other
process attempts to connect() to it. The --background option in
smtp-dummy makes it to go background *after* it started to listen
its server socket.

When --background option is used, the line "smtp_dummy_pid='&lt;pid&gt;'"
is printed to stdout from where shell can eval it.
</content>
</entry>
<entry>
<title>test/smtp-dummy.c: fix compilation on FreeBSD</title>
<updated>2012-09-02T02:16:18Z</updated>
<author>
<name>Mike Kelly</name>
<email>pioto@pioto.org</email>
</author>
<published>2012-05-30T07:01:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1652ea7d1bdbf5b24b6b493f29a98f475d2d6b66'/>
<id>urn:sha1:1652ea7d1bdbf5b24b6b493f29a98f475d2d6b66</id>
<content type='text'>
Use the more portable netint/in.h, instead of netint/ip.h, to include
htons(3), etc.
</content>
</entry>
<entry>
<title>test: make smtp-dummy work with Emacs 24</title>
<updated>2011-11-13T17:48:02Z</updated>
<author>
<name>Thomas Jost</name>
<email>schnouki@schnouki.net</email>
</author>
<published>2011-10-03T16:47:27Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cb7270b27a4cef99fc4a3f5d44c461da5d622605'/>
<id>urn:sha1:cb7270b27a4cef99fc4a3f5d44c461da5d622605</id>
<content type='text'>
In Emacs 24, a space is expected after a SMTP response code. If we don't respect
that, smtpmail-send-it will wait forever.
</content>
</entry>
<entry>
<title>smtp-dummy: clear sockaddr_in structure before use in bind()</title>
<updated>2011-11-12T12:48:00Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2011-11-12T09:57:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ac46c6fdc23c0699ec53972a4082588b046559a2'/>
<id>urn:sha1:ac46c6fdc23c0699ec53972a4082588b046559a2</id>
<content type='text'>
Any junk bytes in sockaddr_in structure before passing that
to bind() system call may cause problems.
</content>
</entry>
<entry>
<title>smtp-dummy: Prefer return rather than exit() in main.</title>
<updated>2011-06-22T13:38:33Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2011-06-21T21:54:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b0ba84f9e71b0f117dc0bdf0b790c6e2341d3949'/>
<id>urn:sha1:b0ba84f9e71b0f117dc0bdf0b790c6e2341d3949</id>
<content type='text'>
The main() function should be written as just another function with a
return value. This allows for more reliable code reuse. Imagine that
main() grows too large and needs to be factored into multiple
functions. At that point, exit() is probably the wrong thing, yet can
also be hard to notice as it's in less-frequently-tested exceptional
cases.
</content>
</entry>
</feed>
