Remailers that do NOT require an fqdn

[Anne Onime]

If you send remailer messages via exim4 or one of the other
programs that do that sort of thing, rather than using the smtp
server of your isp; and if, for whatever reason, your pc does not
have a fully-qualified domain name (fqdn), then you will find your
messages being rejected if the first remailer in your chain is one
that requires an fqdn.

Most of the remailers do require it; however, there are at the
moment 8 that do not. If you make sure that one of them is the
first remailer in your chain, your message will be accepted.

Here is the list of remailers that do NOT require an fqdn:

'kulin','devurandom','kroken','cside','hermetix','pboxmix','starwar
s','eurovibes'

I can't see the need for the fqdn, but what do I know?

[Kulin Remailer]

Post by Anne Onime
If you send remailer messages via exim4 or one of the other
programs that do that sort of thing, rather than using the smtp
server of your isp; and if, for whatever reason, your pc does not
have a fully-qualified domain name (fqdn), then you will find your
messages being rejected if the first remailer in your chain is one
that requires an fqdn.
Most of the remailers do require it; however, there are at the
moment 8 that do not. If you make sure that one of them is the
first remailer in your chain, your message will be accepted.
'kulin','devurandom','kroken','cside','hermetix','pboxmix','starwar
s','eurovibes'
I can't see the need for the fqdn, but what do I know?

If you are able to, stick a "Sign-On: [example.net]" into the handshake.

[Anonymous]

Post by Kulin Remailer
If you are able to, stick a "Sign-On: [example.net]" into the handshake.

Sending a fake domain with HELO / EHLO also isn't guaranteed to work
if it doesn't resolve correctly due to a Tor exit connection. Or what
else did you mean?

[Dave U. Random]

Post by Anonymous

Post by Kulin Remailer
If you are able to, stick a "Sign-On: [example.net]" into the handshake.

Sending a fake domain with HELO / EHLO also isn't guaranteed to work
if it doesn't resolve correctly due to a Tor exit connection. Or what
else did you mean?

In the past it has worked for me for every remailer which required a fqdn,
though I made sure the domain wasn't "fake" but a real one, like
google.com. I never encountered one which matched an IP to the domain.
Things may have changed, however.

[Nomen Nescio]

Post by Dave U. Random

Post by Kulin Remailer
If you are able to, stick a "Sign-On: [example.net]" into the handshake.

Sending a fake domain with HELO / EHLO also isn't guaranteed to work if
it doesn't resolve correctly due to a Tor exit connection. Or what
else did you mean?

In the past it has worked for me for every remailer which required a
fqdn, though I made sure the domain wasn't "fake" but a real one, like
google.com. I never encountered one which matched an IP to the domain.
Things may have changed, however.

If I am sending a mixmaster message and the first remailer in the chain
is one that requeires an fqdn, can you tell me how I send a domain like
google.com with the 'HELO / EHLO', whatever that is?

Can you tell me with enough detail so that I can do it myself? If all you
have is a reference to some help page, I am afraid I will not be able to
understand it if past experience is a guide.

I kow how to send a mixmaster command from a terminal, or I can include
it in a python script, and I know how to change mix.cfg to include
whatever parameters are needed. Does what you are talking about apply to
sending messages to a remailer in that fashion?

If it does not, exactly what is it that you do when you send a message to
a remailer and send a domain like google.com with the 'HELO / EHLO'?

[Kulin Remailer]

Post by Nomen Nescio

Post by Dave U. Random

Post by Kulin Remailer
If you are able to, stick a "Sign-On: [example.net]" into the handshake.

Sending a fake domain with HELO / EHLO also isn't guaranteed to work if
it doesn't resolve correctly due to a Tor exit connection. Or what
else did you mean?

In the past it has worked for me for every remailer which required a
fqdn, though I made sure the domain wasn't "fake" but a real one, like
google.com. I never encountered one which matched an IP to the domain.
Things may have changed, however.

If I am sending a mixmaster message and the first remailer in the chain
is one that requeires an fqdn, can you tell me how I send a domain like
google.com with the 'HELO / EHLO', whatever that is?
Can you tell me with enough detail so that I can do it myself? If all you
have is a reference to some help page, I am afraid I will not be able to
understand it if past experience is a guide.
I kow how to send a mixmaster command from a terminal, or I can include
it in a python script, and I know how to change mix.cfg to include
whatever parameters are needed. Does what you are talking about apply to
sending messages to a remailer in that fashion?

