inetd problems
in [General Linux]
|
Prev: Linux - retooling from the ground up, for Multicore systems
Next: Linux's Much Overlooked Calculator -- BC
From: Martin Sjoeberg on 22 Mar 2010 05:11 Hey guys, Hope to get some help here. I have a small linux-box running BusyBox for small home server use (samba, ftp, http, etc.). I'm currently trying to get SSMTP to work for relaying all mails sent to the home server to my ISPs smtp server. The box has no sendmail or any other mail software installed, but SSMTP. Ssmtp work fine from the commandline sending test mails through my ISP with no problems whatsoever. But, when I send mails to the box i get "ssmtp: No recipients supplied - mail will not be sent" - the exact same message, that ssmtp gives, if you try to run it from commandline with no recipients supplied. In inetd i have: ssmtp stream tcp nowait root /usr/sbin/ssmtp ssmtp .... and it seems that ssmtp is started, but never gets the mailstream (or whatever). What i can tell from the above is that: 1. ssmtp is correctly configured (it sends mails from command line) 2. i have no routing problems (i can connect to the server) 3. inetd starts ssmtp upon communication to the port (so its not a problem with wrong entry in /etc/services) 4. but somehow, inetd fails in delivering the stream to ssmtp. I am using port 52526 to connect to the home server, which then uses port 25 to send the mails through ISP: remote client --SMTP:52526--> home server --SMTP:25--> ISP Am I completely overlooking something? Regards, Martin --- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: The Natural Philosopher on 22 Mar 2010 05:40 Martin Sjoeberg wrote: > Hey guys, > > Hope to get some help here. > > I have a small linux-box running BusyBox for small home server use (samba, > ftp, http, etc.). I'm currently trying to get SSMTP to work for relaying all > mails sent to the home server to my ISPs smtp server. The box has no > sendmail or any other mail software installed, but SSMTP. Ssmtp work fine > from the commandline sending test mails through my ISP with no problems > whatsoever. But, when I send mails to the box i get "ssmtp: No recipients > supplied - mail will not be sent" - the exact same message, that ssmtp > gives, if you try to run it from commandline with no recipients supplied. In > inetd i have: > > ssmtp stream tcp nowait root /usr/sbin/ssmtp ssmtp > > ... and it seems that ssmtp is started, but never gets the mailstream (or > whatever). > > What i can tell from the above is that: > 1. ssmtp is correctly configured (it sends mails from command line) > 2. i have no routing problems (i can connect to the server) > 3. inetd starts ssmtp upon communication to the port (so its not a problem > with wrong entry in /etc/services) > 4. but somehow, inetd fails in delivering the stream to ssmtp. > > I am using port 52526 to connect to the home server, which then uses port 25 > to send the mails through ISP: > > remote client --SMTP:52526--> home server --SMTP:25--> ISP > > > Am I completely overlooking something? Yes. It cant recieve mails on a socket. "ssmtp is a send-only sendmail emulator for machines which normally pick their mail up from a centralized mailhub (via pop, imap, nfs mounts or other means)." If you want to use your server as a mail *relay*, you need something else. Exim IIRC is the easiest to set up for simple use. > > Regards, > > Martin > > > > > --- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: Martin Sjoeberg on 22 Mar 2010 06:11
(...) >> >> >> Am I completely overlooking something? > > Yes. It cant recieve mails on a socket. > > "ssmtp is a send-only sendmail emulator for machines which normally pick > their mail up from a centralized mailhub (via pop, imap, nfs mounts or > other means)." > > If you want to use your server as a mail *relay*, you need something else. > Exim IIRC is the easiest to set up for simple use. > Ah, thanks a lot! I totally overlooked that. I'll try Exim. --- news://freenews.netfront.net/ - complaints: news(a)netfront.net --- |