David Ecker wrote:
>
> When I telnet, send a mail or recieve a mail from a local computer on my
> lan to my linux server (Suse 5.3) running diald, the server connects to
> the internet.
> Example : telnet://192.168.1.1 (from 192.168.1.10)
>
> I dont't want diald to do that!!
In /etc/sendmail.cf,
# default delivery mode
O DeliveryMode=queueonly
There will be a delivery mode in there already; it'll probably be
'background', though my memory could be faulty.
'deferred' would set it to not try to send it right away, but it would
try to look up the mail exchange, which would cause a dialout.
queueonly has it not do a single thing with the message other than
queueing it, until it is time to process the queue. My queue is set to
2 hours. This will present a problem if your system takes longer to
dial up than sendmail will wait to try and resolve a host (my system
does this.) I fix this problem by killing and restarting sendmail in
/etc/ppp/ip-up. I *could* just do a sendmail -q, but if I have multiple
messages, the first one running may still be processing the queue, and
I'd rather not task the file locking.
> I found out that the message responsible for going online is accepted by
> the following rules :
>
> accept udp 30 udp.dest=udp.domain
> accept udp 30 udp.source=udp.domain
>
> Changing those to ignore doesn't solve the problem either. Http or
> ftp won't bring the line online anymore. I have to ping the outside to go
> online, but that isn't a solution.
>
> If somebody got an idea, please help :-)
Well, undo all the things you broke to fix the problem. They shouldn't
be broken... Then do the queueonly thing, as mentioned above.
Hint: when a program is causing diald to call your ISP more than you
want, tweak the offending program, not diald. Tweak diald only as a
last resort.
Ed
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
