On Wed, 28 Oct 2009 14:38:12 -0500
Noel Jones wrote:
> I say put on your somber face and agree that Hotmal is goofed
> up, hope they fix it soon.
My experience with Hotmail and other major web mail vendors is that
they are too busy finding new and innovative ways to break email
interconnectivit
her domains
from the potential effects of real or perceived misbehavior from the
others.
Chris Babcock
signature.asc
Description: PGP signature
> Are there any non-internet, unix domain socket(s) which can be used
> to send mail to the smtp daemon? i.e. is there any *documented* way
> to give mail to postfix for remote delivery that doesn't involve the
> tcp/ip stack (other than the sendmail binary).
http://www.postfix.org/master.5.html
On Tue, 01 Sep 2009 22:30:48 +0200
Benny Pedersen wrote:
> On tir 01 sep 2009 02:20:26 CEST, LuKreme wrote
> > On 31-Aug-2009, at 08:07, nunatarsuaq wrote:
> >> Aug 30 11:46:28 ghost postfix/smtpd[26223]: connect from
> >> ppp-124-122-30-5.revip2.asianet.co.th[124.122.30.5]
> > WHy are you ac
On Sat, 08 Aug 2009 11:24:55 +0200
Per Jessen wrote:
> I'd like to treat the original and the bcc copy slightly different
> based on their content. Basically:
>
> a) original: if headerX matches condition1, override transport to
> divert email.
>
> b) bcc-copy: if headerX matches condition2, o
ownstream
consumers of the subdomain. Someone who behaves perfectly well on my
server might be an exceedingly poor judge of character. Without
limiting the depth of the certificate, I would have no way to accept a
TLS connection as the first without being open to the second.
I love waking
On Sun, 12 Jul 2009 15:12:24 -0500
Noel Jones wrote:
> Yes, the message was rejected by your DKIM policy action. The
> postfix default_milter_action only triggers when the milter
> cannot be contacted. If you want to accept mail that fails
> DKIM, see the dkim-filter documentation.
I sent a
alhost.$mydomain localhost
mydomain = asciiking.com
myhostname = $mydomain
mynetworks = 127.0.0.0/8 70.38.5.64/29
myorigin = $mydomain
owner_request_special = no
queue_directory = /var/spool/postfix-asciiking
recipient_delimiter = +
smtpd_banner = $myhostname ESMTP Chris Babcock 602-85
at then you
could give each customer a different internal interface and establish
your own reputation metrics as a basis for routing their mail to your
Internet-facing mail servers, in effect creating a risk pool for mail
senders. It's still expensive and sub-optimal, but it's not entirely
doomed. More importantly, it's a path toward the re-evaluation of the
business model.
Chris Babcock
signature.asc
Description: PGP signature
teful for returned mail and I
take care to make sure that it goes someplace where it can be used to
stop the sorceror's apprentice from making more brooms. I hate it when
providers don't notify me when they won't deliver mail because it
doesn't give me a chance to fix the
On Mon, 02 Feb 2009 16:26:43 +0200
Murat Ugur EMINOGLU wrote:
> "reverse record,spf record, ptr record " OK.
You sure?
[ch...@mail ~]$ dig murat.ws
; <<>> DiG 9.5.0-P1 <<>> murat.ws
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53656
;; flags
w bruises if it is going to keep
you from getting killed in the real world.
Chris Babcock
signature.asc
Description: PGP signature
k.
> I use
>
> *^Sender: owner-postfix
> .listes.postfix/
"From:" != "From "
Tolga is filtering on the envelope sender, not the header field. The
colon in first post was an error. The list id header is the most likely
to remain consistant, but sender is a good c
> > The relay access was rejected, but I don't want anyone to get even
> > this far. Newbie-oriented advice appreciated.
> >
> Postfix listens for all connections on inet_interfaces.
...by default. See:
http://www.postfix.org/postconf.5.html#inet_interfaces
> The easiest, and best, way is
al with the joe job issue, but even with
strict sending policies I don't know the chances that the recieving
machine will implement either of these policies in a way that deals
constructively with backscatter.
Chris Babcock
signature.asc
Description: PGP signature
0]: DCA4A9480D9: removed
I don't mind being more exhaustive if there's any chance that I've
overlooked something, but I've been using Postfix a couple years now
and this is the only part of my configuration that I don't really know
that well.
Thanks,
Chris Babcock
signature.asc
Description: PGP signature
rather
than handing it to the other instance for delivery. I'm trying to follow
"Configuring an Alternate Transport" from p 403 of 'The Book of
Postfix'. Is my transport misconfigured? Is transport_maps the right
main.cf parameter? Something painfully obvious?
Thanks,
Chris Babcock
signature.asc
Description: PGP signature
ur master
copy as its prerequisite. Type "make all" to propagate your changes.
Chris Babcock
signature.asc
Description: PGP signature
about how to
handle incoming mail to the archive. There are many ways to do that,
including pulling mail off a POP or IMAP server or delivering to a
command that parses the message and inserts the content into the data
base.
Chris Babcock
signature.asc
Description: PGP signature
On Fri, 9 Jan 2009 03:33:59 -0800
carconni wrote:
> HI,
>
> Two days ago my company mail server died. I was able to set up a
> temporary server until I could get the data off the old drive.
> Tonite I moved mailman and /var/spool/ over and reconstructed the
> mail boxes.
>
> Everything looked
to submit mail for Gmail
to relay.
http://mail.google.com/support/bin/answer.py?answer=78799
Chris Babcock
signature.asc
Description: PGP signature
hat your users are not to originate mail
"from" their accounts outside of your network then you are not dropping
any legitimate mail. The wisdom of the policy is outside the scope of
the list, but there's no shortage of people who will either tell you
"Don't do it," or "Fine, but you need to provide a way (auth) for users
to follow the policy."
Chris Babcock
signature.asc
Description: PGP signature
d the bounce message also from the sender "<>". I
> am wondering if this is by default then my users will get lots of
> bounce notification mails which they have never sent. So, the total
> idea behind implementing this feature will fail. There has to be some
> way that I am not able to find. Please suggest how should I proceed.
> Am I testing in the wrong way or missing any thing?
>
> > If I've got it backwards, and you simply do not want to
> > receive bounce messages, though it is generally considered a
> > bad idea as it's against RFC, you can filter on the
> > empty envelope sender (<>). Standard disclaimer:
> > DON'T DO THAT! Somebody recently mentioned a DNSBL
> > (ips.backscatterers.org I think, search for it) to use as a
> > conditional aid, but that would do nothing about the
> > 'problem' in this scenario, the first server
> > (internal server) relaying a message that it should not
> > have.
>
> Thats not a case, we are receiving the Bounce messages for local
> users.
It's doing what you're asking... "REJECT" means bounce the message. You
probably want to "DISCARD" it.
There *MAY BE* legitimate reasons for for mail to come into your network
from a server outsite the network addressed to one of your users and
purporting to be from that user. For example, test messages from remote
workers sending through their home ISP. Just so that you are aware of
the other side of the issue.
Chris Babcock
signature.asc
Description: PGP signature
mynetworks" includes machines that aren't in a room with a lock on the
door, but not if it meant reconfiguring every PHP app and shell script
that sends mail out of the company to authenticate itself.
Chris Babcock
signature.asc
Description: PGP signature
On Sun, 28 Dec 2008 12:01:02 -0500
Vince Sabio wrote:
> I'm looking for a perl script that can create an e-mail message with
> a custom header (i.e., customized header-From and To lines, and
> ideally customized envelope-From, so that I can route bounces to a
> different address). I'm willing
25 matches
Mail list logo
