There are a number of possibilities given the config snippet below. Jason wrote: > Set($SendmailArguments , "-oi -t -f support\@obscured.com");
Does [email protected] go into RT? -f sets the envelope-sender address which is where bounces go. If it goes into RT, that's potentially a mail loop. > Set($MaxAttachmentSize , 10000000); > > #Set($RTAddressRegexp , '(^rt\@obscured.com$)(.*\@obscured.co.za)'); > Set($RTAddressRegexp , '.*\@obscured.co.za'); The commented out $RTAddressRegexp (which I suppose is commented out because it didn't work; the regex syntax is incorrect) contains [email protected], but the uncommented version of the option doesn't match that. Does [email protected] still go into RT? If so, that could be the source of a loop if a ticket got a watcher of the rt@ address added. Try this instead: '^(rt@obscured\.com|.*@obscured\.co\.za)$' Escaping the @ isn't necessary in a single-quoted string, just double quoted to prevent interpolation. Additionally, the current $RTAddressRegexp should have the dots (.) in .co.za escaped with a backslash, though that's unlikely to cause a loop. > Set($CorrespondAddress , '[email protected]'); > Set($CommentAddress , '[email protected]'); These values are strange, since normally those addresses are intended to receive replies! However, they are unlikely to be a mail loop source since they will match your RTAddressRegexp. Thomas
