Re: [cobalt-users] IMAP & POP before SMTP? (Raq XTR)

["Zeffie" <cobaltlist@xxxxxxxx>]

> On Sunday 16 November 2003 16:29, Zeffie wrote:
> > > On Sunday 16 November 2003 13:15, Zeffie wrote:
> > > > > To quote from the poprelayd program:
> > > > > <quote>
> > > > <snip>
> > > > > </quote>
> > > > > It should be doing IMAP already in addition to POP, but what might
be
> > > > > happening is that your IMAP clients are "staying" connected longer
> > > > > the 30 minutes or whatever you have the "relay" time set for
> > > > > Larry Smith
> > > > Nope...
> > > > It's a little broke on the XTR...
> > > > While it can be fixed,  I'm not the person that should be doing it
> > > > publicly...
> > > No problem, if someone with an XTR will send me all the poprelayd*
files
> > > (believe they are in /usr/local/sbin), I will look at fixing it and
> >> posting
> > > it somewhere "public".
> > > Larry Smith
> >
> > When I said "I'm not the person that should be doing it" I didn't mean
> > "somebody that has never worked on the problem"  Larry I would be happy
to
> > release the version I have already built for this but it's really Suns
job
> > to do this... They already know about this issue and they need to
provide
> > an update to fix it...  I wouldn't want my work to get in the way, delay
or
> > break any future updates by Sun...  I only use this with my customers
that
> > I do all the updates for.
> >
> > As you are not aware of the issue I would suggest your time might be
better
> > spent proding Sun to make the needed update...  they already have it,
They
> > just need to do it.
> Appreciate the comments, and understand your position, but poprelayd is
> nothing more than a perl program that "watches" the maillog for pop3 and
> imapd logins, extracts the appropriate IP address and adds it to the
sendmail
> (/etc/mail/popip.db) database to "let" sendmail know who is "allowed" to
> relay (eg who checked mail).
>
> If it is working for pop3 on the XTR, then poprelayd and its associated
> sendmail configuration is correct.  The problem is nothing more than it
> correctly recognizing the imapd logins (which I already fixed for the raq
> series several years ago and passed back to then Cobalt)....
> Larry Smith


ohhhh.. well why didn't you say so... Thats a horse of a different color!

This is the required change ... ie the cobalt patch...  Don't say I didn't
warn you and if you need support I don't provide free support anywhere but
here on this list...

--- poprelayd.orig      Tue Mar 19 14:19:57 2002
+++ poprelayd   Tue Mar 19 23:26:52 2002
@@ -185,7 +185,7 @@

     # imapd[11676]: Authenticated user=admin host=pyro.cobalt.com
[10.9.28.29]
     # ensure line ends at IP address.  Filter on rejected syntax.
-    if ($s =~ /(?:Authenticated|Login) user=\S+ host=\S+
\[([\d\.]+)\]\s*$/) {
+   if ($s =~ /(?:Authenticated|Login) user=\S+
host=(?:\S+ )*\[([\d\.]+)\]\s*$/) {
         my $authuser = $1;
         return $authuser unless ($s =~ /unknown command/i);
     }


Zeffie
Cobalt System Administration, Maintenance and Repairs. 734.454.9117
http://www.zeffie.com/ Home of the Worlds Largest Collection of RaQ rpms
Advanced Cobalt Security, Firewall, Snort, AntiSpam, AntiVirus and other
GUI's