[rt-users] Upgraded from 4.0.7 to 4.0.17, but rt-mailgate has lost its way
Kevin Falcone
falcone at bestpractical.com
Tue Oct 22 13:10:47 EDT 2013
On Mon, Oct 21, 2013 at 12:00:34PM +0200, Sakhi Hadebe wrote:
> Dear All,
>
> I have upgraded succcesfully upgraded to 4.0.17, everything seems to be fine, except that RT
> is not receiving email tickets. nor sending automated emails to requestors.
>
> Oct 21 11:55:46 tracker postfix/local[28064]: 352E3129BB: to=<rt at tracker.sanren.ac.za>,
> relay=local, delay=328, delays=327/0.02/0/0.22, dsn=4.3.0, status=deferred (temporary failure.
> Command output: An Error Occurred ================= 302 Found )
rt-mailgate hits an error here.
What's in your apache logs?
Since 302 is a redirect, I assume that rt-mailgate is being pointed to
a url that your apache configuration then redirects to RT. This is
not currently handled well by rt-mailgate. Most commonly this is
because you've pointed rt-mailgate to an http:// url but apache
redirects to https://
> Oct 21 11:55:46 tracker postfix/qmgr[4558]: C5F3B129BF: from=<>, size=3181, nrcpt=1 (queue
> active)
>
> Oct 21 11:55:46 tracker postfix/bounce[28068]: 352E3129BB: sender delivery status
> notification: C5F3B129BF
>
> Oct 21 11:55:48 tracker postfix/smtp[28071]: C5F3B129BF: to=<shadebe at csir.co.za>,
> relay=smtp.csir.co.za[146.64.10.99]:25, delay=2.1, delays=0.01/0.01/2/0.12, dsn=2.0.0,
> status=sent (250 2.0.0 r9L9tmZZ031607 Message accepted for delivery)
>
Looks like something generated a bounce here, but the mail was
accepted locally for delivery rather than forwarded on.
-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20131022/c65e2b8b/attachment.sig>
More information about the rt-users
mailing list