🚀 go-pugleaf

 In article <829403796_OASIS_@phil4.demon.co.uk>
  phil4@phil4.demon.co.uk (Phil Hough) said:-

>thanks for this, the value was 20, which I indeed change to 1, and it 
>sped the process up no-end.... thanks !!!
>
>I don't understanf the difference between sending direct and 'through 
>the gateway' though !

When you send mail to the gateway it only goes onto a queue on one of 
demons machines. This is fast for you in connection time but means the 
email will have to wait its turn to get sent to the destination. 
Normally there is not much difference between it and direct in terms 
of when it is delivered (maybe hours instead of minutes). If there is 
a mail backlog though, or you want to ensure it gets there (as much as 
is possible) then you may want to send it direct.

Direct means Nos (or whatever) has to negotiate a connection with the 
destination directly. If it is a lot of hops (steps) away or there is 
a bottleneck somewhere it can take ages to send from your machine. 
However, once sent from your machine it will be available for the 
recipient almost immediately.

>One last question - what effect would changing the wait value to 0 
>have ???

Like me, you would guess it turns direct posting off but it does the 
opposite so you are stuck with 1.

There is another way to control the email delivery using the percent 
or pling hack. I never use it so I can't remember which does what. You 
can edit the .wrk file and change (for example) ...

guy@swampdog.demon.co.uk

to

guy%swampdog.demon.co.uk

or

guy!swampdog.demon.co.uk

Someone else will have to explain the details for these.

>Thanks for the help, now I don't have to dread sending huge emails...

Most of my emails are small enough to not bother me if I occasionally 
get a direct connection (sometimes you do with "smpt wait 1"). For the 
rare large email which sod's law says will get a direct connection, I 
find this method quicker than messing aroung with the .wrk files ...

You notice a direct connection - type "socket" ("so" for short) and 
look at the TCP connection. Note the TCP address then type ...

"tcp reset address"

which kills the direct post. It then goes on to the gateway.


__

Guy Harrison

guy@swampdog.demon.co.uk