On Thu Mar 26, 2009 at 09:14:32 -0400, John Peacock wrote:
> Historically, I have seen this behavior if the time between steps 4 and
> 5 was significant (for some value of significant). What was happening
> was that the sending MTA would timeout before the receiving MTA would
> send the 250.
Steve Kemp wrote:
This sequence can repeat multiple times though
I cannot seem to find why the RSET is being issued
by the client side. At each step my plugins are
returning the correct responses (e.g. "250 QUEUED"
after the DATA phase). Of course the MS-Exchange
admin believes their ser
On Fri, 20 Mar 2009 00:39:33 +
Steve Kemp wrote:
> +sub rset_respond {
> + my ($self, $rc, $msg, $args) = @_;
> + if ($rc == OK) {
> + $self->reset_transaction;
> + }
> + $self->respond($rc, @$msg);
> }
We have to keep the default behaviour. Without any plugin hooking rset,
this wi
I've received reports by some users that messages
are being duplicated. After a fair amount of head
scratching it seems that a Microsoft Exchange serer
is connecting to qpsmtpd and sending:
1. HELO blah.
2. MAIL FROM:
3. RCPT TO:
4. DATA
5 .
6. RSET
7. M
