I was able to recover by also rebuilding. BTW, I too am using the latest
version of m0n0.
>I am not sure if this helps, but I had a similar problem with the latest
>build of m0n0wall.
>Basically I lost access to an external mail server on port 25 (not blocked
>by the ISP) and the only way I could fix it was to rebuild my m0n0wall and
>then everything returned to normal.
>It was bizarre as I never put any rules in my m0n0wall to block SMTP, I
>ever put in a rule to allow it to my DMZ.
>I still have no idea why m0n0wall dropped this nor could I find anything in
>any log saying it was blocked.
>On 10/22/06, Vadim Pushkin <wiskbroom at hotmail dot com> wrote:
>>Thanks guys, but my problem is getting outbound connections to other smpt
>>servers. I am testing by telnetting to another host on port 25. I am not
>>getting connected from one particuliar machine only, and it has no selinux
>>running. I have another windoze box that this does work for. This
>>after I created a nat rule, which I've since removed. I am not sure if
>>perhaps a remnant of this rule is hosing me somehow, which is why I need
>>know how to clean nat cache or something else.
>> >Lee Sharp wrote:
>> > > On Sat, 2006-10-21 at 00:58 +0000, Vadim Pushkin wrote:
>> > >> Hello;
>> > >>
>> > >> I've been using monowall for my home for quite some time, now I wish
>> > >> it for bigger things but I am baffled as to why I am unable to get
>> > >> smtp from inside my LAN. I have very simple rules and setup.
>> > >>
>> > >> My internal network is 192.168.1.0, my m0n0 box is 192.168.1.1
>> > >
>> > > Many ISPs filter smtp. That is most likely your problem, as I am
>> > > running mail servers behind many m0n0walls.
>> >Many ISPs who think they are smart block port 25, but do not understand
>> >that port is for MTA (Mail Transport Agent) use to move message.
>> >The port to inject a message into the system is the "submission
>> >services" port, which is 587. Try setting that as your SMTP port.
>> >Works on my ISP, which blocks inbound 25, but not 587.