On 06/22/2014 09:36 PM, Peter Fraser wrote:
>
> Ok I went scouring through the logs trying to trace a particular message like
> you suggested and I did find some like this:
>
> Here's one message I tracked.214CA3AC88D: from=,
> size=585098, nrcpt=500 (queue active)
> then214CA3AC88D: to=, rela
Ok I went scouring through the logs trying to trace a particular message like
you suggested and I did find some like this:
Here's one message I tracked.214CA3AC88D: from=,
size=585098, nrcpt=500 (queue active)
then214CA3AC88D: to=, relay=none, delay=32256,
delays=32255/0.05/0.15/0, dsn=4.4.
On 06/21/2014 08:43 PM, Peter Fraser wrote:
> And what did that log show for the sender non-delivery notification
> message generated as a result of the undeliverable message.
> I looked at the postfix logs again and although I do see different type of
> bounces, I am not seeing anything delivere
And what did that log show for the sender non-delivery notification
message generated as a result of the undeliverable message.
I looked at the postfix logs again and although I do see different type of
bounces, I am not seeing anything delivered to mailman. Here are some examples:
Jun 20 04:11:3
On 06/21/2014 07:23 PM, Peter Fraser wrote:
>
>
> Wait a minute, I typed this command by force of habit, just realized that's
> not what you told me to type so I ran it again
> ps -ax | grep BounceRunner
> and the result is:
> 8138 ?? S 0:00.26 /usr/local/bin/python2.7
> /usr/local/ma
Wait a minute, I typed this command by force of habit, just realized that's not
what you told me to type so I ran it again
ps -ax | grep BounceRunner
and the result is:
8138 ?? S 0:00.26 /usr/local/bin/python2.7
/usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
Ok so ps -waux | grep BounceRunner returns nothing. How do I start it up?
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: htt
Peter Fraser writes:
> The message I showed earlier was the postfix on the same box as
> mailman. Mailman should detect those bounces. I was just thinking
> based on what you said about some smtp servers getting the 5xx
> status from downstream servers thatthose errors would not reach
> mail
On 06/21/2014 01:24 PM, Peter Fraser wrote:
>
>
> The message I showed earlier was the postfix on the same box as mailman.
> Mailman should detect those bounces.
And what did that log show for the sender non-delivery notification
message generated as a result of the undeliverable message.
And
The message I showed earlier was the postfix on the same box as mailman.
Mailman should detect those bounces.
I was just thinking based on what you said about some smtp servers getting the
5xx status from downstream servers thatthose errors would not reach mailman the
way things are set up her
On 06/21/2014 11:00 AM, Peter Fraser wrote:
> I checked the data directory and saw some *.pck files Their names were along
> the lines of "heldmsg--727.pck"so I guess then bouncerunner should
> be running. All the .pck files have heldmsg in the name.
These are all messages held waiting moderato
I checked the data directory and saw some *.pck files Their names were along
the lines of "heldmsg--727.pck"so I guess then bouncerunner should
be running. All the .pck files have heldmsg in the name.
The way our setup is designed though, the mailman box isn't the mail smtp
relay. It sits behin
On 06/20/2014 06:03 PM, Peter Fraser wrote:
> Hi AllI have mailman-2.1.17 running on FreeBSD 9.1 along with postfix-2.11.0,1
> I noticed that bad email addresses were not being cleared out so I downloaded
> get_bounce_info.py,saved it and ran it. No bounce info was displayed.I
> checked the postf
Hi AllI have mailman-2.1.17 running on FreeBSD 9.1 along with postfix-2.11.0,1
I noticed that bad email addresses were not being cleared out so I downloaded
get_bounce_info.py,saved it and ran it. No bounce info was displayed.I checked
the postfix logs and the bounce info was there. A bit from th
14 matches
Mail list logo
