This post is submitted by the YAMN_Remailer_Client_v0.4.05_
[build_1322], outbound through OmniMix 2.6.2, 127.0.0.1:25.

In order for this to work, Server tab, Mail Snd (SMTP), TLS disabled
vs TLS enabled.

I don't see a problem with this as the client to OmniMix
communication is on the same host and inaccessible externally.

QSL 1.1.4

It's the same for QSL 1.1.4, Server tab, Mail Snd (SMTP), TLS
disabled vs TLS enabled.

QSL is limited to 1 copy this way. It gets hung up at the second
copy and must be killed with task manager.

Sending mixmaster packet 2 of 3
Connected to localhost:25
e OmniMix SMTP Server (V.2.6.2 - Non-Commercial License)
e OmniMix SMTP Server (V.2.6.2 - Non-Commercial License)

For whatever reason there are two end connection lines when it
hangs. Believe this to be a QSL issue.

The post will still make it with Copies=1. Tested four, all four
arrived.

End QSL comments.

I have devurandom and other mail servers configured in the Anon Mail
S, Anon tab.

Currently the default outbound server is devurandom. The yamn posts
were relayed by devurandom.

You can see them identified as yamn2,yamn3,etc. in the Outgoing
Messages window.

Very Nice Work!

sci local <none@anonymous.net> wrote:

>This post is submitted by the YAMN_Remailer_Client_v0.4.05_
>[build_1322], outbound through OmniMix 2.6.2, 127.0.0.1:25.
>
>In order for this to work, Server tab, Mail Snd (SMTP), TLS disabled
>vs TLS enabled.
>
>I don't see a problem with this as the client to OmniMix
>communication is on the same host and inaccessible externally.
>
>QSL 1.1.4
>
>It's the same for QSL 1.1.4, Server tab, Mail Snd (SMTP), TLS
>disabled vs TLS enabled.
>
>QSL is limited to 1 copy this way. It gets hung up at the second
>copy and must be killed with task manager.
>
>Sending mixmaster packet 2 of 3
>Connected to localhost:25
> e OmniMix SMTP Server (V.2.6.2 - Non-Commercial License)
> e OmniMix SMTP Server (V.2.6.2 - Non-Commercial License)
>
>For whatever reason there are two end connection lines when it
>hangs. Believe this to be a QSL issue.
>
>The post will still make it with Copies=1. Tested four, all four
>arrived.
>
>End QSL comments.
>
>I have devurandom and other mail servers configured in the Anon Mail
>S, Anon tab.
>
>Currently the default outbound server is devurandom. The yamn posts
>were relayed by devurandom.
>
>You can see them identified as yamn2,yamn3,etc. in the Outgoing
>Messages window.
>
>
>Very Nice Work!

