y original approach.
Thanks!
Nicolás
Mensaje original
De: wie...@porcupine.org
Fecha:25/03/2016 17:56 (GMT+00:00)
Para: Postfix users
Asunto: Re: Hardware with non-FQDN EHLO
Nicol?s:
> Hi,
>
> I have some hardware which I've configured to send e-mails thr
ches the reject_non_fqdn_helo_hostname restriction.
I'd like to know if there's a simpler way to handle these kind of situations,
though. Do you guys have some tips?
Thanks.
Nicolás
Hi,
We have a filter located outside our organization for outgoing mail
which rewrites the Return-Path to their domain, in the form:
username=abc@theirdomain.com. Once the filter processes the message,
it's forwarded to the destination where these headers are received:
Return-Path: usern
ou can use reject_non_fqdn_helo_hostname in the smtpd_helo_restrictions
parameter. For example:
smtpd_helo_restrictions =
permit_mynetworks
reject_non_fqdn_helo_hostname
reject_unknown_helo_hostname
permit
Regards,
Nicolás
header_checks parameter
instead of mime_header_checks, though).
Regards,
Nicolás
Check http://www.postfix.org/SMTPD_ACCESS_README.html, especially
http://www.postfix.org/SMTPD_ACCESS_README.html#danger
Regards,
Nicolás
marks, ... in the query, it's likely
you missed copying the sentence correctly.
[...]
I did have this
virtual_mailbox_base = /var/mail/vhosts
[...]
Also check that this directory (and subdirectories) has the right
permissions so Postfix and your e-mail server can access them. Otherwi
ilbox_base to this value so
the user mailbox's path would be returned as
/home/virtual/quantum-radio.net/station.manager/.
Regards,
Nicolás
f the domains and see the
result for debugging purposes.
Another idea: Is your environment chrooted? Maybe it's a resolv.conf
misconfiguration inside your chroot jail.
Regards,
Nicolás
El 24/03/2015 a las 20:00, Wietse Venema escribió:
After 18 years, including the best of my career, I decided that it
was time to move on. I'll be working on security at Google NY.
Please, there is no reason to say negative things about my old
employer (or my new one!).
Needless to say, I will
outgoing e-mail will go through a different header or
body table depending on which domain it is.
I didn't find any restriction to define inside
smtpd_(client|sender|recipient)_restrictions that I could use to achieve it.
Is it even possible to do this?
Thanks.
Nicolás
El 05/03/2015 a las 23:03, Noel Jones escribió:
On 3/5/2015 4:51 PM, Nicolás wrote:
Actually, on second though, the "different" part just implies that
one of the domains should run a check_policy_service in its
smtpd_(sender|recipient)_restrictions, and the other one would not.
Post
El 05/03/2015 a las 22:30, Noel Jones escribió:
On 3/5/2015 1:27 PM, Nicolás wrote:
Hi,
Up until now I've been using Postfix for one domain, evidently with
just one configuration, using the virtual domains approach. Now I'm
in a situation where I need to handle another completely
scenario, would
someone recommend another way to face it?
Thanks,
Nicolás
do is tell your
mail recipients to whitelist your mail so your domain gains reputation
little by little.
Regards,
Nicolás
El 22/10/2014 a las 19:47, Viktor Dukhovni escribió:
Mail that passes these two conditions is either sent from a client
that matches "permit_mynetworks" (checks logs or Received headers for
client IP) or from an *envelope sender* address that is not blocked
by that table.
Ok, this would explai
I'm running Postfix 2.11 and I'm having some issues with the
check_sender_access parameter. Currently my configuration for sender
restrictions is the following:
smtpd_sender_restrictions =
permit_mynetworks
check_sender_access hash:/etc/postfix/valid_senders
reje
.conf.ext file (most important are the
user_query and password_query directives).
However, this question probably better suits the Dovecot mail list as
the issue you're having has apparently nothing to do with Postfix.
Nicolás
it or if the
problem is them.
--
John Baker
Network Administrator
Marlboro College
Phone: 451-7551 Cell: 490-0066
Regards,
Nicolás
Maybe Apparmor/SELinux/alike blocking access to /run directory?
Enviado de Samsung Mobile
Mensaje original
De: li...@rhsoft.net
Fecha:04/08/2014 21:18 (GMT+01:00)
Para: Mailing-List postfix
Asunto: service unix:/run/clamav-milter/clamav-milter.socket: Permission
denied
El 25/07/2014 3:45, Ian Evans escribió:
I'm currently running postfix in two places. I have a fully
functioning postfix email server for my site's domain and at home I
have postfix installed to allow my home server to send alert messages.
The home server is relaying through my home ISP's smtp
El 22/07/2014 8:58, Jonas Wielicki escribió:
On 22.07.2014 08:17, Nicolás wrote:
Having this configuration, anyone using my mail server as the relayhost
is able to send mails to the domains that I handle (not outside), even
without SASL. I guess that behavior is determined by
Hi,
After maintaining an old version of Postfix for some longer time, I
finally decided to jump to version 2.11 and currently I'm tuning it up.
I'm having an issue with smtpd_relay_restrictions. At this time, the
configuration is the default one:
smtpd_relay_restrictions =
permit_
me configurations as from the older server which
is also running on debian squeeze.
Any suggestions?
Thanks in advanced for your time.
Have you checked whether selinux/apparmor/similar could be blocking it?
Regards,
Nicolás
El 26/07/2012 15:52, /dev/rob0 escribió:
On Thu, Jul 26, 2012 at 01:45:54PM +0100, Nicolás wrote:
El 23/07/2012 12:13, Nicolás escribió:
Hi all!
I have a server with postfix with virtual users (using MySQL),
it's working ok, let's call it A. I also have a secondary server,
which I w
El 23/07/2012 12:13, Nicolás escribió:
Hi all!
I have a server with postfix with virtual users (using MySQL), it's
working ok, let's call it A. I also have a secondary server, which I
want to use to send mails even outside my local network, let's call it
B. So I'm tryi
"Bar" | mailx -s "Foo" postfix-...@gmail.com --tls=true
Could someone tell me what am I doing wrong? I thought using
'smtp_sasl_auth_enable' at B would be enough to use SMTP authentication,
but it's not happening.
Thank you so much!
Nicolás
because it would be delivered again to
pickup and again filtered by header_checks, so it would be placed on
Hold again.
2) postsuper -H doesn't work either.
So how can I deliver one of those mails placed on the hold queue?
Thanx a lot!
Nicolás
El 20/06/2012 17:12, Dennis Guhl escribió:
On Wed, Jun 20, 2012 at 03:00:44PM +0100, Nicolás wrote:
Hi there!
[..]
The whole postconf -n command on the client, nagios.domain.es:
config_directory = /etc/postfix
relayhost = [domain.es]
Is it intentional that you turned MX lookups off? See
id: 535 Incorrect authentication data)
Surprisingly on the server side (mail.domain.es) there's no log activity.
Any ideas of why is this happening?
Thank you very much.
Nicolás
El 08/06/2012 19:40, Patrick Westenberg escribió:
Nicolás schrieb:
myaddr...@gmail.com: host devels.es[78.138.97.64] said: 550-Verification
...
subdomain.devels.es. IN MX 0 mail.devels.es
The response comes from devels.es with 78.138.97.64 but your
MX-Records points to mail.devels.es with
El 08/06/2012 19:22, Reindl Harald escribió:
Am 08.06.2012 20:19, schrieb Patrick Westenberg:
Nicolás schrieb:
myaddr...@gmail.com: host devels.es[78.138.97.64] said: 550-Verification
failed for 550-The mail server could not
deliver mail
to. The account or domain may not exist
to enable subdomain.devels.es
to use devels.es as relay.
I added the following records:
subdomain.devels.es. IN A 85.155.102.33
subdomain.devels.es. IN MX 0 mail.devels.es
mail.devels.es is the server where Postfix is running.
Is there anything I'm missing?
Thanks in advance!
Nicolás
El 06/06/2012 22:25, Patrick Ben Koetter escribió:
* Nicolás:
I'm new to this list and the reason why I'm writing is because I
found out one thing I think is worrying enough to share it with you
I've got my Postfix configured with virtual users, integrated with
Dovecot. Every
s? Is there any way to restrict
creating identities for users unless the administrator allows to do so?
I really would be worried if ANY user would create ANY identities and
use them the way he wants... Any ideas appreciated!
Thanks!
Nicolás
Thanks, it was the reject_unverified_recipient. Now it is working...
2008/10/6 Brian Evans - Postfix List <[EMAIL PROTECTED]>:
> Nicolás Velásquez O. wrote:
>> Hello,
>>
>> We receive a high volume of mail for non nonexistent mailboxes, so we
>> want to pre
e = 550
unverified_sender_reject_code = 550
virtual_alias_maps = $alias_maps$aliasdatabase
regexp:/etc/postfix/virtual.regexp
hash:/etc/postfix/LDAPaddressbook.txt
ldap:/etc/postfix/ldap-users.cf
2008/10/3 Noel Jones <[EMAIL PROTECTED]>:
> Nicolás Velásquez O. wrote:
>>
>
op in
/etc/postfix/transport?
--
Nicolás Velásquez O.
Genève, Suisse
Mobile +41.797976460
38 matches
Mail list logo
