Pkg exim4 users - Mar 2007 - How to run a script before each queue run?

Hello,

this is not strictly Debian, but: 

Is there a way to run a script before each queue run or before the SMTP
transport connects to the smarthost?

Background info: I am using as smarthost the SMTP server of my ISP. They have
just changed the policies on their SMTP servers and now each time my exim
connects to the smarthost it gets a "550 Authorization required". This
is because now they require POP before SMTP authentication. Which is why I need
to run the script _before_ any of those two events (queue run or SMTP connect).

Any advice welcome.

Thanks
a.

On Saturday 10 March 2007 15:00, Eugen Melinte wrote:
> Background info: I am using as smarthost the SMTP server of my ISP. They
> have just changed the policies on their SMTP servers and now each time my
> exim connects to the smarthost it gets a "550 Authorization
required". This
> is because now they require POP before SMTP authentication. Which is why I
> need to run the script _before_ any of those two events (queue run or SMTP
> connect).
My first advice, if they don''t support SMTP AUTH, would be to bash them
really
hard about this. POP before SMTP is *so* 1990''s. (If they actually
already do
support SMTP AUTH you should of course use that instead.)

-- 
Magnus Holmgren        holmgren@lysator.liu.se
                       (No Cc of list mail needed, thanks)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/pkg-exim4-users/attachments/20070310/e9f6a72b/attachment.pgp

On Sat, Mar 10, 2007 at 02:00:14PM +0000, Eugen Melinte
wrote:
> Background info: I am using as smarthost the SMTP server of my ISP.
> They have just changed the policies on their SMTP servers and now each
> time my exim connects to the smarthost it gets a "550 Authorization
> required". This is because now they require POP before SMTP
> authentication. Which is why I need to run the script _before_ any of
> those two events (queue run or SMTP connect).
Find out the interval that your ISP allows you to relay after POP, and
then set up a cron job to POP every n-1 minutes. Then pester them to
finally support SMTP AUTH.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don''t trust Computers. They | Mailadresse
im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835

* on the Sat, Mar 10, 2007 at 02:00:14PM +0000, Eugen Melinte wrote:
> Is there a way to run a script before each queue run or before the
> SMTP transport connects to the smarthost?
> 
> Background info: I am using as smarthost the SMTP server of my ISP.
> They have just changed the policies on their SMTP servers and now
> each time my exim connects to the smarthost it gets a "550
> Authorization required". This is because now they require POP before
> SMTP authentication. Which is why I need to run the script _before_
> any of those two events (queue run or SMTP connect).
> 
> Any advice welcome.
You might be able to set up something like readsocket in a condition in
the router that passes the mail onto the smarthost (untested):

condition = ${if eq\
               {${readsocket\
                  {inet:your.isps.pop.host:110}\
                  {USER your.username\nPASS your.password\nQUIT\n}\
                  {30s}\
                  {}\
                  {}\
               }}\
               {}\
               {true}\
               {true}\
            }

If you''re using pop over SSL that becomes more of a problem.
I''d
probably use "openssl s_client" and ${run} for that. But if
you''re ISP is making you use POP before SMTP I doubt they''re
sophisticated enough for SSL.

Mike

>If you''re using pop over SSL that becomes more of a problem.
I''d
>probably use "openssl s_client" and ${run} for that. But if
>you''re ISP is making you use POP before SMTP I doubt
they''re
>sophisticated enough for SSL.

Thanks for the run suggestion :) I ended up hooking the perl script to the
transport with a headers_add = ${run{...}{}{}}

Regards
e.