• PING Stefan Claas - mini.mailer

    From Mini Mailer@bounce.me@mini.mailer.msg to alt.privacy.anon-server on Sat Aug 9 16:36:27 2025
    From Newsgroup: alt.privacy.anon-server

    How can I avoid the 2nd. Message-ID below the message?
    Message-ID: <xddyrztx6b.1754757385@lqvvp.vc>
    Date: Sat, 09 Aug 2025 16:36:25 +0000

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mini Mailer@bounce.me@mini.mailer.msg to alt.privacy.anon-server on Sat Aug 9 17:25:12 2025
    From Newsgroup: alt.privacy.anon-server

    Mini Mailer wrote:

    How can I avoid the 2nd. Message-ID below the message?
    Message-ID: <xddyrztx6b.1754757385@lqvvp.vc>
    Date: Sat, 09 Aug 2025 16:36:25 +0000


    I remember, that there was a bug in an older *test* version, which
    showed this behaviour. All GitHub versions, GUI or CLI should work
    properly.

    Which version are you using?

    This message is posted with the GUI version v0.1.5

    Regards
    Stefan

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mini Mailer@bounce.me@mini.mailer.msg to alt.privacy.anon-server on Sun Aug 10 12:17:35 2025
    From Newsgroup: alt.privacy.anon-server

    Stefan wrote:

    Mini Mailer wrote:

    How can I avoid the 2nd. Message-ID below the message?
    Message-ID: <xddyrztx6b.1754757385@lqvvp.vc>
    Date: Sat, 09 Aug 2025 16:36:25 +0000


    I remember, that there was a bug in an older *test* version, which
    showed this behaviour. All GitHub versions, GUI or CLI should work
    properly.

    Which version are you using?

    This message is posted with the GUI version v0.1.5


    I use also v0.1.5
    minimailer-windows-amd64.exe sha256:e2fcca32fb97a5c91458cdb2ab443f85192fce8d56439fa765d555e47330f401

    Message-ID: <b1fudo3wqr.1754828252@oeyxj.bx>
    Date: Sun, 10 Aug 2025 12:17:32 +0000

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Stefan Claas@pollux@yeffqiea4xtcu6woyab6z6bz4oehisfuzgtmk4e277bydq25p7nha7ad.onion to alt.privacy.anon-server on Sun Aug 10 15:03:25 2025
    From Newsgroup: alt.privacy.anon-server

    Mini Mailer wrote:
    Stefan wrote:

    Mini Mailer wrote:

    How can I avoid the 2nd. Message-ID below the message?
    Message-ID: <xddyrztx6b.1754757385@lqvvp.vc>
    Date: Sat, 09 Aug 2025 16:36:25 +0000


    I remember, that there was a bug in an older *test* version, which
    showed this behaviour. All GitHub versions, GUI or CLI should work properly.

    Which version are you using?

    This message is posted with the GUI version v0.1.5


    I use also v0.1.5
    minimailer-windows-amd64.exe sha256:e2fcca32fb97a5c91458cdb2ab443f85192fce8d56439fa765d555e47330f401

    Message-ID: <b1fudo3wqr.1754828252@oeyxj.bx>
    Date: Sun, 10 Aug 2025 12:17:32 +0000


    I just downloaded Mini Mailer v0.1.5 from my GitHub account and
    your shasum matches, but I can't reproduce the bug, sorry.

    My Template looks like this:

    From: Mini Mailer <bounce.me@mini.mailer.msg>
    To: mail2news@dizum.com
    Subject:
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: 8bit
    Newsgroups:

    and my Configuration looks like this:

    SMTP Host smtp.dizum.com
    SMTP Port 2525
    SOCKS5 Port 9050
    Config File dizum
    Theme (light/dark) dark

    I am using Windows 11.

    Regards
    Stefan
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mini Mailer@bounce.me@mini.mailer.msg to alt.privacy.anon-server on Sun Aug 10 14:49:10 2025
    From Newsgroup: alt.privacy.anon-server

    Stefan,

    I'm using Windows 10 and with running TOR browser SOCKS5 Port 9150.

    but I can't reproduce the bug, sorry.
    No problem ! I will wait for the next version.



    Message-ID: <avjozp336k.1754837348@nyort.ka>
    Date: Sun, 10 Aug 2025 14:49:08 +0000

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Stefan Claas@pollux@yeffqiea4xtcu6woyab6z6bz4oehisfuzgtmk4e277bydq25p7nha7ad.onion to alt.privacy.anon-server on Fri Aug 22 20:57:30 2025
    From Newsgroup: alt.privacy.anon-server

    Mini Mailer wrote:
    Stefan,
    I'm using Windows 10 and with running TOR browser SOCKS5 Port 9150.
    but I can't reproduce the bug, sorry.
    No problem ! I will wait for the next version.


    Message-ID: <avjozp336k.1754837348@nyort.ka>
    Date: Sun, 10 Aug 2025 14:49:08 +0000


    Please try the new version v0.1.6.

    https://github.com/Ch1ffr3punk/mmg/releases/tag/v0.1.6

    I added a checkbox in the Configuration Tab to omit
    the automatic generation of the Message-ID and Date
    header, so that they should not be send any longer,
    when checked and then the server sets the headers.

    This was the easiest workaround for me. Hope you like!

    Regards
    Stefan
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mini Mailer@bounce.me@mini.mailer.msg to alt.privacy.anon-server on Mon Aug 25 17:01:13 2025
    From Newsgroup: alt.privacy.anon-server

    testing version v0.1.6


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mini Mailer@bounce.me@mini.mailer.msg to alt.privacy.anon-server on Mon Aug 25 17:17:46 2025
    From Newsgroup: alt.privacy.anon-server

    Mini Mailer wrote:

    testing version v0.1.6

    Thank you so much for the new version :-)

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Mini Mailer@bounce.me@mini.mailer.msg to alt.privacy.anon-server on Mon Aug 25 18:13:03 2025
    From Newsgroup: alt.privacy.anon-server

    Mini Mailer wrote:
    Mini Mailer wrote:

    testing version v0.1.6

    Thank you so much for the new version :-)


    You're welcome! I am glad that this is now
    working for you.

    Regards
    Stefan
    --
    -----BEGIN YUBIKEY SIGNATURE----- 54a2d5a47e8ae9a788ab22a288939c006af1c716cc61de48e32a09df874f1b30 9f5c637aea91898e522e381deb03591532028b1283a937f6727ecdc7e52edf21 9cb0435c7fcc6de11cf8302666ae1261927ebafb4914a4f7dd006f0141556415 d1bf72d813e229fae2c3c56a9336a52bbd94b82a1abf99ff709354a057947787
    -----END YUBIKEY SIGNATURE-----

    --- Synchronet 3.21a-Linux NewsLink 1.2