| 01:39:42.093 0 SMTP State: Trying server 'mail.virebent.art', port 25 for 'yamn@virebent.art' ...
| 01:39:42.093 0 SMTP State: 'From:' header set to 'invalid@msn.com', EHLO 'msn.com'
| 01:39:42.093 0 SMTP State: Connecting with mail host (mail.virebent.art:25 - 60000:40000 - TLS required - EHLO 'msn.com' - SOCKS5 - no authentication) ...
| 01:39:42.093 > SMTP State: Connecting to 127.0.0.1.
| 01:39:46.359 > SMTP State: Connected.
| 01:39:48.890 0 SMTP State: Connected with 'mail.virebent.art', port 25
| 01:39:48.890 0 SMTP Greeting:
| 01:39:48.890 0 SMTP Protocol Capabilities: PIPELINING|SIZE 52428800|ETRN|STARTTLS|ENHANCEDSTATUSCODES|8BITMIME|DSN|SMTPUTF8|CHUNKING
| 01:39:48.890 0 SMTP Encryption: TLS supported
| 01:39:48.890 0 SMTP State: Sending chunk 1 of 1 from 'invalid@msn.com' to 'yamn@virebent.art', server 'mail.virebent.art', port 25 ...
| 01:39:49.640 > SMTP SSL Status Info: SSL status: "before/connect initialization"
| 01:39:49.640 > SMTP SSL Status Info: SSL status: "before/connect initialization"
| 01:39:49.640 > SMTP SSL Status Info: SSL status: "SSLv2/v3 write client hello A"
| 01:39:50.422 > SMTP SSL Status Info: SSL status: "SSLv2/v3 read server hello A"
| 01:39:50.422 > SMTP SSL Status Info: SSL status: "SSLv2/v3 read server hello A"
| 01:39:50.422 > SMTP State: Disconnecting.
| 01:39:50.422 > SMTP Response: Ready to start TLS
| 01:39:50.422 > SMTP State: Disconnected.
| 01:39:50.422 0 SMTP State: None of 1 chunk sent.
| 01:39:50.422 0 SMTP Error: SSL negotiation failed.: 220
| 01:39:50.422 0 SMTP State: Sending directly to anon SMTP host failed

| 01:40:56.359 0 SMTP State: Connected with 'mixrelay.mixmin.net', port 2525
| ...
| 01:41:01.109 0 SMTP Error: <yamn@virebent.art>: Relay access denied: 250 - Ok

| 01:41:10.031 0 SMTP State: Connected with 'tncsrv06.tnetconsulting.net', port 25
| ...
| 01:41:16.859 0 SMTP Error: <yamn@virebent.art>... Relaying denied. IP name lookup failed [23.129.64.142]: 250 - Reset state

