You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by fractals <fr...@ping.be> on 2001/05/15 13:35:14 UTC
still not able to send mail outward
Sorry to bother you with this. This is not a developer issue but a user one.
I asked this question already a couple of times to the user mailing-list,
but I could not get a working answer.
I think what I am trying to do in very simple and basically everyone should
be able to do it:
To avoid relaying I just want mails whose Sender is not a local user to be
considered as spam. That's all folks !
It seems to me that the basic anti-relay mailet is meant just the other way
around:
<mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
<processor>spam</processor>
</mailet>
Doesn't this mean that the *recipient* is not allowed to be on a remote
server ? How do local users send mail to the outside world then ? This
really doesn't make sense to me... I already tried to put ",urbanium.tv.*"
after the "127.0.0.1" and ",194.183.224.*" which are the 3 first numbers of
the IP address of my server, all this without much confidence. But anyway
none worked.
PLEASE help me on this, I'll be a much more enthusiast James users for the
advanced capabilities it offers (which is why I *do* want to use it as my
mail server) when I know my users can use them to send e-mail !!!
my
Thanks,
Candide
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: still not able to send mail outward
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Alec Yu wrote:
>
> But, pity that, I could not find a solution as you want (and it's what I want too),
> so I wrote my own matcher.
>
> ----- Original Message -----
> From: "fractals" <fr...@ping.be>
> To: <ja...@jakarta.apache.org>
> Cc: <ja...@jakarta.apache.org>
> Sent: Tuesday, May 15, 2001 7:35 PM
> Subject: still not able to send mail outward
>
> > I think what I am trying to do in very simple and basically everyone should
> > be able to do it:
> >
> > To avoid relaying I just want mails whose Sender is not a local user to be
> > considered as spam. That's all folks !
>
> > <mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
> > <processor>spam</processor>
> > </mailet>
> > Doesn't this mean that the *recipient* is not allowed to be on a remote
> > server ? How do local users send mail to the outside world then ? This
> > really doesn't make sense to me... I already tried to put ",urbanium.tv.*"
> > after the "127.0.0.1" and ",194.183.224.*" which are the 3 first numbers of
> > the IP address of my server, all this without much confidence. But anyway
> > none worked.
> That matching condtion means: if you are connecting from outside the localhost
or outside the ip address ranges you specify
> (of the server resides on), you are going to spam something out.
> Anyway, that doesn't make any sense, if you are going to provide services to
> people who may send mails via your server from anywhere (even the users
> can't make sure if they will have the same IP address as their last dial up).
As the matcher is called 'RemoteAddressNotInNetwork', it should not be a
big surpise to hear that it won't work if you don't know what network
they connect from! (DHCP within given networks should work fine, though)
>
> > PLEASE help me on this, I'll be a much more enthusiast James users for the
> > advanced capabilities it offers (which is why I *do* want to use it as my
> > mail server) when I know my users can use them to send e-mail !!!
> I think, with its currently bundled matchers, JAMES just can't do what you want.
> You need my AUTH LOGIN solution... ;-)
>
> My modification also provides 8bit-MIME SMTP service extension for passing
> 8-bit message subjects.
>
> But before I figure out how to make the JAMES core less touched from my
> modification, I am not going to contribute it to the JAMES developmenet team...
> (and to whom? I just felt a bit confused on Apache's contribution mechanism..)
subscribe to james-dev, get current source from cvs or nightly build
(see website), submit tested patches or source files (on james-dev). See
http://jakarta.apache.org/site/guidelines.html
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: still not able to send mail outward
Posted by Alec Yu <al...@msa.hinet.net>.
JAMES implemented no SMTP message delivery authentication service extension.
As a result, up to JAMES 1.2.1, for the SMTP server to check if a message is a spam one,
it can only checks if the sender is from a trusted host or from a real network domain.
Such a spam check cannot check if the sender owns a JAMES user account.
AUTH LOGIN is a kind of SMTP service extension for message delivery authentication.
With a mail servers implementating AUTH LOGIN, for a user to send a message via
SMTP to the server, he/she must be authenticated as one of users on the mail server,
usually with the same ID/psssword as his/her POP3 mail account ID/password.
In offices, MIS people may configure their M$ Exchange serverss to do AUTH LOGIN check,
as to make sure only their local users may send messages via their Exchange servers.
(whether the sender gives an e-mail address not on the sender may not matter, it depends
on how the Exchange server is configured.)
Most mail clients support this feature for a long time already.
----- Original Message -----
From: "fractals" <fr...@ping.be>
To: <ja...@jakarta.apache.org>
Sent: Tuesday, May 15, 2001 10:21 PM
Subject: Re: still not able to send mail outward
> : You need my AUTH LOGIN solution... ;-)
>
> Now I get what you say, it's true that for instance my access provider for
> the office isn't the same as the one for home. So what do you do ? Do some
> authentication or what ? I'd like to know...
Re: still not able to send mail outward
Posted by fractals <fr...@ping.be>.
Ok ok ok
It's all my fault, stupid me. I was indeed connecting from a network outside
that of my server. I'm sorry.
Everything works fine now !
: That matching condtion means: if you are connecting from outside the
localhost
: (of the server resides on), you are going to spam something out.
: Anyway, that doesn't make any sense, if you are going to provide services
to
: people who may send mails via your server from anywhere (even the users
: can't make sure if they will have the same IP address as their last dial
up).
:
: > PLEASE help me on this, I'll be a much more enthusiast James users for
the
: > advanced capabilities it offers (which is why I *do* want to use it as
my
: > mail server) when I know my users can use them to send e-mail !!!
: I think, with its currently bundled matchers, JAMES just can't do what you
want.
: You need my AUTH LOGIN solution... ;-)
Now I get what you say, it's true that for instance my access provider for
the office isn't the same as the one for home. So what do you do ? Do some
authentication or what ? I'd like to know...
: My modification also provides 8bit-MIME SMTP service extension for passing
: 8-bit message subjects.
:
: But before I figure out how to make the JAMES core less touched from my
: modification, I am not going to contribute it to the JAMES developmenet
team...
: (and to whom? I just felt a bit confused on Apache's contribution
mechanism..)
:
:
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: still not able to send mail outward
Posted by Alec Yu <al...@msa.hinet.net>.
But, pity that, I could not find a solution as you want (and it's what I want too),
so I wrote my own matcher.
----- Original Message -----
From: "fractals" <fr...@ping.be>
To: <ja...@jakarta.apache.org>
Cc: <ja...@jakarta.apache.org>
Sent: Tuesday, May 15, 2001 7:35 PM
Subject: still not able to send mail outward
> I think what I am trying to do in very simple and basically everyone should
> be able to do it:
>
> To avoid relaying I just want mails whose Sender is not a local user to be
> considered as spam. That's all folks !
> <mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
> <processor>spam</processor>
> </mailet>
> Doesn't this mean that the *recipient* is not allowed to be on a remote
> server ? How do local users send mail to the outside world then ? This
> really doesn't make sense to me... I already tried to put ",urbanium.tv.*"
> after the "127.0.0.1" and ",194.183.224.*" which are the 3 first numbers of
> the IP address of my server, all this without much confidence. But anyway
> none worked.
That matching condtion means: if you are connecting from outside the localhost
(of the server resides on), you are going to spam something out.
Anyway, that doesn't make any sense, if you are going to provide services to
people who may send mails via your server from anywhere (even the users
can't make sure if they will have the same IP address as their last dial up).
> PLEASE help me on this, I'll be a much more enthusiast James users for the
> advanced capabilities it offers (which is why I *do* want to use it as my
> mail server) when I know my users can use them to send e-mail !!!
I think, with its currently bundled matchers, JAMES just can't do what you want.
You need my AUTH LOGIN solution... ;-)
My modification also provides 8bit-MIME SMTP service extension for passing
8-bit message subjects.
But before I figure out how to make the JAMES core less touched from my
modification, I am not going to contribute it to the JAMES developmenet team...
(and to whom? I just felt a bit confused on Apache's contribution mechanism..)
Re: still not able to send mail outward
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
fractals wrote:
>
> : The following works fine on James 1.2.1:
> :
> : <mailet match="RemoteAddrNotInNetwork=127.0.0.1,192.168.1.*"
> : class="ToProcessor">
> : <processor>spam</processor>
> : </mailet>
> :
> :
> : Do use ip addresses, don't use domain names.
> : As the note in James.config.xml says - order of mailets is important.
> : This comes after local delivery and before remote delivery.
>
> This is my exact configuration (transport processor):
>
> <mailet match="RecipientIsLocal" class="LocalDelivery">
> </mailet>
> <mailet match="HostIsLocal" class="ToProcessor">
> <processor>spam</processor>
> </mailet>
> <mailet match="RemoteAddressNotInNetwork=127.0.0.1,192.168.1.*"
> class="ToProcessor">
> <processor>spam</processor>
> </mailet>
> <mailet match="All" class="RemoteDelivery">
>
> I used 192.168.1.* because you just told me to, but as I said I already
> tried 194.183.224.* which are the 3 first numbers of the IP address of my
> machine, without success. BTW, I already noted that local networks often
> have addresses beginning with 192.168.111... Perhaps you know why...
192.168.1 is one of three IP address ranges reserved for private use (ie
LANs).
You should use your IP addresses!
Other than that, your config looks fine.
>
> The latter configuration still generates error reports in the form:
>
> We were unable to deliver the attached message because of an error in the
> mail server.
>
> Message details:
> Subject: fjdskqmfqsdkljfqmsdfj
> Sent date: Tue May 15 15:44:28 GMT+02:00 2001
> To: fractals <fr...@ping.be>
> Size (in bytes): 2
I don't think this is an error message from james.
What machine gave that mesage?
After you've changed the IP address, try again and look in the file
mailets.log to see what has happened.
>
> BTW2, I *can* send an email from a local user to another local user
good - means james is working
>which
> led me to think that the anti-relay mailet was really discarding remote
> recipients and not remote senders.
>
> Still very, very confused...
>
If you still have a problem (after changing to your IP address) then:
1) Tell us if you have messages in any of the outgoing, error or spam
folders
2) copy & paste the last few lines of mailets.log into an email.
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: still not able to send mail outward
Posted by fractals <fr...@ping.be>.
: The following works fine on James 1.2.1:
:
: <mailet match="RemoteAddrNotInNetwork=127.0.0.1,192.168.1.*"
: class="ToProcessor">
: <processor>spam</processor>
: </mailet>
:
:
: Do use ip addresses, don't use domain names.
: As the note in James.config.xml says - order of mailets is important.
: This comes after local delivery and before remote delivery.
This is my exact configuration (transport processor):
<mailet match="RecipientIsLocal" class="LocalDelivery">
</mailet>
<mailet match="HostIsLocal" class="ToProcessor">
<processor>spam</processor>
</mailet>
<mailet match="RemoteAddressNotInNetwork=127.0.0.1,192.168.1.*"
class="ToProcessor">
<processor>spam</processor>
</mailet>
<mailet match="All" class="RemoteDelivery">
I used 192.168.1.* because you just told me to, but as I said I already
tried 194.183.224.* which are the 3 first numbers of the IP address of my
machine, without success. BTW, I already noted that local networks often
have addresses beginning with 192.168.111... Perhaps you know why...
The latter configuration still generates error reports in the form:
We were unable to deliver the attached message because of an error in the
mail server.
Message details:
Subject: fjdskqmfqsdkljfqmsdfj
Sent date: Tue May 15 15:44:28 GMT+02:00 2001
To: fractals <fr...@ping.be>
Size (in bytes): 2
BTW2, I *can* send an email from a local user to another local user which
led me to think that the anti-relay mailet was really discarding remote
recipients and not remote senders.
Still very, very confused...
Thanks anyway ! :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: still not able to send mail outward
Posted by fractals <fr...@ping.be>.
: The following works fine on James 1.2.1:
:
: <mailet match="RemoteAddrNotInNetwork=127.0.0.1,192.168.1.*"
: class="ToProcessor">
: <processor>spam</processor>
: </mailet>
:
:
: Do use ip addresses, don't use domain names.
: As the note in James.config.xml says - order of mailets is important.
: This comes after local delivery and before remote delivery.
This is my exact configuration (transport processor):
<mailet match="RecipientIsLocal" class="LocalDelivery">
</mailet>
<mailet match="HostIsLocal" class="ToProcessor">
<processor>spam</processor>
</mailet>
<mailet match="RemoteAddressNotInNetwork=127.0.0.1,192.168.1.*"
class="ToProcessor">
<processor>spam</processor>
</mailet>
<mailet match="All" class="RemoteDelivery">
I used 192.168.1.* because you just told me to, but as I said I already
tried 194.183.224.* which are the 3 first numbers of the IP address of my
machine, without success. BTW, I already noted that local networks often
have addresses beginning with 192.168.111... Perhaps you know why...
The latter configuration still generates error reports in the form:
We were unable to deliver the attached message because of an error in the
mail server.
Message details:
Subject: fjdskqmfqsdkljfqmsdfj
Sent date: Tue May 15 15:44:28 GMT+02:00 2001
To: fractals <fr...@ping.be>
Size (in bytes): 2
BTW2, I *can* send an email from a local user to another local user which
led me to think that the anti-relay mailet was really discarding remote
recipients and not remote senders.
Still very, very confused...
Thanks anyway ! :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: still not able to send mail outward
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
fractals wrote:
>
> Sorry to bother you with this. This is not a developer issue but a user one.
> I asked this question already a couple of times to the user mailing-list,
> but I could not get a working answer.
>
> I think what I am trying to do in very simple and basically everyone should
> be able to do it:
>
> To avoid relaying I just want mails whose Sender is not a local user to be
> considered as spam. That's all folks !
which is exactly what the mailet does.
>
> It seems to me that the basic anti-relay mailet is meant just the other way
> around:
>
> <mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
> <processor>spam</processor>
> </mailet>
>
> Doesn't this mean that the *recipient* is not allowed to be on a remote
> server ? How do local users send mail to the outside world then ? This
> really doesn't make sense to me... I already tried to put ",urbanium.tv.*"
> after the "127.0.0.1" and ",194.183.224.*" which are the 3 first numbers of
> the IP address of my server, all this without much confidence. But anyway
> none worked.
>
> PLEASE help me on this, I'll be a much more enthusiast James users for the
> advanced capabilities it offers (which is why I *do* want to use it as my
> mail server) when I know my users can use them to send e-mail !!!
>
The following works fine on James 1.2.1:
<mailet match="RemoteAddrNotInNetwork=127.0.0.1,192.168.1.*"
class="ToProcessor">
<processor>spam</processor>
</mailet>
Do use ip addresses, don't use domain names.
As the note in James.config.xml says - order of mailets is important.
This comes after local delivery and before remote delivery.
As for naming, the remote address here is the ip address from which the
mail came. You set it to your own network(s). So you can read the
mailet/matcher combo as: "if the sender's ip address is not in my
network, its spam".
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: still not able to send mail outward
Posted by Marcel Juffermans <mj...@dds.nl>.
----- Original Message -----
From: "fractals" <fr...@ping.be>
> To avoid relaying I just want mails whose Sender is not a local user to be
> considered as spam. That's all folks !
>
> It seems to me that the basic anti-relay mailet is meant just the other
way
> around:
>
> <mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
> <processor>spam</processor>
> </mailet>
>
Perhaps this helps: the "Remote" bit in "RemoteAddrNotInNetwork" seems to
mean the (remote) client connecting to James via SMTP. Of course, when
spamming, the (remote) client connecting to James is not on your networks,
so you just put your networks in the list.
> Doesn't this mean that the *recipient* is not allowed to be on a remote
> server ? How do local users send mail to the outside world then ? This
> really doesn't make sense to me... I already tried to put ",urbanium.tv.*"
> after the "127.0.0.1" and ",194.183.224.*" which are the 3 first numbers
of
> the IP address of my server, all this without much confidence. But anyway
> none worked.
>
And, as someone else already mentioned, the order of the matcher is
important.
Marcel
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org