Am 30.03.2014 06:30, schrieb Peter:
> On 03/30/2014 01:25 PM, li...@rhsoft.net wrote:
>>
>> while i agree that it is a bad idea to take headers into account
>
> I wouldn't say that, it depends on exactly what you're doing and how
> much you're basing your decision to reject on that single piece
On Sun, 30 Mar 2014 12:03:45 +0200
"li...@rhsoft.net" wrote:
> time to realize them, however, http://dspam.nuclearelephant.com/
FYI,
the correct URL for dspam -> http://dspam.sourceforge.net
Am 30.03.2014 12:13, schrieb Wijatmoko U. Prayitno:
> On Sun, 30 Mar 2014 12:03:45 +0200
> "li...@rhsoft.net" wrote:
>
>> time to realize them, however, http://dspam.nuclearelephant.com/
>
> FYI,
> the correct URL for dspam -> http://dspam.sourceforge.net
which is *exactly* the same page
dsp
Hello all,
The plan is to have srv #1 to send email to srv #2 and srv #2 gets rid
of the sender server IP address so it only shows srv #2 IP address.
How can I acomblish it?
Br,
Sami Mäntysaari
Am 30.03.2014 13:13, schrieb Sami Mäntysaari:
> The plan is to have srv #1 to send email to srv #2 and srv #2 gets rid
> of the sender server IP address so it only shows srv #2 IP address.
>
>
> How can I acomblish it?
header_checks = regexp:/etc/postfix/header_checks.cf
nested_header_checks =
30.3.2014 14:38, li...@rhsoft.net wrote:
>
> Am 30.03.2014 13:13, schrieb Sami Mäntysaari:
>> The plan is to have srv #1 to send email to srv #2 and srv #2 gets rid
>> of the sender server IP address so it only shows srv #2 IP address.
>>
>>
>> How can I acomblish it?
>
> header_checks = regexp:/
Hi. I am a bit unclear about how email works in a closed domain from roaming
clients (SASL auth clients).
If there is a postfix server that is configured to only accept and send
email to users in the same domain, say for example
j...@restricted.com can only send to another_u...@restricted.com, doe
Am 31.03.2014 00:35, schrieb cybermass:
> Hi. I am a bit unclear about how email works in a closed domain from roaming
> clients (SASL auth clients).
>
> If there is a postfix server that is configured to only accept and send
> email to users in the same domain, say for example
> j...@restricted.
On Sun, Mar 30, 2014 at 03:35:13PM -0700, cybermass wrote:
> If there is a postfix server that is configured to only accept and send
> email to users in the same domain, say for example
> j...@restricted.com can only send to another_u...@restricted.com, does this
> mean that the client's email nev
How can I configure it so that the user's email never bounce through any
other hop but go directly through the server? Also how do I configure it to
ONLY deliver via LMTP and not even SMTP? This confuses me because the user
is a roaming client, how would that user make a connection to the postfix
s
On Sun, Mar 30, 2014 at 04:13:00PM -0700, cybermass wrote:
> How can I configure it so that the user's email never bounce through any
> other hop but go directly through the server?
By arranging for mail to the domain in question to be delivered locally:
http://www.postfix.org/BASIC_CONFIGUR
Ok the user's emails should not go through any other servers out on the
internet to reach mine. Meaning their emails are sent directly within the
server. so if j...@restricted.com sends to j...@restricted.com, nobody else
should be able to read that email, no ISP, or any system. I understand how
no
cybermass:
> Ok the user's emails should not go through any other servers out on the
> internet to reach mine. Meaning their emails are sent directly within the
> server. so if j...@restricted.com sends to j...@restricted.com, nobody else
> should be able to read that email, no ISP, or any system.
Interesting, that is something I never even thought of. Yes the clients are
configured to only go through our custom smtps port since some ISP's block
outgoing 25 and even 465. These clients just need to have only one account
in their mail client I understand. Is there any other configuration I wou
Am 31.03.2014 01:54, schrieb cybermass:
> Interesting, that is something I never even thought of
why should a server hosting example.com relay a to him
submitted message from a...@example.com to b...@example.com
trough a foreign server?
what should that foreign server do with that message
other
I did think about this for a second, Wiestse Venema. Wouldn't my server
just reject those emails if they did try to send via other smtp servers
outbound? Those hosts/senders are auto rejected since my restrictions
reject everyone but my domain
On Sun, Mar 30, 2014 at 4:51 PM, Wietse Venema [via P
587 is dedicated for submission but is it any different if I have
configured smtps to be port 8809 and just have the clients use that port
with STARTTLS instead of 587?
On Sun, Mar 30, 2014 at 5:02 PM, li...@rhsoft.net [via Postfix] <
ml-node+s1071664n66502...@n5.nabble.com> wrote:
>
> Am 31.03.
Am 31.03.2014 02:07, schrieb cybermass:
> 587 is dedicated for submission but is it any different if I have
> configured smtps to be port 8809 and just have the clients use that port
> with STARTTLS instead of 587?
technically you can use whatever port but why not
use standars and make users life
Ok I just noticed I can even comment out the regular smtp protocol from
master.cf to remove listening from port 25. I get alot of hits to our
server, we are an open domain but looking to close soon. We dont intendto
make anyone's life difficult but we have complaints from clients that
cannot send o
The way I had assumed it earlier was the client authenticates via 993
(dovecot IMAP in our case), crafts an email to another user and this email
is delivered instantly via lmtp (in our case, dovecot LDA), but now I see
that in reality, the client sends the email via the smtp port instead
making a d
Am 31.03.2014 02:35, schrieb Shawn Zaidermann:
> The way I had assumed it earlier was the client authenticates via 993
> (dovecot IMAP in our case), crafts an email
> to another user and this email is delivered instantly via lmtp (in our case,
> dovecot LDA), but now I see that in
> reality, th
On Mon, Mar 31, 2014 at 02:44:10AM +0200, li...@rhsoft.net wrote:
> > The way I had assumed it earlier was the client authenticates via
> > 993 (dovecot IMAP in our case), crafts an email to another user
> > and this email is delivered instantly via lmtp (in our case, dovecot
> > LDA), but now I s
Viktor Dukhovni:
> Postfix does not yet support Apple's BURL SMTP extension. With
> Apple as the only MUA that supports BURL, it probably does not make
> sense for Postfix to support BURL.
Last time I asked (late 2013) Apple currently does not support BURL.
Wietse
On Sun, Mar 30, 2014 at 09:13:19PM -0400, Wietse Venema wrote:
> Viktor Dukhovni:
> > Postfix does not yet support Apple's BURL SMTP extension. With
> > Apple as the only MUA that supports BURL, it probably does not make
> > sense for Postfix to support BURL.
>
> Last time I asked (late 2013) Ap
On Thu, Mar 20, 2014 at 11:26:09AM +0530, Tout Guy wrote:
> I was suggested to replace
>
> local_recipient_maps = $virtual_mailbox_maps
Why did you have this in the first place? Remove it.
Mailman is very easy to configure and will maintain its own list
of aliases when given the chance to do
25 matches
Mail list logo
