Why are SRS announcements coming using the <> address as the sender? 
This is broken and needs fixed. The null-sender is a reserved 
special-case, and this ISN'T the special-case.

D


Jan 24 14:12:56 minbar sm-mta[18753]: g0OECupw018753: from=<>, 
size=835, class=0
, nrcpts=1, msgid=<[EMAIL PROTECTED]>, 
proto=ESMTP, da
emon=MTA, relay=smtp.tucows.com [216.40.39.50]
Jan 24 14:12:57 minbar sm-mta[18756]: g0OECupw018753: 
to=<[EMAIL PROTECTED]>, d
elay=00:00:01, xdelay=00:00:00, mailer=local, pri=30290, dsn=2.0.0, stat=Sent

>Return-Path: <MAILER-DAEMON>
>Received: from smtp.tucows.com (smtp.tucows.com [216.40.39.50])
>       by minbar.megacity.org (8.12.2/8.12.2/MegacityAntiSpam) with 
>ESMTP id g0OECupw018753
>       for <[EMAIL PROTECTED]>; Thu, 24 Jan 2002 14:12:56 GMT
>Received: from osrs1.opensrs.net ([129.33.169.22])
>       by smtp.tucows.com with esmtp (Exim 3.20 #3)
>       id 16TkcZ-0007H3-00; Thu, 24 Jan 2002 09:12:55 -0500
>Received: from localhost (popensrs@localhost)
>       by osrs1.opensrs.net (8.12.1/8.12.1/Debian -5) with SMTP id 
>g0OECK8r017760;
>       Thu, 24 Jan 2002 09:12:20 -0500
>Date: Thu, 24 Jan 2002 09:12:20 -0500
>Received: by osrs1.opensrs.net (bulk_mailer v1.13); Thu, 24 Jan 2002 
>09:10:23 -0500
>Subject: OpenSRS Live Reseller Update (.ca) 01/24/02
>Bcc:
>Message-ID: <[EMAIL PROTECTED]>
>X-UIDL: G[!"!i<9"!0kK"!n%V"!
>
>Greetings,
>
>Please find following an update on OpenSRS!
>
>1. Next TBR names window
>
>1. Next TBR names window
>
>The window for TBR names beginning with
>the letter 'a' commences at 9:20.
>
>CIRA is using:
>
>http://www.nrc.ca/inms/time/cesium.shtml
>
>to determine the time.
>
>Thanks,
>
>Ken


-- 
+---------------------+-----------------------------------------+
| [EMAIL PROTECTED]  | "Thou art the ruins of the noblest man  |
|  Derek J. Balling   |  That ever lived in the tide of times.  |
|                     |  Woe to the hand that shed this costly  |
|                     |  blood" - Julius Caesar Act 3, Scene 1  |
+---------------------+-----------------------------------------+

Reply via email to