Have you tried to allow insecure TLS v1.0 connections (S3 checkboxes @
OM's Server tab), deactivated by default?

In article
<ae74fcef210f8e2036d5b17299ceeb45@remailer.paranoici.org>
Anonymous <nobody@remailer.paranoici.org> wrote:
>
> sci local <none@anonymous.net> wrote:
>
> >This post is submitted by the YAMN_Remailer_Client_v0.4.05_
> >[build_1322], outbound through OmniMix 2.6.2, 127.0.0.1:25.
> >
> >In order for this to work, Server tab, Mail Snd (SMTP), TLS disabled
> >vs TLS enabled.
> >
> >I don't see a problem with this as the client to OmniMix
> >communication is on the same host and inaccessible externally.
> >
> >QSL 1.1.4
> >
> >It's the same for QSL 1.1.4, Server tab, Mail Snd (SMTP), TLS
> >disabled vs TLS enabled.
> >
> >QSL is limited to 1 copy this way. It gets hung up at the second
> >copy and must be killed with task manager.
> >
> >Sending mixmaster packet 2 of 3
> >Connected to localhost:25
> > e OmniMix SMTP Server (V.2.6.2 - Non-Commercial License)
> > e OmniMix SMTP Server (V.2.6.2 - Non-Commercial License)
> >
> >For whatever reason there are two end connection lines when it
> >hangs. Believe this to be a QSL issue.
> >
> >The post will still make it with Copies=1. Tested four, all four
> >arrived.
> >
> >End QSL comments.
> >
> >I have devurandom and other mail servers configured in the Anon Mail
> >S, Anon tab.
> >
> >Currently the default outbound server is devurandom. The yamn posts
> >were relayed by devurandom.
> >
> >You can see them identified as yamn2,yamn3,etc. in the Outgoing
> >Messages window.
> >
> >
> >Very Nice Work!
>
> Have you tried to allow insecure TLS v1.0 connections (S3 checkboxes @
> OM's Server tab), deactivated by default?

Yes. Tried that first. No success until disabling TLS for
inbound SMTP.

----With TLS enabled S3 checked or unchecked, no difference----
10:53:29.192 X Stopping servers ...
10:53:29.209 X Servers stopped
10:53:32.184 X Starting servers in Normal Mode ...
10:53:33.321 X Servers started in Normal Mode
10:54:26.587 X Client connection request (SMTP Port 25 IPext
127.0.0.1 IPint 127.0.0.1)
10:54:26.587 X Checking for ImplicitSSL client connection
request ...
10:54:28.594 X Non-ImplicitSSL client request detected
10:54:28.682 X Server SSL Status Info: SSL status:
"before/accept initialization"
10:54:28.682 X Server SSL Status Info: SSL status:
"before/accept initialization"
10:54:28.700 X Server SSL Status Info: SSL status: "error"
10:54:28.700 X Server SSL Status Info: SSL status: "error"
10:54:28.700 X Server SSL Status Info: SSL status: "error"

This does not affect outbound SMTP traffic as you can see TLS /
SSL connections continue to be negotiated between OmniMix and
the receiving SMTP server. Example below.

11:10:12.181 > SMTP SSL Status Info: SSL status: "before/connect
initialization"
11:10:12.181 > SMTP SSL Status Info: SSL status: "before/connect
initialization"
11:10:12.182 > SMTP SSL Status Info: SSL status: "SSLv2/v3 write
client hello A"
11:10:12.862 > SMTP SSL Status Info: SSL status: "SSLv3 read
server hello A"
11:10:13.097 C Request for adding Certificate (Fprint
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ) ...
11:10:13.097 > SMTP TLA Certificate (Depth 0, REJECTED_NO_ENTRY -
Connection not refused (Filter deactivated)):
11:10:13.097 Fprint : ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
11:10:13.097 Subject: /CN=mail.anonymitaet-im-inter.net
11:10:13.097 Issuer : /C=US/O=Let's Encrypt/CN=R3
11:10:13.097 Valid : 2021-09-06 06:47:23 ... 2021-12-05
06:47:22
11:10:13.098 C Request for adding Certificate (Fprint
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ) ...
11:10:13.098 > SMTP TLA Certificate (Depth 0, REJECTED_NO_ENTRY -
Connection not refused (Filter deactivated)):
11:10:13.098 Fprint : ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
11:10:13.098 Subject: /CN=mail.anonymitaet-im-inter.net
11:10:13.098 Issuer : /C=US/O=Let's Encrypt/CN=R3
11:10:13.098 Valid : 2021-09-06 06:47:23 ... 2021-12-05
06:47:22
11:10:13.098 > SMTP SSL Status Info: SSL status: "SSLv3 read
server certificate A"
11:10:13.100 > SMTP SSL Status Info: SSL status: "SSLv3 read
server key exchange A"
11:10:13.100 > SMTP SSL Status Info: SSL status: "SSLv3 read
server done A"
11:10:13.104 C Certificate (Fprint
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ) added:
11:10:13.104 Subject: /CN=mail.anonymitaet-im-inter.net
11:10:13.104 Issuer : /C=US/O=Let's Encrypt/CN=R3
11:10:13.104 Valid : 2021-09-06 06:47:23 ... 2021-12-05
06:47:22
11:10:13.117 C Certificate (Fprint
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ) already known
11:10:13.171 > SMTP SSL Status Info: SSL status: "SSLv3 write
client key exchange A"
11:10:13.171 > SMTP SSL Status Info: SSL status: "SSLv3 write
change cipher spec A"
11:10:13.171 > SMTP SSL Status Info: SSL status: "SSLv3 write
finished A"
11:10:13.171 > SMTP SSL Status Info: SSL status: "SSLv3 flush
data"
11:10:13.724 > SMTP SSL Status Info: SSL status: "SSLv3 read
server session ticket A"
11:10:13.725 > SMTP SSL Status Info: SSL status: "SSLv3 read
finished A"
11:10:13.725 > SMTP SSL Status Info: SSL status: "SSL
negotiation finished successfully"
11:10:13.725 > SMTP SSL Status Info: SSL status: "SSL
negotiation finished successfully"
11:10:13.725 > SMTP SSL Status Info: Cipher: name = DHE-RSA-
AES256-GCM-SHA384; description = DHE-RSA-AES256-GCM-SHA384
TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(256) Mac=AEAD|; bits = 256;
version = TLSv1/SSLv3;

Additional note.

This change also now permits use of the OmniMix HS Address (V3
onion) with QSL 1.1.4. Tested it running remotely on a VM from
three external locations / different networks (hotel, coffee
shop, airport) several hundred miles distant. It is not fast -
that is Tor latency not OmniMix.

Richard made mention in the QSL 1.1.4 release notes that he was
undecided with some portions of TLS implementation. It's
possible he had not yet addressed local connectivity.

Original QuickSilver.

None of these changes are necessary with QS 1.2.7 and OmniMix
2.6.2. It works flawlessly, localhost or OmniMix HS Address (V3
onion). No copy issues.

The YAMN_Remailer_Client effort was just an experiment to see if
it would work with the latest OmniMix release supporting yamn.
It does (With the TLS adjustment) and there are no copy issues.

sci local <none@anonymous.net> wrote:

>In article
><ae74fcef210f8e2036d5b17299ceeb45@remailer.paranoici.org>
>Anonymous <nobody@remailer.paranoici.org> wrote:
>>
>> sci local <none@anonymous.net> wrote:
>>
>> >This post is submitted by the YAMN_Remailer_Client_v0.4.05_
>> >[build_1322], outbound through OmniMix 2.6.2, 127.0.0.1:25.
>> >
>> >In order for this to work, Server tab, Mail Snd (SMTP), TLS disabled
>> >vs TLS enabled.
>> >
>> >I don't see a problem with this as the client to OmniMix
>> >communication is on the same host and inaccessible externally.
>> >
>> >QSL 1.1.4
>> >
>> >It's the same for QSL 1.1.4, Server tab, Mail Snd (SMTP), TLS
>> >disabled vs TLS enabled.
>> >
>> >QSL is limited to 1 copy this way. It gets hung up at the second
>> >copy and must be killed with task manager.
>> >
>> >Sending mixmaster packet 2 of 3
>> >Connected to localhost:25
>> > e OmniMix SMTP Server (V.2.6.2 - Non-Commercial License)
>> > e OmniMix SMTP Server (V.2.6.2 - Non-Commercial License)
>> >
>> >For whatever reason there are two end connection lines when it
>> >hangs. Believe this to be a QSL issue.
>> >
>> >The post will still make it with Copies=1. Tested four, all four
>> >arrived.
>> >
>> >End QSL comments.
>> >
>> >I have devurandom and other mail servers configured in the Anon Mail
>> >S, Anon tab.
>> >
>> >Currently the default outbound server is devurandom. The yamn posts
>> >were relayed by devurandom.
>> >
>> >You can see them identified as yamn2,yamn3,etc. in the Outgoing
>> >Messages window.
>> >
>> >
>> >Very Nice Work!
>>
>> Have you tried to allow insecure TLS v1.0 connections (S3 checkboxes @
>> OM's Server tab), deactivated by default?
>
>Yes. Tried that first. No success until disabling TLS for
>inbound SMTP.
>
>----With TLS enabled S3 checked or unchecked, no difference----
>10:53:29.192 X Stopping servers ...
>10:53:29.209 X Servers stopped
>10:53:32.184 X Starting servers in Normal Mode ...
>10:53:33.321 X Servers started in Normal Mode
>10:54:26.587 X Client connection request (SMTP Port 25 IPext
>127.0.0.1 IPint 127.0.0.1)
>10:54:26.587 X Checking for ImplicitSSL client connection
>request ...
>10:54:28.594 X Non-ImplicitSSL client request detected
>10:54:28.682 X Server SSL Status Info: SSL status:
>"before/accept initialization"
>10:54:28.682 X Server SSL Status Info: SSL status:
>"before/accept initialization"
>10:54:28.700 X Server SSL Status Info: SSL status: "error"
>10:54:28.700 X Server SSL Status Info: SSL status: "error"
>10:54:28.700 X Server SSL Status Info: SSL status: "error"
>
>This does not affect outbound SMTP traffic as you can see TLS /
>SSL connections continue to be negotiated between OmniMix and
>the receiving SMTP server. Example below.
>
>11:10:12.181 > SMTP SSL Status Info: SSL status: "before/connect
>initialization"
>11:10:12.181 > SMTP SSL Status Info: SSL status: "before/connect
>initialization"
>11:10:12.182 > SMTP SSL Status Info: SSL status: "SSLv2/v3 write
>client hello A"
>11:10:12.862 > SMTP SSL Status Info: SSL status: "SSLv3 read
>server hello A"
>11:10:13.097 C Request for adding Certificate (Fprint
>ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ) ...
>11:10:13.097 > SMTP TLA Certificate (Depth 0, REJECTED_NO_ENTRY -
> Connection not refused (Filter deactivated)):
>11:10:13.097 Fprint : ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
>11:10:13.097 Subject: /CN=mail.anonymitaet-im-inter.net
>11:10:13.097 Issuer : /C=US/O=Let's Encrypt/CN=R3
>11:10:13.097 Valid : 2021-09-06 06:47:23 ... 2021-12-05
>06:47:22
>11:10:13.098 C Request for adding Certificate (Fprint
>ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ) ...
>11:10:13.098 > SMTP TLA Certificate (Depth 0, REJECTED_NO_ENTRY -
> Connection not refused (Filter deactivated)):
>11:10:13.098 Fprint : ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
>11:10:13.098 Subject: /CN=mail.anonymitaet-im-inter.net
>11:10:13.098 Issuer : /C=US/O=Let's Encrypt/CN=R3
>11:10:13.098 Valid : 2021-09-06 06:47:23 ... 2021-12-05
>06:47:22
>11:10:13.098 > SMTP SSL Status Info: SSL status: "SSLv3 read
>server certificate A"
>11:10:13.100 > SMTP SSL Status Info: SSL status: "SSLv3 read
>server key exchange A"
>11:10:13.100 > SMTP SSL Status Info: SSL status: "SSLv3 read
>server done A"
>11:10:13.104 C Certificate (Fprint
>ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ) added:
>11:10:13.104 Subject: /CN=mail.anonymitaet-im-inter.net
>11:10:13.104 Issuer : /C=US/O=Let's Encrypt/CN=R3
>11:10:13.104 Valid : 2021-09-06 06:47:23 ... 2021-12-05
>06:47:22
>11:10:13.117 C Certificate (Fprint
>ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ) already known
>11:10:13.171 > SMTP SSL Status Info: SSL status: "SSLv3 write
>client key exchange A"
>11:10:13.171 > SMTP SSL Status Info: SSL status: "SSLv3 write
>change cipher spec A"
>11:10:13.171 > SMTP SSL Status Info: SSL status: "SSLv3 write
>finished A"
>11:10:13.171 > SMTP SSL Status Info: SSL status: "SSLv3 flush
>data"
>11:10:13.724 > SMTP SSL Status Info: SSL status: "SSLv3 read
>server session ticket A"
>11:10:13.725 > SMTP SSL Status Info: SSL status: "SSLv3 read
>finished A"
>11:10:13.725 > SMTP SSL Status Info: SSL status: "SSL
>negotiation finished successfully"
>11:10:13.725 > SMTP SSL Status Info: SSL status: "SSL
>negotiation finished successfully"
>11:10:13.725 > SMTP SSL Status Info: Cipher: name = DHE-RSA-
>AES256-GCM-SHA384; description = DHE-RSA-AES256-GCM-SHA384
>TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(256) Mac=AEAD|; bits = 256;
>version = TLSv1/SSLv3;
>
>Additional note.
>
>This change also now permits use of the OmniMix HS Address (V3
>onion) with QSL 1.1.4. Tested it running remotely on a VM from
>three external locations / different networks (hotel, coffee
>shop, airport) several hundred miles distant. It is not fast -
>that is Tor latency not OmniMix.

Great! And I'm still waiting for Android client software with SOCKS
support, which e.g. K-9 Mail announced years ago, but never delivered.

>
>Richard made mention in the QSL 1.1.4 release notes that he was
>undecided with some portions of TLS implementation. It's
>possible he had not yet addressed local connectivity.

So it may really be broken.

>
>Original QuickSilver.
>
>None of these changes are necessary with QS 1.2.7 and OmniMix
>2.6.2. It works flawlessly, localhost or OmniMix HS Address (V3
>onion). No copy issues.
>
>The YAMN_Remailer_Client effort was just an experiment to see if
>it would work with the latest OmniMix release supporting yamn.
>It does (With the TLS adjustment) and there are no copy issues.

Complex yet stable, that's how it has to be. :-)

In article <5be078e611cd78e2e406a2003c619445@dizum.com>
Nomen Nescio <nobody@dizum.com> wrote:
>
> sci local <none@anonymous.net> wrote:
>
> >Additional note.
> >
> >This change also now permits use of the OmniMix HS Address (V3
> >onion) with QSL 1.1.4. Tested it running remotely on a VM from
> >three external locations / different networks (hotel, coffee
> >shop, airport) several hundred miles distant. It is not fast -
> >that is Tor latency not OmniMix.
>
> Great! And I'm still waiting for Android client software with SOCKS
> support, which e.g. K-9 Mail announced years ago, but never delivered.
>
> >
> >Richard made mention in the QSL 1.1.4 release notes that he was
> >undecided with some portions of TLS implementation. It's
> >possible he had not yet addressed local connectivity.
>
> So it may really be broken.

Maybe a little but it works well enough as long as the core
mixmaster server resources are used.

> >
> >Original QuickSilver.
> >
> >None of these changes are necessary with QS 1.2.7 and OmniMix
> >2.6.2. It works flawlessly, localhost or OmniMix HS Address (V3
> >onion). No copy issues.
> >
> >The YAMN_Remailer_Client effort was just an experiment to see if
> >it would work with the latest OmniMix release supporting yamn.
> >It does (With the TLS adjustment) and there are no copy issues.
>
> Complex yet stable, that's how it has to be. :-)

OmniMix is quite the sophisticated resource.

In article
<e527ed2bdd4e9425930ca129b725cf89@msgid.frell.theremailer.net>
sci local <none@anonymous.net> wrote:
>
> > >
> > >The YAMN_Remailer_Client effort was just an experiment to see if
> > >it would work with the latest OmniMix release supporting yamn.
> > >It does (With the TLS adjustment) and there are no copy issues.
> >
> > Complex yet stable, that's how it has to be. :-)
>
> OmniMix is quite the sophisticated resource.

I tried your change and it works great! Thanks! I can send out
locally via OmniMix SMTP now.

In article <d40b7eb15474a6161a9eba0028a6cde0@dizum.com>
Nomen Nescio <nobody@dizum.com> wrote:
>
> In article
> <e527ed2bdd4e9425930ca129b725cf89@msgid.frell.theremailer.net>
> sci local <none@anonymous.net> wrote:
> >
> > > >
> > > >The YAMN_Remailer_Client effort was just an experiment to see if
> > > >it would work with the latest OmniMix release supporting yamn.
> > > >It does (With the TLS adjustment) and there are no copy issues.
> > >
> > > Complex yet stable, that's how it has to be. :-)
> >
> > OmniMix is quite the sophisticated resource.
>
> I tried your change and it works great! Thanks! I can send out
> locally via OmniMix SMTP now.

Same here. Did not even consider doing that as OmniMix worked
so well with the old QS.

Nomen Nescio <nobody@dizum.com> wrote:
>In article <d40b7eb15474a6161a9eba0028a6cde0@dizum.com>
>Nomen Nescio <nobody@dizum.com> wrote:
>>
>> In article
>> <e527ed2bdd4e9425930ca129b725cf89@msgid.frell.theremailer.net>
>> sci local <none@anonymous.net> wrote:
>> >
>> > > >
>> > > >The YAMN_Remailer_Client effort was just an experiment to see if
>> > > >it would work with the latest OmniMix release supporting yamn.
>> > > >It does (With the TLS adjustment) and there are no copy issues.
>> > >
>> > > Complex yet stable, that's how it has to be. :-)
>> >
>> > OmniMix is quite the sophisticated resource.
>>
>> I tried your change and it works great! Thanks! I can send out
>> locally via OmniMix SMTP now.
>
>Same here. Did not even consider doing that as OmniMix worked
>so well with the old QS.

May I ask why you use QS instead of a standard MUA/NUA or the integrated
Mailer?

On 10/22/2021 7:16 PM, Nomen Nescio wrote:

> In article <d40b7eb15474a6161a9eba0028a6cde0@dizum.com>
> Nomen Nescio <nobody@dizum.com> wrote:
>>
>> In article
>> <e527ed2bdd4e9425930ca129b725cf89@msgid.frell.theremailer.net>
>> sci local <none@anonymous.net> wrote:
>>>
>>>>>
>>>>> The YAMN_Remailer_Client effort was just an experiment to see if
>>>>> it would work with the latest OmniMix release supporting yamn.
>>>>> It does (With the TLS adjustment) and there are no copy issues.
>>>>
>>>> Complex yet stable, that's how it has to be. :-)
>>>
>>> OmniMix is quite the sophisticated resource.
>>
>> I tried your change and it works great! Thanks! I can send out
>> locally via OmniMix SMTP now.
>
> Same here. Did not even consider doing that as OmniMix worked
> so well with the old QS.
>

I must have missed this.

What was the change, what were the details of the change that should be
implemented in Omnimix?

In article
<51571286a4aec799623dae6304337fa3@remailer.paranoici.org>
Anonymous <nobody@remailer.paranoici.org> wrote:
>
> On 10/22/2021 7:16 PM, Nomen Nescio wrote:
>
> > In article <d40b7eb15474a6161a9eba0028a6cde0@dizum.com>
> > Nomen Nescio <nobody@dizum.com> wrote:
> >>
> >> In article
> >> <e527ed2bdd4e9425930ca129b725cf89@msgid.frell.theremailer.net>
> >> sci local <none@anonymous.net> wrote:
> >>>
> >>>>>
> >>>>> The YAMN_Remailer_Client effort was just an experiment to see if
> >>>>> it would work with the latest OmniMix release supporting yamn.
> >>>>> It does (With the TLS adjustment) and there are no copy issues.
> >>>>
> >>>> Complex yet stable, that's how it has to be. :-)
> >>>
> >>> OmniMix is quite the sophisticated resource.
> >>
> >> I tried your change and it works great! Thanks! I can send out
> >> locally via OmniMix SMTP now.
> >
> > Same here. Did not even consider doing that as OmniMix worked
> > so well with the old QS.
> >
>
> I must have missed this.
>
> What was the change, what were the details of the change that should be
> implemented in Omnimix?

OmniMix, Server tab, Mail Snd (SMTP), TLS disabled
vs TLS enabled.

That's it.

Permits sending posts from the yamn client and QSL via OmniMix
SMTP server using 127.0.0.1:25.

Doesn't affect external operation. I could not get this working
with QSL for the life of me until that tip showed up. Had given
up actually.

On 10/25/2021 6:41 PM, Anonymous Remailer (austria) wrote:

>> What was the change, what were the details of the change that should be
>> implemented in Omnimix?
>
> OmniMix, Server tab, Mail Snd (SMTP), TLS disabled
> vs TLS enabled.
>
> That's it.
>
> Permits sending posts from the yamn client and QSL via OmniMix
> SMTP server using 127.0.0.1:25.
>
> Doesn't affect external operation. I could not get this working
> with QSL for the life of me until that tip showed up. Had given
> up actually.
>

Thanks very much!