[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
howtos:misc:proxying_smpt [2015/11/27 23:54 (UTC)] – [Scenario 2] louigi600howtos:misc:proxying_smtp [2016/06/20 07:28 (UTC)] (current) – proxying_smtp renamed to howtos:misc:proxying_smtp (Ended up in the wrong namespace) alienbob
Line 6: Line 6:
 Here are some scenarios with examples on how you could go about working around the problem. Here are some scenarios with examples on how you could go about working around the problem.
  
-Throughout the scenarios we will be referring so 3 machines:+Throughout the scenarios we will be referring to 3 machines:
  
   * Machine A with IP address 192.168.0.2 (cannot send mails directly via internet and cannot relay on Local Mail Relay)   * Machine A with IP address 192.168.0.2 (cannot send mails directly via internet and cannot relay on Local Mail Relay)
Line 74: Line 74:
   DATA   DATA
   354 End data with <CR><LF>.<CR><LF>   354 End data with <CR><LF>.<CR><LF>
-  FROM:drao@invallee.it +  FROM:me@localnet.com 
-  TO:drao@invallee.it+  TO:dude@localnet.com
   SUBJECT:test using ssh tunnel   SUBJECT:test using ssh tunnel
   if you get this sending email trough ssh tunnel worked   if you get this sending email trough ssh tunnel worked
Line 95: Line 95:
 We can then start the ssh socks proxy on Machine B listening on a port Machine A can access: We can then start the ssh socks proxy on Machine B listening on a port Machine A can access:
  
-On machine B+On machine B with a privileged user
   ssh -2 -D 192.168.1.2:1024 -N  192.168.2.2 &   ssh -2 -D 192.168.1.2:1024 -N  192.168.2.2 &
  
Line 109: Line 109:
   DATA   DATA
   354 End data with <CR><LF>.<CR><LF>   354 End data with <CR><LF>.<CR><LF>
-  FROM:drao@invallee.it +  FROM:me@localnet.com 
-  TO:drao@invallee.it+  TO:dude@localnet.com
   SUBJECT:test using ssh tunnel   SUBJECT:test using ssh tunnel
   if you get this sending email trough ssh tunnel worked   if you get this sending email trough ssh tunnel worked
Line 147: Line 147:
  
 ====== NOTES ====== ====== NOTES ======
-The command we used above is probably a good example of bad unixcraft, let me give a brief explanation on how it works.+The command we used in Scenario 1 is probably a good example of bad unixcraft, let me give a brief explanation on how it works.
 Let's momentarely get rid of the odd use of the fifo by just using this: Let's momentarely get rid of the odd use of the fifo by just using this:
  
Line 161: Line 161:
 so now the whole command line looks like this: so now the whole command line looks like this:
   cat /tmp/f | nc -l -p 1234 -s 192.168.1.2 | nc 192.168.2.2 25 >> /tmp/f   cat /tmp/f | nc -l -p 1234 -s 192.168.1.2 | nc 192.168.2.2 25 >> /tmp/f
-it is possible to do the same thing without having to use cat it is a little neater but still bad unixcraft+it is possible to do the same thing without having to use catit is a little neater but still bad unixcraft
   nc -l  -p 1234 -s 192.168.1.2 < /tmp/f |nc 192.168.2.2 25 >> /tmp/f   nc -l  -p 1234 -s 192.168.1.2 < /tmp/f |nc 192.168.2.2 25 >> /tmp/f
  
 howtos:misc:proxying_smtp ()