(with stats from https://www.mixmin.net/yamn/mlist2.txt)

On 3/26/24 04:18, Nomen Nescio wrote:

> | 01:40:56.359 0 SMTP State: Connected with 'mixrelay.mixmin.net', port 2525
> | ...
> | 01:41:01.109 0 SMTP Error: <yamn@virebent.art>: Relay access denied: 250 - Ok

This is the problem. You are trying to relay to a YAMN remailer through
mixrelay.mixmin.net (aka fleegle.mixmin.net). But mixmin.net only allows
relaying to Mixmaster remailers. Not to YAMN remailers.

Try smtp.tnetconsulting.net or mailrelay.archiade.net

See <https://www.sec3.net/misc/mail-relays.html>

--
SEC3

YAMN Help Tutorial - https://www.sec3.net/yamnhelp/

Nomen Nescio <nobody@dizum.com> posted some

You might run into this problem with the YAMN client sending directly to
OmniMix (localhost / 127.0.0.1 vs one of the external YAMN remailers.

Check three things.

1. StateExt tab, Info tab. Replace whatever is there with the strings
below. This will clean up some stuff in the tabs on the right. Look
through the tabs for comparison before you change and Stop / Start.

If a change is made, the indicator (NSPHD) background will change to
pink, Stop and Start will clear and set.

2. Anon, Server (Just before News tab). This will probably fix your
issue.

1. If your client is configured to send to localhost / 127.0.0.1,
uncheck "Use Tor". Be aware this will rat out your real IP address
during the client stats update. Not a big deal as it's a query. Lots
of those from many sources out there. Leaving it checked will result in
an attempt to connect to localhost / 127.0.0.1 on the exit relay.

2. In OmniMix, change SSL to "TLS disabled" in the MailSnd (SMTP)
column.

This only affects communication between your sending client and the
OmniMix listening port on the local machine. It does not affect
outbound TLS / SSL communications from the OmniMix SMTP server to the
receiving SMTP server. You will be able to plainly see and verify this
in the Log, Raw Data and Rem Data tabs.

Stop and Start.

3. Optional, but sometimes the source goes down. Note that sometimes
this is a Tor problem as well. Try stopping and starting Tor before
changing.

If you suspect OmniMix is having issues with SMTP servers and keys, go
to StateExt, Yamn tab.

If it has mixmin there, that's fine, leave it. If you want to try a
different source, try tincture or haph.

-OR- (Optional)
-OR- (Optional)
https://www.haph.org/yamn/pubring.mix
https://www.haph.org/yamn/mlist2.txt

If you change it, Stop and Start.

Nomen Nescio <nobody@dizum.com> wrote in
news:89a54f09fae69aa416cda4d86ad4ef05@dizum.com:

>| 01:39:42.093 0 SMTP State: Trying server 'mail.virebent.art', port 25
>| for 'yamn@virebent.art' ... 01:39:42.093 0 SMTP State: 'From:' header
>| set to 'invalid@msn.com', EHLO 'msn.com' 01:39:42.093 0 SMTP State:
>| Connecting with mail host (mail.virebent.art:25 - 60000:40000 - TLS
>| required - EHLO 'msn.com' - SOCKS5 - no authentication) ...
>| 01:39:42.093 > SMTP State: Connecting to 127.0.0.1. 01:39:46.359 >
>| SMTP State: Connected. 01:39:48.890 0 SMTP State: Connected with
>| 'mail.virebent.art', port 25 01:39:48.890 0 SMTP Greeting:
>| 01:39:48.890 0 SMTP Protocol Capabilities: PIPELINING|SIZE
>| 52428800|ETRN|STARTTLS|ENHANCEDSTATUSCODES|8BITMIME|DSN|SMTPUTF8|CHUNK
>| ING 01:39:48.890 0 SMTP Encryption: TLS supported
>| 01:39:48.890 0 SMTP State: Sending chunk 1 of 1 from
>| 'invalid@msn.com' to 'yamn@virebent.art', server 'mail.virebent.art',
>| port 25 ... 01:39:49.640 > SMTP SSL Status Info: SSL status:
>| "before/connect initialization" 01:39:49.640 > SMTP SSL Status Info:
>| SSL status: "before/connect initialization" 01:39:49.640 > SMTP SSL
>| Status Info: SSL status: "SSLv2/v3 write client hello A" 01:39:50.422
>| > SMTP SSL Status Info: SSL status: "SSLv2/v3 read server hello A"
>| 01:39:50.422 > SMTP SSL Status Info: SSL status: "SSLv2/v3 read
>| server hello A" 01:39:50.422 > SMTP State: Disconnecting.
>| 01:39:50.422 > SMTP Response: Ready to start TLS
>| 01:39:50.422 > SMTP State: Disconnected.
>| 01:39:50.422 0 SMTP State: None of 1 chunk sent.
>| 01:39:50.422 0 SMTP Error: SSL negotiation failed.: 220
>| 01:39:50.422 0 SMTP State: Sending directly to anon SMTP host failed
>
>| 01:40:56.359 0 SMTP State: Connected with 'mixrelay.mixmin.net', port
>| 2525 ...
>| 01:41:01.109 0 SMTP Error: <yamn@virebent.art>: Relay access denied:
>| 250 - Ok
>
>| 01:41:10.031 0 SMTP State: Connected with
>| 'tncsrv06.tnetconsulting.net', port 25 ...
>| 01:41:16.859 0 SMTP Error: <yamn@virebent.art>... Relaying denied. IP
>| name lookup failed [23.129.64.142]: 250 - Reset state
>
> (with stats from https://www.mixmin.net/yamn/mlist2.txt)

Apologies.

I sent my earlier response using the YAMN client, it stripped out a bunch.
It tends to do that sometimes.

Resending all from QS.

You might run into this problem with the YAMN client sending directly to
OmniMix (localhost / 127.0.0.1) vs one of the external YAMN remailers.

Check three things.

1. StateExt tab, Info tab. Replace whatever is there with the strings
below. This will clean up some stuff in the tabs on the right. Look
through the tabs for comparison before you change and Stop / Start.

Mail2News: https://www.sec3.net/misc/mail-relays.txt
AllPingers: https://www.sec3.net/misc/allpingers.txt
MX Servers: https://sec3.net/misc/TLS-info.html

If a change is made, the indicator (NSPHD) background will change to pink,
Stop and Start will clear and set.

2. Anon, Server (Just before News tab). This will probably fix your
issue.

1. If your client is configured to send to localhost / 127.0.0.1, uncheck
"Use Tor". Be aware this will rat out your real IP address during the
client stats update. Not a big deal as it's a query. Lots of those from
many sources out there. Leaving it checked will result in an attempt to
connect to localhost / 127.0.0.1 on the exit relay.

2. In OmniMix, change SSL to "TLS disabled" in the MailSnd (SMTP) column.

This only affects communication between your sending client and the
OmniMix listening port on the local machine. It does not affect outbound
TLS / SSL communications from the OmniMix SMTP server to the receiving
SMTP server. You will be able to plainly see and verify this in the Log,
Raw Data and Rem Data tabs.

Stop and Start.

3. Optional, but sometimes the source goes down. Note that sometimes this
is a Tor problem as well. Try stopping and starting Tor before changing.

If you suspect OmniMix is having issues with SMTP servers and keys, go to
StateExt, Yamn tab.

If it has mixmin there, that's fine, leave it. If you want to try a
different source, try tincture or haph.

Stats: https://www.mixmin.net/yamn/mlist2.txt
Keys: https://www.mixmin.net/yamn/pubring.mix
-OR- (Optional)
Stats: https://tincture.ws/pinger/yamn/mlist2.txt
Keys: https://tincture.ws/pinger/yamn/pubring.mix
-OR- (Optional)
https://www.haph.org/yamn/pubring.mix
https://www.haph.org/yamn/mlist2.txt

If you change it, Stop and Start.

anonymous <noreply@mixmin.net> posted some

> 2. Anon, Server (Just before News tab). This will probably fix your
> issue.
>
> 1. If your client is configured to send to localhost / 127.0.0.1,
uncheck
> "Use Tor". Be aware this will rat out your real IP address during the
> client stats update. Not a big deal as it's a query. Lots of those
from
> many sources out there. Leaving it checked will result in an attempt
to
> connect to localhost / 127.0.0.1 on the exit relay.
>
> 2. In OmniMix, change SSL to "TLS disabled" in the MailSnd (SMTP)
column.
>
> Stop and Start.

Thanks for the tip! This worked for me.

anonymous <noreply@mixmin.net> wrote:

>Apologies.
>
>I sent my earlier response using the YAMN client, it stripped out a bunch.
>It tends to do that sometimes.

OM won't. ;-)

>
>Resending all from QS.
>
>You might run into this problem with the YAMN client sending directly to
>OmniMix (localhost / 127.0.0.1) vs one of the external YAMN remailers.
>
>Check three things.
>
>1. StateExt tab, Info tab. Replace whatever is there with the strings
>below. This will clean up some stuff in the tabs on the right. Look
>through the tabs for comparison before you change and Stop / Start.
>
>Mail2News: https://www.sec3.net/misc/mail-relays.txt
>AllPingers: https://www.sec3.net/misc/allpingers.txt
>MX Servers: https://sec3.net/misc/TLS-info.html
>
>If a change is made, the indicator (NSPHD) background will change to pink,
>Stop and Start will clear and set.
>
>2. Anon, Server (Just before News tab). This will probably fix your
>issue.
>
>1. If your client is configured to send to localhost / 127.0.0.1, uncheck
>"Use Tor".

Where? In your client? Which client?

> Be aware this will rat out your real IP address during the
>client stats update.

What's a client stats update?

>Not a big deal as it's a query. Lots of those from
>many sources out there. Leaving it checked will result in an attempt to
>connect to localhost / 127.0.0.1 on the exit relay.

Localhost on the exit relay? What???

>
>2. In OmniMix, change SSL to "TLS disabled" in the MailSnd (SMTP) column.

Why not "TLS enabled", which uses encryption if available?

>
>This only affects communication between your sending client and the
>OmniMix listening port on the local machine. It does not affect outbound
>TLS / SSL communications from the OmniMix SMTP server to the receiving
>SMTP server. You will be able to plainly see and verify this in the Log,
>Raw Data and Rem Data tabs.
>
>Stop and Start.
>
>3. Optional, but sometimes the source goes down. Note that sometimes this
>is a Tor problem as well. Try stopping and starting Tor before changing.
>
>If you suspect OmniMix is having issues with SMTP servers and keys, go to
>StateExt, Yamn tab.
>
>If it has mixmin there, that's fine, leave it. If you want to try a
>different source, try tincture or haph.
>
>Stats: https://www.mixmin.net/yamn/mlist2.txt
>Keys: https://www.mixmin.net/yamn/pubring.mix
>-OR- (Optional)
>Stats: https://tincture.ws/pinger/yamn/mlist2.txt
>Keys: https://tincture.ws/pinger/yamn/pubring.mix
>-OR- (Optional)
>https://www.haph.org/yamn/pubring.mix
>https://www.haph.org/yamn/mlist2.txt
>
>If you change it, Stop and Start.