No it does not, for I am a mere Windows user using QS/QSL and *poof* it
just does it for me.

Post by Nomen Nescio
If it does not, exactly what is it that you do when you send a message to
a remailer and send a domain like google.com with the 'HELO / EHLO'?

Fcc: outbox
Host: requires.fqdn.com
Sign-On: google.com
From: ***@google.com
Chain: *,*,*; copies=3;
To: You
Subject: None

[Nomen Nescio]

Post by Dave U. Random
In the past it has worked for me for every remailer which required a fqdn,
though I made sure the domain wasn't "fake" but a real one, like
google.com. I never encountered one which matched an IP to the domain.
Things may have changed, however.

SMTP Error: 95.111.134.38 is not yet authorized to deliver mail from
<***@google.com> to <***@eurovibes.org>. Please try later.: 250
- Reset OK

[Anonymous Remailer (austria)]

Post by Dave U. Random

Post by Anonymous

Post by Kulin Remailer
If you are able to, stick a "Sign-On: [example.net]" into the handshake.

Sending a fake domain with HELO / EHLO also isn't guaranteed to work
if it doesn't resolve correctly due to a Tor exit connection. Or what
else did you mean?

In the past it has worked for me for every remailer which required a fqdn,
though I made sure the domain wasn't "fake" but a real one, like
google.com. I never encountered one which matched an IP to the domain.
Things may have changed, however.

An OmniMix protocol where the sender's (German austingrub Tor exit) IP
was blocked:

Envelope From: Invalid <***@google.com>
HELO ID: google.com

| 0 SMTP State: Chunks remaining: 1 for direct delivery, 2 of 5 in total
| 0 SMTP State: Trying server 'smtp-in-01.dizum.com', port 25 for '***@dizum.com' ...
| 0 SMTP State: 'From:' header 'Anon <***@domain.invalid>' replaced by 'Invalid <***@google.com>'
| 0 SMTP State: Connecting to 'smtp-in-01.dizum.com', port 25
| > SMTP SSL State: Connecting to 127.0.0.1.
| > SMTP State: Connected.
| 0 SMTP State: Connected to 'smtp-in-01.dizum.com', port 25
| 0 SMTP Greeting:
| 0 SMTP Protocol Capabilities: PIPELINING|SIZE 10240000|VRFY|ETRN|STARTTLS|ENHANCEDSTATUSCODES|8BITMIME|DSN
| 0 SMTP Encryption: TLS supported
| 0 SMTP State: Sending chunk 1 of 1 from 'Invalid <***@google.com>' to '***@dizum.com', server 'smtp-in-01.dizum.com', port 25 ...
| > SMTP SSL Status Info: SSL status: "before/connect initialization"
<SSL negotiation removed>
| > SMTP SSL Status Info: SSL status: "SSL negotiation finished successfully"
| > SMTP SSL Status Info: Cipher: name = DHE-RSA-AES256-SHA; description = DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1|; bits = 256; version = TLSv1/SSLv3;
| 0 SMTP Error: Service unavailable; Client host [93.104.215.8] blocked using xbl.spamhaus.org; http://www.spamhaus.org/query/bl?ip=93.104.215.8: 250 - Ok
| > SMTP State: Disconnecting.
| > SMTP Response: Bye
| > SMTP SSL Status Info: SSL status: "SSL negotiation finished successfully"
| > SMTP State: Disconnected.
| 0 SMTP State: Original 'From:' header 'Anon <***@domain.invalid>' restored
| 0 SMTP State: Sending directly to anon SMTP host failed

Nslookup result for 8.215.104.93.static.giga-dns.com querytype=A:
Name: 8.215.104.93.static.giga-dns.com
Address: 93.104.215.8

Pass 2 shows:

| 0 SMTP Error: Service unavailable; Client host [87.11.38.102] blocked using xbl.spamhaus.org; http://www.spamhaus.org/query/bl?ip=87.11.38.102: 250 - Ok

That's the Italian viroide Tor node.

Nevertheless more than half of my Mixmaster packets are delivered
directly.