Exim4 + port forwarding
Kumar Appaiah
I have been using fetchmail + procmail + exim4 to handle my mail. I
have a setup by which certain messages are received by procmail, and a
copy of some is forwarded to another address automatically.
Now, recently, due to excessive spread of viruses on the network due
to a popular but highly vulnerable mail client on a popular but
vulnerable OS (need I say more ;-), port 25 requests have ben blocked
for good! That means, exim can't forward my messages anymore.
Now, I have access through SSH to a machine close to my SMTP server,
so I have managed to get sending work using port forwarding and
esmtp. However, if I try to tell exim to relay mail to a smarthost on
my own computer (on a port different from 25, of course), exim
complains that it won't send the messages to the same machine. How do
I tell exim4 that I am actually sending the mail to a different
computer through a port, and not trying to cheat it?
Thanks.
Kumar
--
Kumar Appaiah,
462, Jamuna Hostel,
Indian Institute of Technology Madras,
Chennai - 600 036
James Vahn
> Dear list,
> I have been using fetchmail + procmail + exim4 to handle my mail. I
> have a setup by which certain messages are received by procmail, and a
> copy of some is forwarded to another address automatically.
>
> Now, recently, due to excessive spread of viruses on the network due
> to a popular but highly vulnerable mail client on a popular but
> vulnerable OS (need I say more ;-), port 25 requests have ben blocked
> for good! That means, exim can't forward my messages anymore.
By this I think you are saying that exim on localhost is connecting
to other servers directly instead of using a "smart host" - your ISP.
Relay your forwarded messages through him.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Kumar Appaiah
> Kumar Appaiah wrote:
> > Dear list,
> > I have been using fetchmail + procmail + exim4 to handle my mail. I
> > have a setup by which certain messages are received by procmail, and a
> > copy of some is forwarded to another address automatically.
> >
> > Now, recently, due to excessive spread of viruses on the network due
> > to a popular but highly vulnerable mail client on a popular but
> > vulnerable OS (need I say more ;-), port 25 requests have ben blocked
> > for good! That means, exim can't forward my messages anymore.
>
> By this I think you are saying that exim on localhost is connecting
> to other servers directly instead of using a "smart host" - your ISP.
> Relay your forwarded messages through him.
No, let me make it clear.
The problem is that all my requests to the smarthost's port 25 are
blocked. So, I try to ssh to another computer, forward the port 25 of
that SMTP server to port 10025 on my computer, and tell exim to use
localhost and port 10025 as the smart host; but exim refuses to
relay the mail through localhost, though it is actually a forwarded
port.
Any suggestion?
Laurent CARON
why not relaying directly to port 10025 of your other server?
--
Vos évangiles, vos bibles, vos corans, vos torahs, vos talmuds, vos
puranas, vos avestas, vos tantras, ne sont qu'un ramassis de conneries
et de mensonges qui font passer les aventures de Oui-Oui pour des
chefs-d'oeuvre.
-+- Philippe Charon -+-
Kumar Appaiah
> Kumar Appaiah a écrit :
> >The problem is that all my requests to the smarthost's port 25 are
> >blocked. So, I try to ssh to another computer, forward the port 25 of
> >that SMTP server to port 10025 on my computer, and tell exim to use
> >localhost and port 10025 as the smart host; but exim refuses to
> >relay the mail through localhost, though it is actually a forwarded
> >port.
>
>
Because there is no SMTP server running there! The server runs SMTP on
port 25, which is blocked, and I have a connection to that port 25
through my machine's 10025 port.
Steve Lamb
> Because there is no SMTP server running there! The server runs SMTP on
> port 25, which is blocked, and I have a connection to that port 25
> through my machine's 10025 port.
Do you control that other machine? What is preventing you from opening up
another port for Exim (presuming it is running Exim) to listen to?
--
Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
PGP Key: 8B6E99C5 | main connection to the switchboard of souls.
-------------------------------+---------------------------------------------
James Vahn
> The problem is that all my requests to the smarthost's port 25 are
> blocked.
Meaning that this command does not produce a response?
telnet smarthost 25
"smarthost" being something like "mail.isp.com" or (better) their IP
address. Will they give you an MX address? Become your own "smarthost"
and deliver directly, a leaf off of their domain.
> So, I try to ssh to another computer, forward the port 25 of that SMTP
> server to port 10025 on my computer, and tell exim to use localhost and
> port 10025 as the smart host; but exim refuses to relay the mail
> through localhost, though it is actually a forwarded port.
No no.. don't do that. I think you really want to forward 25 on yours to
25 on the other. What you have done is make your computer act as their
server, and probably nothing is listening... Use telnet on 25 to see.
You'd be better off using it as a smarthost. If you forward the port,
where would mail sent to root@localhost on both machines go? ;-)
Kumar Appaiah
> Kumar Appaiah wrote:
> > Because there is no SMTP server running there! The server runs SMTP on
> > port 25, which is blocked, and I have a connection to that port 25
> > through my machine's 10025 port.
>
> Do you control that other machine? What is preventing you from opening up
> another port for Exim (presuming it is running Exim) to listen to?
1.I do not control the other machine.
2.How would making exim4 on my machine listen on another port help? It
still doesn't want me to send relay messages to localhost (another
port).
Kumar Appaiah
> Kumar Appaiah wrote:
> > The problem is that all my requests to the smarthost's port 25 are
> > blocked.
>
> Meaning that this command does not produce a response?
>
> telnet smarthost 25
Exactly. But I have ssh access to another computer, where it does give
a response. So, I have forwarded mail.isp.com:25 using ssh to
localhost:10025.
> "smarthost" being something like "mail.isp.com" or (better) their IP
> address. Will they give you an MX address? Become your own "smarthost"
> and deliver directly, a leaf off of their domain.
Out of the question. I am behind a firewall which lets me do internal
ssh, and browse the 'net and do FTP via proxy.
> > So, I try to ssh to another computer, forward the port 25 of that SMTP
> > server to port 10025 on my computer, and tell exim to use localhost and
> > port 10025 as the smart host; but exim refuses to relay the mail
> > through localhost, though it is actually a forwarded port.
>
> No no.. don't do that. I think you really want to forward 25 on yours to
> 25 on the other. What you have done is make your computer act as their
> server, and probably nothing is listening... Use telnet on 25 to see.
No! I have got mail.isp.com:25 to localhost:10025. So, *my* machine
has their mail server on port 10025. Now, all I want exim4 to do is
use localhost:10025 as the smart host, but it frowns at the word
*localhost*!
Thanks for patiently anwering my query, hope it's clear now. Now, can
you think of a solution?
Thanks again.
Steve Lamb
> Thanks for patiently anwering my query, hope it's clear now. Now, can
> you think of a solution?
How attached are you to Exim? Personally when it comes to smarthost
relaying I found nullmailer to be a much better alternative. Smaller,
specially designed to forward to a smart host, capable of handling different
ports and might just be willing to mail to the local machine.
Steve Lamb
> On Wed, Sep 07, 2005 at 07:08:01PM -0700, Steve Lamb wrote:
>> Do you control that other machine? What is preventing you from opening up
>>another port for Exim (presuming it is running Exim) to listen to?
> 1.I do not control the other machine.
> 2.How would making exim4 on my machine listen on another port help? It
> still doesn't want me to send relay messages to localhost (another
> port).
The second statement was a continuation of the first. IE, "If you control
the remote machine what is preventing you from opening up another port for
Exim?" I had the same problem and for a time configured Exim to listen to
port 2525 as well as 25. But I controlled the remote machine and was able to
do so.
Steve Lamb
> Meaning that this command does not produce a response?
James, you're way off base. Look, his ISP has blocked him from outbound
port 25 connections. He did not every connect to his ISP's SMTP server. He
does not want to connect to his ISP's SMTP server. He wants to connect to
*his remote SMTP server* and is now blocked on port 25 from doing so. Telling
him to use his ISP's server is not the answer.
Roel Schroeven
> On Wed, Sep 07, 2005 at 06:33:28AM -0700, James Vahn wrote:
>
>>Kumar Appaiah wrote:
>>
>>>Dear list,
>>>I have been using fetchmail + procmail + exim4 to handle my mail. I
>>>have a setup by which certain messages are received by procmail, and a
>>>copy of some is forwarded to another address automatically.
>>>
>>>Now, recently, due to excessive spread of viruses on the network due
>>>to a popular but highly vulnerable mail client on a popular but
>>>vulnerable OS (need I say more ;-), port 25 requests have ben blocked
>>>for good! That means, exim can't forward my messages anymore.
>>
>>By this I think you are saying that exim on localhost is connecting
>>to other servers directly instead of using a "smart host" - your ISP.
>>Relay your forwarded messages through him.
>
>
> No, let me make it clear.
>
> The problem is that all my requests to the smarthost's port 25 are
> blocked. So, I try to ssh to another computer, forward the port 25 of
> that SMTP server to port 10025 on my computer, and tell exim to use
> localhost and port 10025 as the smart host; but exim refuses to
> relay the mail through localhost, though it is actually a forwarded
> port.
The computer you ssh to is not blocked by the smarthost, I presume?
There's something strange in your explanation, and I'm not sure if it is
because I misunderstand you or because you did something wrong. You
should forward the SMTP's port to your computer, it should be the other
way around: forward port 10025 on your computer to port 25 on the SMTP
server:
ssh user@sshhost -L 10025:smarthost:25
--
If I have been able to see further, it was only because I stood
on the shoulders of giants. -- Isaac Newton
Roel Schroeven
Roel Schroeven
> On Wed, Sep 07, 2005 at 06:33:28AM -0700, James Vahn wrote:
>
>>Kumar Appaiah wrote:
>>
>>>Dear list,
>>>I have been using fetchmail + procmail + exim4 to handle my mail. I
>>>have a setup by which certain messages are received by procmail, and a
>>>copy of some is forwarded to another address automatically.
>>>
>>>Now, recently, due to excessive spread of viruses on the network due
>>>to a popular but highly vulnerable mail client on a popular but
>>>vulnerable OS (need I say more ;-), port 25 requests have ben blocked
>>>for good! That means, exim can't forward my messages anymore.
>>
>>By this I think you are saying that exim on localhost is connecting
>>to other servers directly instead of using a "smart host" - your ISP.
>>Relay your forwarded messages through him.
>
>
> No, let me make it clear.
>
> The problem is that all my requests to the smarthost's port 25 are
> blocked. So, I try to ssh to another computer, forward the port 25 of
> that SMTP server to port 10025 on my computer, and tell exim to use
> localhost and port 10025 as the smart host; but exim refuses to
> relay the mail through localhost, though it is actually a forwarded
> port.
Can you connect to port 25 or 10025 on that remote computer you ssh to?
If so, you can use that as smarthost in exim and instruct that computer
to forward to the SMTP-server.
--
If I have been able to see further, it was only because I stood
on the shoulders of giants. -- Isaac Newton
Roel Schroeven
Kumar Appaiah
This is exactly what I am doing. Sorry if I didn't state it properly.
Now, how do I tell exim4 to relay my mail through localhost:10025?
James Vahn
> On Wed, Sep 07, 2005 at 06:54:38PM -0700, James Vahn wrote:
>> Meaning that this command does not produce a response?
>
> Exactly.
So what happens if you run exim on another port, and then do your port
forwarding on that very same computer?
e-mail>25>100025>smarthost
Roel Schroeven
OK, sorry, I misunderstood.
In that case, I can't help you other that with my other suggestion:
configure exim to use the other computer as smarthost, if you can find a
port that's not filtered by the firewall, and forward from there to port
25 on the real smarthost.
sa...@speakeasy.net
into what seems to be a common problem, but can find no pointer to the
solution. How can I tell the kernel that I want "/dev/hdc=ide-scsi"? Or,
better yet, can I upgrade from 2.4 to a fairly late 2.6 without installing
the distro again? If so, how?
Sam
anoop aryal
> I am running Sarge, linux 2.4.27, and grub with a NEC cdrom. I have run
> into what seems to be a common problem, but can find no pointer to the
> solution. How can I tell the kernel that I want "/dev/hdc=ide-scsi"? Or,
> better yet, can I upgrade from 2.4 to a fairly late 2.6 without installing
> the distro again? If so, how?
>
> Sam
(replace 'aptitude' with 'apt-get' below if you use 'apt-get' instead of
'aptitude').
aptitude install kernel-image-2.6-686
should do the trick.
--
M-L
>----> I am running Sarge, linux 2.4.27, and grub with a NEC cdrom. I have
> run ----> into what seems to be a common problem, but can find no pointer
> to the ----> solution. How can I tell the kernel that I want
> "/dev/hdc=ide-scsi"? Or, ----> better yet, can I upgrade from 2.4 to a
> fairly late 2.6 without installing ----> the distro again? If so, how?
>---->
>----> Sam
>---->
>---->
Heres my /boot/grub/menu.lst entry:-
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda5 ro apic=off vga=788
hdc=ide-scsi acpi
But I installed the system with these directions. Don't know if it can be
added later. Won't hurt if you try, just check dmesg if you can't read it
while booting this?
HTH
--
Registered Linux User:- 329524
+++++++++++++++++++++++++++++++++++
Men are born to succeed, not to fail. .............................Henry David
Thoreau
***********************************************
Debian Sarge 3.1.......... loving it
___________________________________________________________
Shawn Lamson
M-L <rose...@bigpond.com> wrote:
> On Thu, 9 Feb 2006 10:56 am, sa...@speakeasy.net thought about and sent this:
> >----> I am running Sarge, linux 2.4.27, and grub with a NEC cdrom. I have
> > run ----> into what seems to be a common problem, but can find no pointer
> > to the ----> solution. How can I tell the kernel that I want
> > "/dev/hdc=ide-scsi"? Or, ----> better yet, can I upgrade from 2.4 to a
> > fairly late 2.6 without installing ----> the distro again? If so, how?
> >---->
> >----> Sam
> >---->
> >---->
>
> Heres my /boot/grub/menu.lst entry:-
>
> kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda5 ro apic=off vga=788
> hdc=ide-scsi acpi
>
> But I installed the system with these directions. Don't know if it can be
> added later. Won't hurt if you try, just check dmesg if you can't read it
> while booting this?
it can definitely be added later, of course you must boot up with that there, it is called a kernel parameter. If you update to a 2.6 kernel though it probably won't do what you want, if dvd/cd writing is what you want... you will probably be in the position of putting ATAPI in front of your drive spec in cd writing apps or using a modified x-cdroast app... for example I now do #cdrdao --device ATAPI:0,0 to indicate my non-scsi cdrom device when writing a cd, again this is with the 2.6 kernels, and no hdc=ide-scsi is needed.
>
> HTH
>
----------
Shawn Lamson
sl...@optonline.net
Sam Rosenfeld
I recently replaced the Linux 2.4-27 kernel with a 2.6-8. Now I cannot
get my system to run X (and incidentally my mouse). To run X
I am using a very simple "startx", which calls XFree86, which, in turn,
relies on XF86Config-4. The config file is the same file I have used for
quite a while. The errors I see reported in /var/log/ indicate that
"display 0.0" must be run first.
I would appreciate any tips for debugging this problem.
Thanks,
s.
Hugo Vanwoerkom
> I recently replaced the Linux 2.4-27 kernel with a 2.6-8. Now I cannot
> get my system to run X (and incidentally my mouse). To run X
> I am using a very simple "startx", which calls XFree86, which, in turn,
> relies on XF86Config-4. The config file is the same file I have used for
> quite a while. The errors I see reported in /var/log/ indicate that
> "display 0.0" must be run first.
>
> I would appreciate any tips for debugging this problem.
>
> Thanks,
>
> s.
>
>
What is the exact error message?