>>On 19.04.12 23:36, Sam Varshavchik wrote: >>>What also needs to be done is also >>>to save which IP address each message was received from, and then use >>>that IP address in case that message ever goes out via SMTP again, in >>>addition to using an IP address-specific configuration.
>Matus UHLAR - fantomas writes: >>according to the apparent OP's reason, he apparently needs table for >>mapping source domains into source IPs. On 20.04.12 06:52, Sam Varshavchik wrote: >I can see the argument for this alternative. However, this means that >any party can set their return address, and end up with a message >that appears to have come from "their" server, leading to complaints >that "their" server has been "hacked". iiuc, users can do that already (set any fromaddress), and the sending IP is always the same with courier. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. One OS to rule them all, One OS to find them, One OS to bring them all and into darkness bind them ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
