> Sorry to disagree, but in case of malicious code this doesn't help me > much. Any header field can be faked.
Your script has to connect to xmail CTRL interface and check with userlist <domain> <username> if the account is local. then you can be sure of it. > And that is exactly what I intend to do. After a local mail user > agent handed over the message to XMail, it should be passed on to my > script verifying the validity (again, I will have to deal with this > very carefully) and signing the message body. Then the message will > get delivered via SMTP. yes, see above. ;-) > I do similar things with incoming messages, as stated before. And if > I understood the docs 'Custom domain mail processing' (Part 10) lets > me do everything I need, except modify the message body. :-( custom domain processing will not work, if the domain is registered in your xmail server as local domain. it only works if the domain is NOT local-handled by your xmail server. there is no special bypass possibility for local domain handling, but davide told that he thinks about a new layer into xmail to to such things. > So I need 'Domain message filters' (Part 13, you see, I _know_ the > docs ;-) ) in the reversed direction. yes, we call it outgoing filters, it's requested often, maybe davide thinks about that feature, again. > Excuse me if I am insisting, but can anyone tell me: can I modify > outgoing mail message bodies (from my users to domains not handled by > my server) or not ? if the message should only be signed if the outgoing adress is outside your xmail server, your script/program has to check that per xmail ctrl interface, too. > Thanks for your patience no problem .. - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
