Hi,
Another approach that you could consider is using SASL for SMTP, and
let the SMTP server add a "X-Authenticated-User" header.
This way you now exactly what user that send an email, that way is
even more bulletproof for tracking abuse ( if an user group is behind
of NAT for example )
Roundcube already supports logging into SASL and Postifx + Dovecot
for SASL is a nice way to get this up and running.
Cheers
Anders
On Feb 25, 2006, at 18:51, sofar wrote:
Hi,
I operate roundcube on a larger server with possibly groing amount
of users - therefore I'd like to cover my back and have roundcube
add an X-Originating-ip header or something equal to outgoing
messages, in the same way that yahoo and hotmail do (actually gmail
doesn't do this and this is getting them blacklisted by spamcop all
the damn time).
Having the ability to add such a header will allow me better to
track abuse of my servers and would make roundcube more usable in
larger deployments. I'd appreciate it if this feature will be
considered ;^)
Auke
--
TDC Song
[EMAIL PROTECTED]
CDTT (Certified Duct Tape Technician)
"Light travels faster than sound, thats why some people appear bright
before they speak"
Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to
produce
bigger and better idiots. So far, the Universe is winning. - Rich Cook
