+My system is running under Linux SuSE 7.1 with firewall, masquerading
+and ISDN-dial-up connection (nothing of that will be described
+below). It was a quite lot of work to get all
+components accordingly running for doing the job they are intended to
+do.
+
+
+First of all, lets have a look at the big picture -- the real thing
+and my requirements are:
+
+
+
I have several E-Mail accounts at different providers with different
+access behaviours.
+
+
I am a subscriber of multiple mailing-list and want
+to sort this traffic out of common E-Mailing.
+
+
I want to assure only using oneMail-User-Agent
+ during daily work, managing all different mail-accounts.
+
+
I want to use a MUA doing some PGP-stuff automatically.
+
+
+In short, I want to receive mails from different E-Mail providers,
+manage the mail within one application and send out mails via
+different providers. Especially the last point is under LINUX a
+big obstacle, because of being a native server system it seems to be
+no way to go outside with different faces.
+
+Solving this leads me towards the following bunch of applications
+building my working environment:
+
+
+
+First of all you have to enable SMTP-transfers via port 25
+from inside to outside (set up your firewall-rules
+accordingly). Second, you can write your E-Mails within mutt, send them
+and they will be queued. Third, you run
+
+sendmail -g -qo all
+
+And you have sent all of your mails and received all waiting mail from
+your provider.
+
+
+
+Georg Lohrer
+2001-03-23
+
+
+
+
diff -r b95795affb63 -r a8c310973cbe docs/georg-lohrer_handlingmasqmail/node2.html
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/georg-lohrer_handlingmasqmail/node2.html Thu Sep 18 18:57:52 2008 +0200
@@ -0,0 +1,76 @@
+
+
+
+
+
+
+How to setup MasqMail
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Next:masqmail.conf
+ Up:Receiving and sending mails
+ Previous:Receiving and sending mails
+
+
+
+
+
+MasqMail has to be compiled and installed in a proper way. If
+you need authorization support, configure with
+-enable-auth.
+For continuing running already available scripts of sendmail you
+could set a sym-link after installation:
+
+Especially the map commands need a closer look. These lines
+map local parts of the given address towards a full RFC 822 compliant
+email address. map_return_path_addresses does this for the
+passed Return address, map_h_from_addresses for the given
+From part.
+
+But, pay attention! As you can see the strange name gmx_foo in
+front of both items has never been seen until now. And in
+allowed_mail_locals you see the same item. What about this?
+
+An E-Mail will be passed towards the E-Mail provider giving a so
+called envelope. This construction envelopes the real E-Mail
+and passes important things like the address of the sender and the
+address of the receiver to the E-Mail provider. These envelope date
+will never be seen again on the receiver's site, because the MTA
+running on receiver's host will delete them. But only the envelope is
+valid for any MTA distinguishing the route towards the receiver. So,
+it must be a valid address.
+
+Per default MasqMail uses the current user-name as
+Envelope-From:. If we want to use different E-Mail accounts
+with mapping of addresses via the above shown map_return_path_addresses and
+map_h_from_addresses we have to to mutilate the envelope
+data! That could be done very easily within mutt.
+
+
+ Next:masqmail/web_foo.route
+ Up:Receiving and sending mails
+ Previous:masqmail.conf
+
+
+Georg Lohrer
+2001-03-23
+
+
+
+
diff -r b95795affb63 -r a8c310973cbe docs/georg-lohrer_handlingmasqmail/node5.html
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/georg-lohrer_handlingmasqmail/node5.html Thu Sep 18 18:57:52 2008 +0200
@@ -0,0 +1,56 @@
+
+
+
+
+
+
+masqmail/web_foo.route
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Next:masqmail/gmx_foo.get
+ Up:Receiving and sending mails
+ Previous:masqmail/gmx_foo.route
+
+
+
+
+