| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 23 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 46:52:44 |
| Calls: | 583 |
| Files: | 1,138 |
| Messages: | 111,071 |
Some complete information on how to reply to an email on Usenet with Omnimix >With QSL clipboard > follow-up...with Omnimix?
OmniMix * Tutorial * Configuration * Client * Thunderbird * Mail[end quoted plain text]
To prepare Thunderbird for OmniMix mail interaction open the 'Account Settings'
window by selecting the menu 'Tools' > 'Account Settings' with Windows and OS X
or 'Edit' > 'Account Settings' with Linux.
Add a new account by clicking on 'Account Actions'.
From the menu select the 'Add Mail Account ...' item.
Enter an alias and an invalid email address into the appropriate fields as well
as 'omnimix' for your OmniMix password, check 'Remember password' and click 'Next'.
Now Thunderbirds tries to figure out mail server parameters for your mail >address, which has to fail, as the address is invalid. Select 'POP3' for incoming
mail, then for Incoming and Outgoing specify 'localhost' as the Server hostname
and enter 'omnimix' into the Username field. Click the 'Re-test' button. >Thunderbird contacts the OmniMix POP3 and SMTP server and finally shows the >connection parameters it learned, which are port 110 for POP3, port 25 for SMTP,
both with STARTTLS and normal password transmission. Click 'Done'.
As in default configuration the OmniMix servers use a self-signed certificate >you'll get a warning. With 'Permanently store this exception' checked click >'Confirm Security Exception'.
In the 'Accounts Settings' window select 'Outgoing Server (SMTP)', click 'Edit'
and enter a Description,
which reminds you of this account's message routing.
Select the POP3 account of your alias ('john.doe@anon.invalid') to review the >data you've entered.
Finally configure its Server Settings, e.g. deactivate automatic checks for new
messages.
Mail message retrieval (context menu 'Get Messages' of your POP3 account) either
bases on the POP3 configuration within OmniMix, or you use the 'Extended Username
Syntax' to transfer the retrieval rules while Thunderbird connects with OmniMix.
If applicable enter your extended username into the 'User Name' field. >Finally click 'Ok' to finish configuration.
Now it's time to send your first anonymous mail message through OmniMix. >Select 'Message' > 'Mail Mesage' from Thunderbird's menu to open a 'Write:' >window, enter a 'To' destination address (for testing preferably an invalid one),
a Subject and Body Text, then click 'Send'.
Thunderbird asks for your OmniMix account's password, which defaults to 'omnimix'.
Once again Thunderbird may find fault with your self-signed OmniMix certificate.
Click 'Confirm Security Exception' with 'Permanently store this exception' checked.
Thunderbird transfers your mail to OmniMix, then waits for a reply, which may >take a few minutes, as OmniMix first has to forward the message to the Internet.
If OmniMix interaction fails due to a connection timeout you have to extend >Thunderbird's respective timeout interval, which unfortunately only can be done
with its Config Editor.
Select the 'Tools' > 'Options' menu, in 'Advanced' > 'General' click the 'Config
Editor' button.
A window with a warning opens, confirm your intentions.
Locate the 'mailnews.tcptimeout' parameter by entering that text into the search
field, from the line's context menu select 'Modify'.
A time interval of 1000 seconds (more than 15 minutes) should usually suffice >for OmniMix to get message processing done. Click 'Ok'.
Close the Config Editor, then retry to send the message.
PreviousTopNext
Some complete information on how to reply to an email on Usenet with Omnimix >With QSL clipboard > follow-up...with Omnimix?
OmniMix * Tutorial * Remailing * Scanning Different Mailboxes[end quoted plain text]
OmniMix offers you to define one incoming mail (POP3) account within the >program. If you need to collect mail from several mailboxes, the parameters for
the single POP3 hosts have to be transmitted with the authentication data. At the
side of your mail client you integrate them into the OmniMix username by using >the 'extended' syntax. Here's a list of the supported parameters:
ht (Host) IP address or URL of the external server
pt (Port) Port number of the external server
un (Username) Username to access the external server
pw (Password) Password to access the external server
au (Authentication) Method to transmit login credentials:
'u' Unencrypted plaintext transmission of username and password
'a' APOP challenge/response protocol using a hash function
's' SASL Simple Authentication and Security Layer framework
pl (Polling) Switch whether the POP3 and/or nym related NNTP server has
to be polled:
't' No external server connection - only for testing
'p/P' POP3 server polling (if accessible / mandatory)
'n/N' Polling of the nym related NNTP server (if accessible /
mandatory)
So a value of 'Pn' would mean no error message, if the news
server isn't available
tl (TLS) Necessity of a TLS encrypted server connection:
d Disabled - no TLS-secured connection
e Enabled - TLS-secured connection if offered by the server
r Required - no data exchange without encryption
i Implicit - implicit SSL
to (Tor) Usage of Tor to communicate with the server:
n Disabled - normal connection
4 Connection through Tor using SOCKS version 4
4a Connection through Tor using SOCKS version 4a
(accepts host name)
5 Connection through Tor using SOCKS version 5
(accepts either the host's IP address or host name)
Thus a username string including all server access data looks like >username;ht=mail.my_isp.com;pt=110;un=my_alias;pw=my_pwd;ap=y;pl=P;tl=e;to=n >Apart from the username and password any parameter which isn't defined is >replaced by the internal OmniMix setting. This may be relevant especially if the
'Username' field within the client application doesn't provide enough space for
all parameters (usually about 80 characters), so that at least the assignment of
a standard port number like '110' for POP3 can be left undone.
If the extended username syntax is activated ('Ext.S' at the 'Server' tab), and
you transmit an extended username (indicated by a ';' somewhere in that name), >all separator characters (';') within the username itself or a parameter have to
be preceded by an asterisk '*' (as well as an asterisk itself of course)!
So OmniMix user 'john', who has to fetch messages for his nyms, sent to a >newsgroup, as well as mail from 'pop3.yahoo.com' (port 110, username >'eagle@yahoo.com', password 'eagle;pwd') using the predefined TLS and Tor >settings has to authenticate with the username >john;ht=pop3.yahoo.com;pt=110;un=eagle@yahoo.com;pw=eagle*;pwd;pl=PN
whereas if he only intends to pick up his nym messages from the corresponding >newsgroups
john;pl=N
would suffice.
The extended username syntax isn't limited to the POP3 server. The NNTP server >is able to handle those parameters as well, though of course 'ap' (authentication
schemes) and 'pl' (polling) aren't relevant in that case.
For example your news client logged into OmniMix with the extended username >john;ht=ruxuklsvo4pk74m5.onion;pt=119;tl=r;to=4a
gets anonymously connected with the Mixmin news server's Hidden Service. >PreviousTopNext
Some complete information on how to reply to an email on Usenet with Omnimix
With QSL clipboard > follow-up...with Omnimix?