s somewhat limited.
You could eliminate the need to guess by complying with these
guidelines for posting here:
http://www.postfix.org/DEBUG_README.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ice: use a separate submission service and ONLY allow relay
through that, not on port 25 at all.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
mailbox.
Note: I don't use this; I manually create postmaster and abuse
aliases. It's untested. Test it before you commit. :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
de = 550
> virtual_alias_maps = pgsql:/etc/postfix/virtual-aliases-pg.cf
> virtual_gid_maps = static:60008
> virtual_mailbox_base = /vhome
> virtual_mailbox_domains = pgsql:/etc/postfix/virtual-mailbox-domains-pg.cf
> virtual_mailbox_maps = pgsql:/etc/postfix/virtual-mailboxes-pg.cf
> virtual_transport = dovecot
> virtual_uid_maps = static:60008
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ut smtpd_proxy_filter?
At this point you will do better if you back up and describe the
problem you're trying to solve. Where/why do you need the queue ID
displayed?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Wed, Feb 29, 2012 at 12:31:37PM +0100,
Tugdual de Lassat (ML) wrote:
> On 2/28/2012 07:15 PM, /dev/rob0 wrote :
> > LEARN regular expressions if you plan to use them. KNOW what
> > those metacharacters mean. KNOW how and when and why you need
> > to anchor expression
>
> flags=DRhu user=www-data argv=/usr/bin/php
> /home/samba/test/get_bounces.php
>
> bouncer unix - n n - - pipe
>
> flags=DRhu user=www-data argv=/usr/bin/php /home/samba/test/get_return.php
--
http://rob0.nodns4.us/ -- system adminis
domain name.
check_recipient_access and check_sender_access lookups check
individual addresses before domains. See the section "EMAIL
ADDRESS PATTERNS" in:
http://www.postfix.org/access.5.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is s
d "warn_if_permit". To actually use it as Stan describes, it
would be:
smtpd_mumble_restrictions = [ ... ]
warn_if_permit permit_dnswl_client list.dnswl.org
permit_dnswl_client list.dnswl.org
[ ... ]
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Thu, Feb 23, 2012 at 03:46:49PM -0600, Noel Jones wrote:
> On 2/23/2012 3:39 PM, /dev/rob0 wrote:
> > On Thu, Feb 23, 2012 at 12:58:46PM -0800, rg86...@airpost.net
> > wrote:
>
> > snip
> >>> Here's another thought, which I think someone else menti
On Thu, Feb 23, 2012 at 12:58:46PM -0800, rg86...@airpost.net wrote:
> On Thu, Feb 23, 2012, at 02:28 PM, /dev/rob0 wrote:
> > sendmail(1) writes mail to a file which is enqueued by the
> > pickup(8) daemon. smtpd(8) is not used. smtpd-specific settings
> > such as smtpd_se
postfix/smtpd[19684]: NOQUEUE:
> client=mail.rogermail.lan[192.168.1.10]
> Feb 23 11:16:22 mx postfix/smtpd[19684]: NOQUEUE:
> reject: RCPT from mail.rogermail.lan[192.168.1.10]: 550
> 5.1.1 : Recipient address
> rejected: User unknown in virtual mailbox table;
> from=
> to= proto=ESMTP
> helo=
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Thu, Feb 23, 2012 at 08:28:05AM -0800,
rg86...@airpost.net wrote:
> On 02/23/2012 06:53 AM, /dev/rob0 wrote:
> > I see the goal as being, in part, to detect a spammer in THIS
> > transaction. That sounds reasonable to me. But the proper thing
> > here would be to us
]:2446
> postscreen[99920]: NOQUEUE: reject: RCPT from [124.42.204.113]:2446: 550
> 5.7.1 Service unavailable; client [124.42.204.113] blocked using
> zen.spamhaus.org; ...
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
reasons why you wish to do so. There
> are likely many alternatives that may well work better.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ior in the 2.x syntax. My migration to 2.x was painless.
> I'll take a closer look at NetBSD's AUTH
> library, and see what it takes to support that in Postfix.
More choices are always good! :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
to both lists), or offlist to the address in the README file (or as
detailed below.) Thanks for your interest.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
/rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t, but is worth a visit.
All of the aforementioned HTML files can be found in your own
$html_directory, as well as online at http://www.postfix.org/ . Be
sure to browse the other titles in the $html_directory while you are
there. I keep a link in my browser for ready reference.
--
http:/
der periodic automated DNS checks which would
disable any domain where DNS points elsewhere. (Or at least alert
administrators to check on it.)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
leanup. "postfix reload" ensures that the changes are effective
immediately. "man 8 cleanup" has the details.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
bet, while making little if any
impact on spam.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
n only if "/dev/rob0" is in the Subject:
his query:
>
> dbname = postfix
> hosts = 10.0.1.54
> query = SELECT action FROM recipient_access WHERE address='%s'
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
mysql_table(5) for Postfix-specific hints, and talk to the MySQL
people for support of their software.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
smtpd source
> code then I can try to fix the AWK script.
At this point we're not sure if it is an Apple-patched system or just
macports without the Apple patches. My guess is that the OP upgraded
from patched to unpatched, and Larry's reply is the one he needs to
regard, because that upgrade probably broke things.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
me host (see "MX Policy Test", a
Postfix 2.9 feature.) Some clients will immediately try the lower
priority MX, and be accepted.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
o block access to
sendmail, or to write some kind of software to sit in front of
sendmail and check your access rules.
http://www.postfix.org/postconf.5.html#authorized_submit_users
http://www.postfix.org/sendmail.1.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
; > Where the sample@domain.example is a valid address on the
> > > local machine.
> > >
> > > What's the easiest to let this mail through? I tried adding
> > > the domain to /var/spool/postfix/etc/hosts, and it didn't
> > > help.
http://www.postfix.org/SMTPD_ACCESS_README.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
:45:25 -0500
Message-Id: <1326231925.7884.33.camel@SID>
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
rictions and/or smtpd_client_restrictions,
> as well as restriction classes:
> http://www.postfix.org/SMTPD_ACCESS_README.html
> http://www.postfix.org/RESTRICTION_CLASS_README.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ux box can
> resolve exchange.mydoamin.local to an IP.
By default smtp_host_lookup is "dns" only.
> Any suggestions?
Also, please don't top-post your replies. Your MUA badly mangled
quoting in the rest of the thread so I didn't bother to try to fix
that. Thanks.
--
ht
a better way?
That would be one of the worst choices, because a forged HELO cannot
easily be tested.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
much use to CentOS users.
For CentOS support, see CentOS documentation and support forums.
The Postfix answer: http://www.postfix.org/PGSQL_README.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
on and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
E.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
s no additional messages.)
Perhaps a slightly less insane ;) test would be to check
xbl.spamhaus.org at that point. But hotels and public hotspots are
often listed there. You might catch a few bad users, but you will
*not* have reasonable protection for clean users.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
rom the few other files under /var/spool/postfix/. But then,
I am not sure that there is an actual problem that this idea will
solve. :)
We here tend to want to focus on real problems. If everything is
working well, don't tinker. Postfix default settings generally are
good; a competently-managed system's "postconf -n" should typically
be very short.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Fri, Jan 27, 2012 at 02:49:57PM -0500, Wietse Venema wrote:
> Try this patch.
It works! Double apostrophe in the query. Thanks.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Fri, Jan 27, 2012 at 12:54:46PM -0500, Wietse Venema wrote:
> /dev/rob0:
> > Postfix 2.9.0-RC2, trying to send to an external address with
> > an apostrophe:
> >
> > rob0@chestnut:~$ fortune -o | mail -so "Joe's"@example.net
> > rob0@chestnut:~$
thing as a SQLite server, it appears that this
text might have been cloned out of a ??sql_table(5) man page; but
it's not relevant here.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
eks, but my (also
not busy) Linux x86_64 host has none of these. Running various 2.9
snapshots during that time. (Going to install RC2 tonight.)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
g to main.cf:
parent_domain_matches_subdomains =
I hope this is clearer now.
> example.co.in, I must have an explicit ".example.co.in" pattern
> listed.
>
> Rarely is this a good idea; certainly not in the case of a second-
> level domain like co.in.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
unset that, so that if I want to match a subdomain of
example.co.in, I must have an explicit ".example.co.in" pattern
listed.
Rarely is this a good idea; certainly not in the case of a second-
level domain like co.in.
--
http://rob0.nodns4.us/ -- system administration and consulti
> quit
> 221 2.0.0 Bye
> Connection closed by foreign host.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
elope sender address.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
p remedy such issues)?
You seem to have a basic grasp of the real issues. You can use that
in consultation with prospective cloud providers. If they let you
talk to the abuse desk, and you find that THEY are doing the
explaining to YOU, consider that a Good Sign. A cloud provider
without a good, email-fluent abuse desk is likely to have trouble.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
f the disconnects are "after CONNECT"
and not "after EHLO", Noel's theory sounds more likely. But it is a
good idea to look into the client's side of the story, too.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Thu, Jan 19, 2012 at 05:24:31PM -0500, Wietse Venema wrote:
> /dev/rob0:
> > If you want to see smtpd_restriction_classes gone crazy, refer
> > to my "howto" link from the site below. The particular page &
> > sections you would want is 02-postfix-sqlite
s done. I'm working on that as we speak.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tem administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
where there are two authentication failures
> within the same second, or where for some other reason things
> don't match up perfectly.
That can be a problem even with all the logs in one file.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Top-posting fixed, please do not top-post your replies on this list.
Thanks.
On Thu, Jan 19, 2012 at 08:16:22AM +0100, Hervé Hénoch wrote:
> Le 18/01/2012 19:30, /dev/rob0 a écrit :
> >On Wed, Jan 18, 2012 at 10:59:46AM +0100, Hervé Hénoch wrote:
> >>In main.cf :
> >>
0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
(Web address is blacked out, today only, 2012-01-18)
pient validation and is
> >strongly discouraged.
>
> Postfixadmin supports domain aliasing without losing recipient
> validation (although I don't use it myself)...
Seems like a SQL trigger on insert could easily create both entries
when one is entered.
--
http://rob0.nodns
might
choose.
The task of translation into LDAP is left to you.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
(Web address is blacked out, today only, 2012-01-18)
uot;dono...@example.us" and also for
"dono...@example.net".
http://www.postfix.org/BASIC_CONFIGURATION_README.html
If you need namespace separation, consider the virtual alias example:
http://www.postfix.org/VIRTUAL_README.html#virtual_alias
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
15.
It hasn't changed much; I promoted BRBL to 3 points and SEM to 2. It
would not hurt to add a few less-trusted 1-point lists. My threshold
value is 3.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Sun, Jan 15, 2012 at 07:49:49PM -0600, Al Zick wrote:
> On Jan 13, 2012, at 5:52 PM, /dev/rob0 wrote:
> >On Friday 13 January 2012 16:57:21 Al Zick wrote:
> >>On Jan 12, 2012, at 3:57 AM, Egoitz Aurrekoetxea Aurre wrote:
> >>>Apart from this if you u
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
few spams & 419s from hotmail or gmail, but the
direct-to-MX botnets are not getting through very often.
> (like it should be) and a filtering during dovecot should mean
> that whitelisted servers still get their email filtered.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
"IF /^To:/" to anchor to the beginning of the
line.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ld prefer to avoid
> that if possible.
>
> Another unrelated question, I looked at the mailing list archives
> and 2011 seems to be missing.
> http://archives.neohapsis.com/archives/postfix/
Must not have been a memorable year. ;)
--
http://rob0.nodns4.us/ -- system administration and cons
of luck on this one.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ything it needs for data (e.g., mysqld,
> postmaster, whatever.) You do not have a Postfix issue.
Forgot to mention Courier authdaemond, mentioned in the OP.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
hat they are forced to authenticate properly?
That is a policy decision for you to make.
> Whats weird is that the problem gets fixed by simply restarting
> the services.
Try it without restarting Postfix next time, just your saslauthd and
anything it needs for data (e.g., mysqld, postmaster, whatever.) You
do not have a Postfix issue.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
is desirable or important. It is generally far
harder to manually speak SMTP to a server than it is to configure a
mail client. I use Kmail or mutt(1), myself.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
pecial syslog_* settings in your postconf, therefore it
seems likely that the problem was introduced by a change in your
syslogd or its configuration.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
htly less pain.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ame up with: are you using a DNS forwarder which is
probably blocked by Spamhaus? Try testing, from the Postfix host:
$ dig 2.0.0.127.zen.spamhaus.org. any
This should return their test records. Compare with NXDOMAIN here:
$ dig 2.0.0.127.zen.spamhaus.org. any @8.8.4.4
> >> First, please supply 'postconf -n' output, as you were directed
> >> in the list welcome message. This allows us to see how you are
> >> currently configured so we can recommend changes that work with
> >> your particular setup, and help you fix anything that's not
> >> currently correct.
> >>
> >> Also, post the output of following command:
> >>
> >> $ postconf |grep 'mail_version ='
(Stan, UUOG, that can be simply "postconf mail_version" :) )
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nd consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
-- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tuesday 03 January 2012 11:28:09 Charles Marcus wrote:
> On 2012-01-03 12:09 PM, /dev/rob0 wrote:
> > Info/advice: with postscreen(8), sane HELO restrictions, and good
> > DNSBLs, clamav is not going to get much use.
>
> Clamav, with the sane-security sigs, most certain
worth your time;
my guess is that it would not be.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
e inet:127.0.0.1:12525
>
> /etc/postfix/whitelist
> example.com permit_auth_destination
> u...@example2.com permit_auth_destination
>
> After creating or modifying /etc/postfix/whitelist do
>
> $ postmap whitelist
>
> See: man 5 access
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
se may be) see
in their MUA.
> >full logs of sample problem transaction, as well as output of
> >postconf -n.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
g/DEBUG_README.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
g.
My bet is on this file; you have done something in "sender_checks"
that you should not have done.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
urse the amavisd-new list would be a better place to follow
up.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
gt; [1] Where "mumble" is one of _client_ or _recipient_ ; it doesn't
> make much sense to use _helo_, and using _sender_ will actually
> increase the chances that you're doing it wrong; the sequence of
> restrictions is VERY important.
snip
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
you decide to go for local(8) delivery, it is simple to set up:
http://www.postfix.org/BASIC_CONFIGURATION_README.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
reserved for such use.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
"we" refers to my
long-time observation of this list, and I think it's a common
view. Similarly, I think Stan's use of "we" can be defended.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tion and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
onf.5.html#authorized_submit_users
3. Alternatively, you could limit access to sendmail(1) using
filesystem permissions, but this might break in an upgrade.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
including other entries as needed, and 'postmap /path/to/noreply-
reject'.
Finally, main.cf:
smtpd_data_restrictions = [ ... ]
check_recipient_access hash:/path/to/noreply-reject
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
id_maps = static:125
> # Additional for quota support
> virtual_create_maildirsize = yes
> virtual_mailbox_extended = yes
> virtual_mailbox_limit_maps =
> mysql:/usr/local/etc/postfix/mysql_virtual_mailbox_limit_maps.cf
> virtual_mailbox_limit_override = yes
> virtual_maildir_limit_message = Desculpe, tamanho da caixa postal
> excedido, tente mais tarde! Sorry, mailbox size exceeded, try
> later!
> virtual_overquota_bounce = yes
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
it off.
Barracuda "Deep header parsing" is a disaster. A large percentage of
legitimate mail from end users on dynamic IP addresses (most people
are in that group) will be blocked.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Thursday 15 December 2011 08:24:51 Gábor Lénárt wrote:
> On Thu, Dec 15, 2011 at 08:19:18AM -0600, /dev/rob0 wrote:
> > On Thursday 15 December 2011 07:53:35 Tomas Macek wrote:
> > > But we have clients, that send mails on both port 25 and
> > > 587. I really can
tream from your MX mailstream.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
e
whitelist is hard to maintain properly, worse than a large blacklist.
So, you might need to step back and reevaluate your restrictions.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
gsumm.pl; perhaps if Jim is
still reading the list he can comment?
It would be worthwhile to add these to sample submission and smtps
lines in the default master.cf. Wietse, have you considered that?
Thanks.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
t; virtual alias maps hash file.
This is good advice, essentially the same message as from the
aforementioned DATABASE_README.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
in this thread which
suggests that you should be, see:
http://www.postfix.org/ADDRESS_CLASS_README.html#relay_domain_class
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
n the loopback
interface, chances are high that said attacker will also have any
encryption keys that might be used.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
601 - 700 of 1152 matches
Mail list logo
