<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/emailrelay/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/emailrelay/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/emailrelay/bugs/</id><updated>2026-05-07T10:18:26.253000Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>#22 angle brackets around email address</title><link href="https://sourceforge.net/p/emailrelay/bugs/22/?limit=25#ce3e" rel="alternate"/><published>2026-05-07T10:18:26.253000Z</published><updated>2026-05-07T10:18:26.253000Z</updated><author><name>Graeme Walker</name><uri>https://sourceforge.net/u/graeme_walker/</uri></author><id>https://sourceforge.net85bd99f3de1f85ecb103ab107e84e55e67a19f03</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;You can use 2.6.1 on Windows, just add "--server-smtp-config=nostrictparsing".&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#22 angle brackets around email address</title><link href="https://sourceforge.net/p/emailrelay/bugs/22/?limit=25#2c49" rel="alternate"/><published>2026-05-07T07:39:03.744000Z</published><updated>2026-05-07T07:39:03.744000Z</updated><author><name>Great Tree Man</name><uri>https://sourceforge.net/u/greattreeman/</uri></author><id>https://sourceforge.netdbcafecf04a3bc5947539a6a6e269a6d6458abf4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
I'm facing the same issue right now with a scanner. It's sender field uses no brackets therefore SMTPRelay can't process it. I'm using the current version 2.6.1 for Windows. Is the patch.p1 still working for this version? Also I'm not too familiar with compiling, any recommendations for Windows?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#63  emailrelay-keygen.exe flagged as suspicious by AV and VirusTotal</title><link href="https://sourceforge.net/p/emailrelay/bugs/63/?limit=25#214e" rel="alternate"/><published>2026-02-03T20:15:44.113000Z</published><updated>2026-02-03T20:15:44.113000Z</updated><author><name>Graeme Walker</name><uri>https://sourceforge.net/u/graeme_walker/</uri></author><id>https://sourceforge.net204f5fcff60301605ebabbbad09ececf39f249c1</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#63  emailrelay-keygen.exe flagged as suspicious by AV and VirusTotal</title><link href="https://sourceforge.net/p/emailrelay/bugs/63/?limit=25#a52d" rel="alternate"/><published>2025-08-28T21:40:05.136000Z</published><updated>2025-08-28T21:40:05.136000Z</updated><author><name>Graeme Walker</name><uri>https://sourceforge.net/u/graeme_walker/</uri></author><id>https://sourceforge.net7e5fd2b557c1ad1fba742d7e9cb96985e1af36cb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;No, I'm not a fan of that game. I've played it before. Some virus scanners, particularly those with "AI" in the name, seem to be just random number generators with a commercially-sponsored whitelist attached. Even if a trivial rebuild passes today then there is no guarantee for tomorrow.&lt;/p&gt;
&lt;p&gt;FYI, for the 2.6 release I used an "air-gapped" Microsoft WinDev VM for the build. The code and all its dependencies are on GitHub &lt;a href="https://github.com/graeme-walker/emailrelay-build" rel="nofollow"&gt;https://github.com/graeme-walker/emailrelay-build&lt;/a&gt; , in case anyone wants to do their own build. For 2.7 I intend to use the GitHub CI/CD build servers.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#63  emailrelay-keygen.exe flagged as suspicious by AV and VirusTotal</title><link href="https://sourceforge.net/p/emailrelay/bugs/63/?limit=25#c12e/01a8" rel="alternate"/><published>2025-08-28T20:31:21.889000Z</published><updated>2025-08-28T20:31:21.889000Z</updated><author><name>George Bica</name><uri>https://sourceforge.net/u/gbica-hzo/</uri></author><id>https://sourceforge.netd45a46683543683fc2a57b1ebdfe50882a095917</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;OK, not sure if you can try and re-compile after changing the code a bit to see if it will help with ESET block.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#63  emailrelay-keygen.exe flagged as suspicious by AV and VirusTotal</title><link href="https://sourceforge.net/p/emailrelay/bugs/63/?limit=25#c12e" rel="alternate"/><published>2025-08-28T20:25:03.004000Z</published><updated>2025-08-28T20:25:03.004000Z</updated><author><name>Graeme Walker</name><uri>https://sourceforge.net/u/graeme_walker/</uri></author><id>https://sourceforge.net3a7f4c137f488efbb27ff07b4f8533a31ae13c46</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It creates a self-signed X509 certificate so that you can run an SMTP server with TLS, It is run by the emailrelay-setup installer if you check the "enable TLS encryption" checkbox on the "SMTP server" page without specifying a certificate file. If emailrelay-keygen.exe does not exist then you are forced to supply your own certificate file before the "next" button is enabled.&lt;/p&gt;
&lt;p&gt;See also: &lt;a href="https://sourceforge.net/p/emailrelay/support-requests/114/"&gt;https://sourceforge.net/p/emailrelay/support-requests/114/&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title> emailrelay-keygen.exe flagged as suspicious by AV and VirusTotal</title><link href="https://sourceforge.net/p/emailrelay/bugs/63/" rel="alternate"/><published>2025-08-28T20:06:27.049000Z</published><updated>2025-08-28T20:06:27.049000Z</updated><author><name>George Bica</name><uri>https://sourceforge.net/u/gbica-hzo/</uri></author><id>https://sourceforge.net2e9a87dd09f828522f7d7f95aacdbbfc5bf9c1f3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello, what is purpose of emailrelay-keygen.exe  and also note this EXE is flagged as suspicious. Heuristics AV blocked it when extracting from ZIP archive.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.virustotal.com/gui/file/cec436f860651e514a13e14e9b6c39576f686529017f42474ae3bf00757a1a26" rel="nofollow"&gt;https://www.virustotal.com/gui/file/cec436f860651e514a13e14e9b6c39576f686529017f42474ae3bf00757a1a26&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title> emailrelay-keygen.exe flagged as suspicious by AV and VirusTotal</title><link href="https://sourceforge.net/p/emailrelay/bugs/63/" rel="alternate"/><published>2025-08-28T20:06:27.049000Z</published><updated>2025-08-28T20:06:27.049000Z</updated><author><name>George Bica</name><uri>https://sourceforge.net/u/gbica-hzo/</uri></author><id>https://sourceforge.net2e7af0a556b12803024a6bf89464f3ae7153ddb0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 63 has been modified:  emailrelay-keygen.exe flagged as suspicious by AV and VirusTotal&lt;br/&gt;
Edited By: Graeme Walker (graeme_walker)&lt;br/&gt;
Status updated: 'open' =&amp;gt; 'closed'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#62 Change request on Multiple Processes</title><link href="https://sourceforge.net/p/emailrelay/bugs/62/?limit=25#6240" rel="alternate"/><published>2025-01-28T17:26:47.341000Z</published><updated>2025-01-28T17:26:47.341000Z</updated><author><name>Leona</name><uri>https://sourceforge.net/u/leonacarme/</uri></author><id>https://sourceforge.net0ca6f26481cb3d85d2c0bfb6909f5edd85b53d41</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;On doing some tests with the "split" at the end, or any position, I've noticed a bug when the client process the second message. &lt;br/&gt;
Looks like the ClientAccountSelector is not used when connecting to the remote server if the content's "To" field has more than one recipient. Even if the envelope is all correct.&lt;br/&gt;
Am I missing something?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#62 Change request on Multiple Processes</title><link href="https://sourceforge.net/p/emailrelay/bugs/62/?limit=25#eeaf" rel="alternate"/><published>2025-01-28T15:59:16.523000Z</published><updated>2025-01-28T15:59:16.523000Z</updated><author><name>Graeme Walker</name><uri>https://sourceforge.net/u/graeme_walker/</uri></author><id>https://sourceforge.net2cc6682abf8d2d964a3fe0c2cf41b4aacd5271ef</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I'm glad you've made progress.&lt;/p&gt;
&lt;p&gt;If you don't want to forward from the "x" unit to the default unit at all then it might be clearer/safer to use a bogus port number (such as zero or nine) for the "--forward-to" option, rather than 25. &lt;/p&gt;
&lt;p&gt;The "split:" filter should be the last in the chain because it potentially creates more messages and any filters after "split:" only run against the first message. If you need further processing it can go into a client-side filter, in which case its operation should be made idempotent to facilitate retries.&lt;/p&gt;
&lt;p&gt;If you are doing client account selection before the split then the same account will be used for all possible recipient-address domains. I would normally expect client account selection and routing to be dependent on each other, but YMMV.&lt;/p&gt;
&lt;p&gt;I note that falling back to A/AAAA address lookup after the MX lookup has come back with nothing is expected behaviour, so it should probably be at least a configuration option for the built-in "mx:" filter. Please open a feature request if that would be useful to you.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>