On 11/21/2014 11:14 PM, Peter wrote:
On 11/22/2014 04:32 PM, L. D. James wrote:
Actually, all people who use google MX will have google.com or gmail.com
in their domains.
Wrong, and this is easy to disprove:
$ dig pajamian.dhs.org MX +short
0 ASPMX.L.GOOGLE.COM.
10 ALT1.ASPMX.L.GOOGLE.COM.
10
On 11/22/2014 04:32 PM, L. D. James wrote:
> Actually, all people who use google MX will have google.com or gmail.com
> in their domains.
Wrong, and this is easy to disprove:
$ dig pajamian.dhs.org MX +short
0 ASPMX.L.GOOGLE.COM.
10 ALT1.ASPMX.L.GOOGLE.COM.
10 ALT2.ASPMX.L.GOOGLE.COM.
20 ASPMX2.G
Actually, all people who use google MX will have google.com or gmail.com
in their domains.
They can use other email servers on their devices. However, those
servers will not be google.com or gmail.com email addresses. They can
publish their google.com or gmail.com addresses as their return
On 11/21/2014 07:02 AM, Wietse Venema wrote:
> /etc/postfix/master.cf:
> forced-ipv4 unix - - n - - smtp
> -o inet_protocols=ipv4
>
> /etc/postfix/transport:
> google.comforced-ipv4:
> gmail.com forced-ipv4:
>
> /etc/postfix/main.cf:
>
Wietse Venema:
> A. Schulze:
> >
> > smtpd_recipient_restrictions =
> > check_foo_to_allow_something,
> > reject "you did this or that wrong, call +49 ... for assistance"
> >
> >
> > Is that possible?
>
> smtpd_recipient_restrictions does not support free text and the
> main.cf parser
--On November 21, 2014 at 2:30:18 PM -0500 Wietse Venema
wrote:
Postfix 2.12 allows one lookup table to produce a query for another
lookup table. For example:
smtpd_sender_login_maps = pipemap:{lmdb:map1, ldap:map2}
This will transform the sender with the LMDB table, before searchin
wietse:
An improved "static" table would do the job:
check_recipient_access static:{reject you did this or that ...}
I'll post a patch in a little while. This takes four lines of code.
Don't hurry, the system I'm currently working on isn't up to date anyway.
The perspective is enough fo
A. Schulze:
>
> smtpd_recipient_restrictions =
> check_foo_to_allow_something,
> reject "you did this or that wrong, call +49 ... for assistance"
>
>
> Is that possible?
smtpd_recipient_restrictions does not support free text and the
main.cf parser does not support quotes.
Fortunatel
Noel Jones:
We use the built-in feature for this:
http://www.postfix.org/postconf.5.html#smtpd_reject_footer
Aha, good point
It's a really nice idea, but in practice few people ever use the
contact or correction info provided in a reject message -- some
end-user mail programs seem to go to
On 11/21/2014 2:25 PM, A. Schulze wrote:
> Hi,
>
> a smtpd_recipient_restrictions for a submission service usually end
> with explicit "reject". That result in a smtp response string
> 554 5.7.1 : Recipient address rejected: Access denied
>
> Sometimes it's helpful to have a more detailed error
Prove it:
$ cat > issuer.pem <
I guess I'm confused about something. Below are the relevant entries in
my /etc/ssl/certs/ca-certificates.crt file for google. This was obtained
by running the "openssl s_client -CAfile ca.pem -starttls smtp
-showcerts -connect alt4.gmail-smtp-in.l.google.com
Hi,
a smtpd_recipient_restrictions for a submission service usually end
with explicit "reject". That result in a smtp response string
554 5.7.1 : Recipient address rejected: Access denied
Sometimes it's helpful to have a more detailed error,
"please authenticate", "go away", "goto http://here.
Viktor Dukhovni:
# perl collate /var/log/mail.log |
qid=9277043E30 perl -ne '
BEGIN{$/="\n\n";$re=$ENV{qid}}
print if m{$re}oi
'
Wow, what a magic script!
Thanks for publishing!
Andreas
Quanah Gibson-Mount:
> >> This is not a productive direction to pursue. The feature you're
> >> looking for is not there, and is not planned. You need to find
> >> a different solution.
> >
> > If Quanah is asking for the sender login map to automagically
> > expand Postfix virtual alias maps, th
On Fri, Nov 21, 2014 at 12:59:01PM -0500, Deeztek Support wrote:
> I get the following error:
>
> Nov 21 12:52:19 smtp postfix/smtp[17859]: 9277043E30:
> to=,
> relay=alt4.gmail-smtp-in.l.google.com[74.125.136.26]:25, delay=5.7,
> delays=0.05/0.02/5.7/0, dsn=4.7.5, status=deferred (Server certifi
On Fri, Nov 21, 2014 at 01:42:55PM -0500, Deeztek Support wrote:
>
> >Certificate chain
> > 0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=mx.google.com
> >i:/C=US/O=Google Inc/CN=Google Internet Authority G2
> > 1 s:/C=US/O=Google Inc/CN=Google Internet Authority G2
> >i:/C=US
Deeztek Support:
>
> > Certificate chain
> > 0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=mx.google.com
> > i:/C=US/O=Google Inc/CN=Google Internet Authority G2
> > 1 s:/C=US/O=Google Inc/CN=Google Internet Authority G2
> > i:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
> >
--On November 19, 2014 at 7:40:07 PM -0500 Wietse Venema
wrote:
Viktor Dukhovni:
On Wed, Nov 19, 2014 at 03:07:19PM -0800, Quanah Gibson-Mount wrote:
> > Sorry, the login table lookup must handle the original address as
> > the lookup key via a single query.
>
> And clearly postfix is alr
Certificate chain
0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=mx.google.com
i:/C=US/O=Google Inc/CN=Google Internet Authority G2
1 s:/C=US/O=Google Inc/CN=Google Internet Authority G2
i:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
2 s:/C=US/O=GeoTrust Inc./CN=GeoTrust Gl
Deeztek Support:
> Nov 21 12:52:19 smtp postfix/smtp[17859]: 9277043E30:
> to=,
> relay=alt4.gmail-smtp-in.l.google.com[74.125.136.26]:25, delay=5.7,
> delays=0.05/0.02/5.7/0, dsn=4.7.5, status=deferred (Server certificate
> not verified)
Certificate chain
0 s:/C=US/ST=California/L=Mountain V
I'm having a hard time with verifying certificates of remote servers
when trying to encrypt and verify using TLS.
I'm using ubuntu. Here are the relevant entries in main.cf:
smtp_tls_policy_maps = hash:/etc/postfix/tls_policy
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
For instance, i
Am 21.11.2014 um 18:27 schrieb Curtis Maurand:
Looks like it didn't try to authenticate. I walked them through the
settings for the umpteenth time and it looked like it worked this time.
I've seen them send several emails.
We have liftoff:
Nov 21 12:23:48 canon postfix/smtpd[7310]: BC443C65D1:
On 11/21/2014 12:03 PM, Noel Jones wrote:
On 11/21/2014 10:51 AM, Curtis Maurand wrote:
i've been really trying to tighten up spam rejection after getting
lots of complaints from users. I've added a bunch of things to the
main.cf for doing rejects, I'm not having any trouble sending email,
but
On 11/21/2014 10:51 AM, Curtis Maurand wrote:
> i've been really trying to tighten up spam rejection after getting
> lots of complaints from users. I've added a bunch of things to the
> main.cf for doing rejects, I'm not having any trouble sending email,
> but one of my clients is and they are aut
On Fri, Nov 21, 2014 at 11:51:45AM -0500, Curtis Maurand wrote:
> I've added a bunch of things to the main.cf
> for doing rejects,
http://www.postfix.org/DEBUG_README.html#mail
http://www.postfix.org/DEBUG_README.html#logging
To report complete logs pertaining to an email transaction
wit
Am 21.11.2014 um 17:51 schrieb Curtis Maurand:
i've been really trying to tighten up spam rejection after getting lots
of complaints from users. I've added a bunch of things to the main.cf
for doing rejects, I'm not having any trouble sending email, but one of
my clients is and they are authent
i've been really trying to tighten up spam rejection after getting lots of
complaints from users. I've added a bunch of things to the main.cf
for doing rejects, I'm not having any trouble sending email, but one of my
clients is and they are authenticating and I have
permit_sasl_authenticated all
Wietse Venema:
> Olivier Nicole:
> > Hello,
> >
> > In main.cf I have:
> > smtpd_client_restrictions =
> > check_client_access cidr:$config_directory/amavis_bypass
> >
> > with the file amavis_bypass being:
> > 203.159.68.0/22 FILTER smtp-amavis:[127.0.0.1]:10026
> >
> > That is applying a s
Olivier Nicole:
> Hello,
>
> In main.cf I have:
> smtpd_client_restrictions =
> check_client_access cidr:$config_directory/amavis_bypass
>
> with the file amavis_bypass being:
> 203.159.68.0/22 FILTER smtp-amavis:[127.0.0.1]:10026
>
> That is applying a special filter for calling Amavis when
On 2014-11-21 09:50, Patrik Båt wrote:
> On 2014-11-20 18:21, Viktor Dukhovni wrote:
>> On Thu, Nov 20, 2014 at 10:42:20AM +0100, Patrik B?t wrote:
>>
Ah thanks for the heads up, posttls-finger returned sha1, probably
because it runs OpenSSL 1.0.x.
>>> "The best practice algorithm is now
On 2014-11-20 18:21, Viktor Dukhovni wrote:
> On Thu, Nov 20, 2014 at 10:42:20AM +0100, Patrik B?t wrote:
>
>>> Ah thanks for the heads up, posttls-finger returned sha1, probably
>>> because it runs OpenSSL 1.0.x.
>> "The best practice algorithm is now sha1", maybe thats why it is default
>> in pos
Hello,
In main.cf I have:
smtpd_client_restrictions =
check_client_access cidr:$config_directory/amavis_bypass
with the file amavis_bypass being:
203.159.68.0/22 FILTER smtp-amavis:[127.0.0.1]:10026
That is applying a special filter for calling Amavis when a message is
issued by my internal
32 matches
Mail list logo
