On 21/02/2010 22:17, Wietse Venema wrote:
Jonathan Tripathy:
[The backup MX host accepts mail from forged local sender
addresses, but the backup MX does not support SASL].
Actually, the MAILER-DAEMON message doesn't get queued at all! It just
discards it when it can't find the user (If th
On Sun, 21 Feb 2010, Jonathan Tripathy wrote:
> With regards to SPF breaking email fordwarding:
>
> If i implemented SPF on my server, is the above only an issue if
> someone were to use an external forwarding service, and forward mail
> to an account on my server?
Please use google and search m
Jonathan Tripathy:
[The backup MX host accepts mail from forged local sender
addresses, but the backup MX does not support SASL].
> > Actually, the MAILER-DAEMON message doesn't get queued at all! It just
> > discards it when it can't find the user (If the from address was
> > notarealaddr...@my
Hi Folks,
With regards to SPF breaking email fordwarding:
If i implemented SPF on my server, is the above only an issue if someone
were to use an external forwarding service, and forward mail to an
account on my server?
I'm just talking about receiving mail for now..
Thanks
On 21/02/2010 22:03, Jonathan Tripathy wrote:
On 21/02/2010 22:00, Jonathan Tripathy wrote:
On 21/02/2010 21:55, Wietse Venema wrote:
Jonathan Tripathy:
My main issue is that my backup mx doesn't have sasl enabled (It's
relay
only..)
Why would your users submit mail to the backup MX ho
On 21/02/2010 22:00, Jonathan Tripathy wrote:
On 21/02/2010 21:55, Wietse Venema wrote:
Jonathan Tripathy:
My main issue is that my backup mx doesn't have sasl enabled (It's
relay
only..)
Why would your users submit mail to the backup MX host?
Wietse
You're correct, they woudn't. I
On 21/02/2010 21:55, Wietse Venema wrote:
Jonathan Tripathy:
My main issue is that my backup mx doesn't have sasl enabled (It's relay
only..)
Why would your users submit mail to the backup MX host?
Wietse
You're correct, they woudn't. I just don't like the thought tha
Jonathan Tripathy:
> My main issue is that my backup mx doesn't have sasl enabled (It's relay
> only..)
Why would your users submit mail to the backup MX host?
Wietse
On 21/02/2010 21:31, Jonathan Tripathy wrote:
On 21/02/2010 21:16, Wietse Venema wrote:
Jonathan Tripathy:
You can also specify MULTIPLE maps:
/etc/postfix:main.cf
smtpd_sender_login_maps = mysql:whatever
hash:/etc/postfix/default
/etc/postfix/default:
@example.com root
Don
On 21/02/2010 21:16, Wietse Venema wrote:
Jonathan Tripathy:
You can also specify MULTIPLE maps:
/etc/postfix:main.cf
smtpd_sender_login_maps = mysql:whatever hash:/etc/postfix/default
/etc/postfix/default:
@example.com root
Don't forget to postmap the /etc/postfix/default f
Jonathan Tripathy:
> > You can also specify MULTIPLE maps:
> >
> > /etc/postfix:main.cf
> > smtpd_sender_login_maps = mysql:whatever hash:/etc/postfix/default
> >
> > /etc/postfix/default:
> > @example.com root
> >
> > Don't forget to postmap the /etc/postfix/default file.
>
> Great! Tha
On 21/02/2010 20:57, Wietse Venema wrote:
Wietse Venema:
Jonathan Tripathy:
You forgot to set an owner rule for @domain.
How would I do that? I'm not sure if this is relavent but I'm currently
using:
For complete description of
a) the smtpd_sender_login_maps dat
Wietse Venema:
> Jonathan Tripathy:
> > > You forgot to set an owner rule for @domain.
> >
> > How would I do that? I'm not sure if this is relavent but I'm currently
> > using:
>
> For complete description of
>
> a) the smtpd_sender_login_maps database queries
>
> b) the order of queries
>
>
Jonathan Tripathy:
> > You forgot to set an owner rule for @domain.
>
> How would I do that? I'm not sure if this is relavent but I'm currently
> using:
For complete description of
a) the smtpd_sender_login_maps database queries
b) the order of queries
See: http://www.postfix.org/postconf.5.h
You forgot to set an owner rule for @domain.
Wietse
How would I do that? I'm not sure if this is relavent but I'm currently
using:
smtpd_sender_login_maps=mysql:/etc/postfix/mysql_login_maps.cf
and mysql_login_maps.cf is:
hosts = 127.0.0.1
user =
password =
dbname = mailser
Wietse Venema:
> Jonathan Tripathy:
> > On 21/02/2010 19:34, Darren Pilgrim wrote:
> > > Jonathan Tripathy wrote:
> > >> Sorry I forgot to state that im only concerned with MY server here.
> > >> For example, I don't want someone to telnet to MY postfix server, and
> > >> give m...@mydomain.com f
Jonathan Tripathy:
[ Charset ISO-8859-1 unsupported, converting... ]
>
>
> On 21/02/2010 19:34, Darren Pilgrim wrote:
> > Jonathan Tripathy wrote:
> >> Sorry I forgot to state that im only concerned with MY server here.
> >> For example, I don't want someone to telnet to MY postfix server, and
On 21/02/2010 19:39, LuKreme wrote:
On 21-Feb-2010, at 12:22, Sahil Tandon wrote:
Sorry I forgot to state that im only concerned with MY server here.
For example, I don't want someone to telnet to MY postfix server,
and give m...@mydomain.com for both sender and receiver
What's the matter wi
On 21/02/2010 19:34, Darren Pilgrim wrote:
Jonathan Tripathy wrote:
Sorry I forgot to state that im only concerned with MY server here.
For example, I don't want someone to telnet to MY postfix server, and
give m...@mydomain.com for both sender and receiver
Require authentication, set up sm
On 21-Feb-2010, at 12:22, Sahil Tandon wrote:
Sorry I forgot to state that im only concerned with MY server here.
For example, I don't want someone to telnet to MY postfix server,
and give m...@mydomain.com for both sender and receiver
What's the matter with te SPF configuration you already hav
On Sun, 21 Feb 2010, Jonathan Tripathy wrote:
> On 21/02/2010 19:05, Wietse Venema wrote:
> >Jonathan Tripathy:
> >>Hi Folks,
> >>
> >>To prevent spammers sending email from spoofed addressed that appear
> >>from my domain, I currently use SPF. I'm having second thoughts about
> >>using SPF, so is
On 21/02/2010 19:05, Wietse Venema wrote:
Jonathan Tripathy:
Hi Folks,
To prevent spammers sending email from spoofed addressed that appear
from my domain, I currently use SPF. I'm having second thoughts about
using SPF, so is there any other way to make sure that only
authenticated users
Jonathan Tripathy:
> Hi Folks,
>
> To prevent spammers sending email from spoofed addressed that appear
> from my domain, I currently use SPF. I'm having second thoughts about
> using SPF, so is there any other way to make sure that only
> authenticated users can send email from my domain?
Rec
Hi Folks,
To prevent spammers sending email from spoofed addressed that appear
from my domain, I currently use SPF. I'm having second thoughts about
using SPF, so is there any other way to make sure that only
authenticated users can send email from my domain?
Thanks
2010/2/21 James R. Marcus :
> I'm most concerned about keeping my headers clean so I minimize the chance
> of being considered SPAM.
> thanks,
> James
>
You can strip off some headers using postfix, if you want to do so.
--
Eero
I'm most concerned about keeping my headers clean so I minimize the chance of
being considered SPAM.
thanks,
James
On Feb 21, 2010, at 12:39 AM, Eero Volotinen wrote:
2010/2/21 James R. Marcus mailto:jmar...@edhance.com>>:
Hi,
In regards to having honest headers, is it bad to have localhost.loca
Jonathan Tripathy:
> Are you aware of any Postfix implementations?
Wietse:
> Postfix implements SPF SRS DKIM DomainKeys SenderID BATV and so on
> exclusively via plugins. Just like Postfix implements deep content
> inspection.
Jonathan Tripathy:
> Yes, I understand that we have to use Milters and
On 21/02/2010 16:45, Wietse Venema wrote:
Jonathan Tripathy:
Thanks for the reply.
Are you aware of any Postfix implementations?
Postfix implements SPF SRS DKIM DomainKeys SenderID BATV and so on
exclusively via plugins. Just like Postfix implements deep content
inspection.
I don't
Hello all,
I try a solution to insert a counter number into the Subject line for any
message leaving the email server(sent by a local client through local
interface).
I used the example shown at http://www.postfix.org/FILTER_README.html
but the counter appears in every message hitting the email
Jonathan Tripathy:
> Thanks for the reply.
>
> Are you aware of any Postfix implementations?
Postfix implements SPF SRS DKIM DomainKeys SenderID BATV and so on
exclusively via plugins. Just like Postfix implements deep content
inspection.
I don't bake my own bread, and I don't make my own shoes
On Sun, 21 Feb 2010, Jonathan Tripathy wrote:
> Are you aware of any Postfix implementations?
Please, don't top-post. And there is no Postfix implementation; that is
why you need to find/use a milter or external content filter.
--
Sahil Tandon
Thanks for the reply.
Are you aware of any Postfix implementations?
On 21/02/2010 14:33, Wietse Venema wrote:
Jonathan Tripathy:
Hi Folks,
As many of you will probably know, SPF breaks forwarding using aliases.
The solution is to re-write the from-evenlope when forwarding email.
Does any
Jonathan Tripathy:
> Hi Folks,
>
> As many of you will probably know, SPF breaks forwarding using aliases.
> The solution is to re-write the from-evenlope when forwarding email.
>
> Does anyone know how to do this with postfix?
With an external MILTER program (Postfix >= 2.6):
http://www.postf
Hi Folks,
As many of you will probably know, SPF breaks forwarding using aliases.
The solution is to re-write the from-evenlope when forwarding email.
Does anyone know how to do this with postfix?
Thanks
Jonny
34 matches
Mail list logo
