assp have information about IP of connecting party. MTA has
information about used smtp auth username (assp can't have it because
it is combined with password with AUTH-PLAIN). In result assp and mta
does not have IP+username. There are antispam techniques that require
both of them (like geo ip scanning + user preferences and
notifications).
I suggest an option to pass IP to mta. I think HELO is good for it
(mta does not verify it behind assp)
--- assp_oryg.pl 2012-11-12 18:25:00.000000000 +0100
+++ assp.pl 2012-11-13 01:30:33.000000000 +0100
@@ -12277,8 +12277,9 @@
$prot = 'E' . $prot if lc($this->{greeting}) eq 'ehlo';
$this->{rcvd} =~ s/\*SMTP\*/$prot/o;
$this->{rcvd} = &headerWrap( $this->{rcvd} ); # wrap long lines
- $l = "$this->{greeting} $localhostname\r\n" if $myHelo == 2
&& $localhostname;
- $l = "$this->{greeting} $myName\r\n" if $myHelo && ($myHelo
== 1 or !$localhostname);
+# $l = "$this->{greeting} $localhostname\r\n" if $myHelo == 2
&& $localhostname;
+# $l = "$this->{greeting} $myName\r\n" if $myHelo && ($myHelo
== 1 or !$localhostname);
+ $l = "$this->{greeting} $this->{ip}\r\n";
} elsif ( $CanUseIOSocketSSL &&
!$this->{SSLnotOK} &&
Can somebody could make this into mainstream code (of course this
would be under another $myHelo state)
Dissadvantage of this is that reciving party of that email sees sender
IP in recived heavers. But oh well. Many servers put it anyway in
custom headers.
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user