ved, but I know they're not infallible.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
alternate cleanup service is being used.
--
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:
N_FILTER_README.html#limitations
> "helo" etc which I don't want. I want logs to be as clean as
> possible. Is there a way I can accomplish this?
What information is logged is not configurable. Write a script to
clean up the logs before you look at them. :)
--
http://rob
;none".)
You can double your threshold and scores and add in more one-point
lists for testing. I didn't do that with my recent additions, but I
know they have been around long enough to have some credibility. In
that case I think a 1-point result is safe enough.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, Apr 23, 2013 at 11:41:42AM -0700, Steve Jenkins wrote:
> On Tue, Apr 23, 2013 at 11:23 AM, /dev/rob0 wrote:
>
> > Looks very similar to mine, http://rob0.nodns4.us/postscreen.html
> >
> > > postscreen_dnsbl_threshold = 3
[snip]
> > I'm fine with bl
multiple
instances as it is, but there are workarounds, up to and including
patching it. :) (A simpler approach might be to isolate the logs
using a different $syslog_facility per instance.)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, Apr 23, 2013 at 08:05:34PM -0400, Wietse Venema wrote:
> On Fri, Apr 12, 2013 at 06:34:24AM -0400, Wietse Venema wrote:
> > /dev/rob0:
> > > I finally got around to my upgrade to 2.11-20130405 and was
> > > watching logs. A gmail message fell afoul of the after-
ood luck, and enjoy watching the spam rejections. :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
I have rearranged the content and added
scary warnings to show that these settings can cause pain. :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
derstanding of the system s/he is running.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Wed, Apr 24, 2013 at 11:27:41PM +0200, Jeroen Geilman wrote:
> On 04/24/2013 11:23 PM, Steve Jenkins wrote:
> >On Tue, Apr 23, 2013 at 12:41 PM, /dev/rob0 :
> >
> >With those restrictions, you could just as well raise the
> >corresponding postscreen_dnsbl
swl.org*-1 swl.spamhaus.org*-1
Note: if your DNSBL queries have a "secret" in the domain name, you must
censor this information from the postscreen(8) SMTP replies. For example:
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ne of the foregoing three *_enable settings may
> cause
> ### significant and annoying mail delays.
>
>
> READ the postscreen howto, and understand what happens.
> i would not recommend you to enable this.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Wed, Apr 24, 2013 at 03:44:19PM -0700, Steve Jenkins wrote:
> On Wed, Apr 24, 2013 at 3:15 PM, /dev/rob0 wrote:
>
> > True, but for all we know they could be preceded by a
> > check_policy_service or permit_dnswl_client restriction.
>
> Well, in this case they'
from home.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
e vast majority of them are spam zombies.
> Anyway one should be able to configure *client*-side mail software
> without being a specialist of SMTP RFCs and things like that...
Absolutely. You would have your MUA submit to a MSA. Your MSA would
not care about FCrDNS.
This isn't about MUAs, this is about MTAs.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
> you're using a home Internet connection which is listed on PBL. If
> your port 25 is not blocked by the ISP, you could test from home.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
e an issue?
Obviously one must never apply this against one's own submitting
users. Or was Vincent confused about the distinction between mail
exchanging clients and submission clients?
On Tue, May 07, 2013 at 03:12:58PM -0500, Stan Hoeppner wrote:
> On 5/6/2013 6:54 PM, /dev/rob0 wrote:
> &
t. I think in your case you will want to use
"zen.spamhaus.org" as the result.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
e
trick? Would anything else be logged?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ly-run
ESPs.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
aps what you really need is to separate your submission stream
from your MX inbound stream. If you can't/won't force users off of
port 25, you could use a different IP.add.re.ss:25 as your MX, and
leave the old one to your users.
--
http://rob0.nodns4.us/ -- system administration and co
On Sun, May 12, 2013 at 08:11:14PM -0500, /dev/rob0 wrote:
> On Sun, May 12, 2013 at 08:47:38PM -0400, Wietse Venema wrote:
> > A lightly-tested version is available as postfix-2.11-20130512.
>
> Woohoo! Thanks!
>
> I installed it, set postscreen_dnsbl_whitelist_threshol
On Mon, May 13, 2013 at 09:12:57AM -0400, Wietse Venema wrote:
> /dev/rob0:
> > > I don't see any PASS OLD in there, so I guess the whitelist
> > > did the trick? Would anything else be logged?
> >
> > Hmm, I'm not sure what that was; maybe 66.220.144.
On Tue, May 14, 2013 at 12:00:00AM -0600, LuKreme wrote:
> /dev/rob0 opined on Monday 13-May-2013@06:06:27
> > All the Google, Facebook, Yahoo, et c. outbounds as well as
> > most ISPs and legitimate bulk mailers are listed in the
> > dnswl.org whitelist. Your best ch
list.dnswl.org whitelist, put it after the
permit_dnswl_client. If not, there is no point in querying it.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
might wonder how/why this mail is on hold, but I won't ask.
Instead, I will ask you to review this link before posting again:
http://www.postfix.org/DEBUG_README.html#mail
That is likely to get to the root of the problem with no further
guessing.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
NNECT
[208.66.205.36]:53814
To avoid this, I guess I'd need postscreen_greet_wait to be longer
than the 10-second dnsblog reply timeout? (Is that reply timeout
configurable?)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/
On Thu, May 16, 2013 at 07:48:24PM -0400, Wietse Venema wrote:
> /dev/rob0:
> > In the time since I've been running this, I saw the first thing
> > that might be seen as a problem: dnsblog timing out on one of
> > the DNSBL lookups:
> >
> > May 16 21:
On Fri, May 17, 2013 at 05:53:47PM +, Viktor Dukhovni wrote:
> On Fri, May 17, 2013 at 12:26:13PM -0500, /dev/rob0 wrote:
> Wietse:
> > > Increasing the greet-wait to 10+ seconds could result in
> > > legitimate clients hanging up, so I would not recommend that.
> &g
n NS record to point to
that. I'll do that tomorrow if results tonight are inconclusive.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
postfix code change to support filenotify,
> but its just a dream still here :)
Postfix runs on a lot of systems. If they don't all support
filenotify, it gets messy to try to make it work for those which are
different.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t; The log files tell me that it authenticates and entering the
> >> wrong password makes it fail etc.
> >
> > Right.
> >
> > While it is not a default, smtpd_tls_auth_only=yes is a
> > commonly recommended and wise setting. You probably have it.
Did you see this part ^^ up here?
> Sorry about that : Here is the output of postconf - n :
snip
> smtpd_tls_auth_only = yes
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t had initiated
the TCP connection, but had not yet given any commands. Non-SMTP
commands given by a client are specifically logged as such.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
no, it does not offer that feature.
You'll have to find a way in your MDA or your MUA.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t he
said.
http://www.postfix.org/POSTSCREEN_README.html
http://rob0.nodns4.us/postscreen.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
0, which your mind (as well as any
electronic calculator) equates with 2.1?
smtpd_relay_restrictions was introduced in Postfix 2.10, released
this year (2013).
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Fri, May 31, 2013 at 11:15:05AM -0400, James Zee wrote:
> On Fri, May 31, 2013 at 8:09 AM, /dev/rob0 wrote:
> > On Fri, May 31, 2013 at 12:43:51AM -0400, James Zee wrote:
snip
> > Also, you really should separate submission from your inbound
> > port 25. I only
postconf.5.html
describing the release numbering scheme. Repeat that note below at
postconf.5.html#mail_version .
In the "old way", major.minor.patchlevel versioning had real meaning.
What's wrong with that?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ttp://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ingle file certificate+key+CAs. Since you
mentioned upthread that no errors are logged, check your syslogd (try
restarting it.) These errors would be logged.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ding posts will not help.
I think the OP will have to fix the logging problem before we can
solve this issue.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
e line begins
with a Q or if end of file is reached, the connection will be closed
down.
"
Your workaround is to use lowercase "r" in your RCPT TO command:
rcpt to:
rCPT TO:
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
verrides from your submission service ]
Then configure Roundcube to connect to 127.0.0.1:10587 for sending.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
eed in either case.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tic information.
Find out which lookup fails, when, and why. postmap(1)'s -q option
helps you test your lookups.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
hen the
> machine's domain name is virtual. Is this significant?
Um, yes, that's more or less what I have been saying. :)
References which might be of interest:
http://www.postfix.org/ADDRESS_CLASS_README.html
http://www.postfix.org/postconf.5.html#append_at_myorigin
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
.
This should have gone to joeswebsite.com[216.97.227.40] and not to
mail.joeswebsite.com. (It happens to be the same address, but the
actual MX value would have been logged.) Your munged address was
clearly not 216.97.227.40.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Mon, Jun 24, 2013 at 12:34:00PM -0500, /dev/rob0 wrote:
> On Mon, Jun 24, 2013 at 03:12:24PM +0100, Craig R. Skinner wrote:
> > main.cf:
> > myorigin = $mydomain # example.com
> > mydestination = localhost, localhost.$mydomain
>
> Here we see that $myorigin (nor $my
On Mon, Jun 24, 2013 at 10:49:49PM +0100, Craig R. Skinner wrote:
> On 2013-06-24 Mon 12:34 PM |, /dev/rob0 wrote:
> > On Mon, Jun 24, 2013 at 03:12:24PM +0100, Craig R. Skinner wrote:
> > > main.cf:
> > > myorigin = $mydomain # example.com
> > > mydestinat
ME.html#relay_from
http://www.postfix.org/postconf.5.html#permit_mynetworks
http://www.postfix.org/SASL_README.html#server_sasl_authz
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nf.5.html
>
> it appears like that to me. Nonsense?
The default time unit is s (seconds), so "1200" and "1200s" are the
same thing.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
mail.example.com]:587
>
> And similarly from sender_dependent_default_transport_maps, ...
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ven. Your
followup was inadequate without "postconf -n" output.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ue to somehow confuse smtpd or
> break something?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tested.) 587 is not. Perhaps
your ISP is blocking port 25 outbound from the android tablet?
> >
> >> Check the postfix log for errors.
> >> http://www.postfix.org/DEBUG_README.html
> >> http://www.postfix.org/DEBUG_README.html#logging
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tp://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Sat, Jul 20, 2013 at 05:18:58PM -0400, Wietse Venema wrote:
> /dev/rob0:
> > The doubt in my mind about this is for mail truly destined to
> > our hosted domains. It resolves to an Internet (not an internal)
> > IP address which is in the MX instance's proxy_interfac
customers, who might need to send mail to that ex-customer.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, Jul 23, 2013 at 07:54:38AM +0200, Ulrich Zehl wrote:
> On Sat, Jul 20, 2013 at 03:45:35PM -0500, /dev/rob0 wrote:
> > They don't have "hairpin NAT" set up, whereby if I try to
> > connect to this NATed IP address it would go to the router
> > and
redirect testing
> or are the () implied if there's only one match group
So no, apparently you are right. Or this might vary with different
PCRE implementations?
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tp://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
e filter to be bypassed.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
http://www.postfix.org/postconf.5.html#mail_spool_directory
Another reference which might be of interest is the local(8) manual:
http://www.postfix.org/local.8.html
DELIVERY METHOD CONTROLS lists the precedence of delivery methods.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
s fresh and relevant and
easy to find in the logs.
OTOH I see no need for reject_unauth_destination when you're ending
your $submission_recipient_restrictions with "reject" anyway.
--
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:
ster(8) itself are processes which
run under master.
http://www.postfix.org/OVERVIEW.html
http://www.postfix.org/postfix-manuals.html (see section 8)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
type"
"inet".
It's probably not that unusual to want postscreen only on one IP
address. For example, many older sites are still providing MSA
service on port 25. You definitely do not want to put user MUAs
through postscreen.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
provements. I'll see if I can
find my wiki login and fix that.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t one line?
No, but again, that is entirely unrelated to the given subject of
"Custom routing".
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
s(5) lookup
result was encountered. There are of course 52.001 gazillion reasons
which could cause this.
Good luck. I suggest you review this before posting again:
http://www.postfix.org/DEBUG_README.html#mail
> the only match_hostname I see is for
> smtpd_client_event_limit_exceptions
--
tp://rob0.nodns4.us/postscreen.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
here are any compromised accounts, only the suspect IP
> (from which I send L3 mails) gets blocked. As mentioned earlier,
> L1 and L2 are rejected.
Oh, so it's not quite as wrong then, but I still would be very
squeamish about letting any of my IP addresses be seen as a spam
source.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
don't even want non-UBE from
known spammers. If they think they're not spamming, let them make
their case with the folks at Spamhaus, who, I can guarantee, would
love to talk to them about it.
If they're on XBL, stop the exploit! Their site is being actively
used for the benefit
l#server_access
You'll also need to read most of the "SMTP Server specific settings"
section above this. In fact you might need a specific smtpd instance
(submission port, for example) to do the client certificate checking
and verification.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Wed, Aug 21, 2013 at 07:09:32AM -0500, /dev/rob0 wrote:
> "Open" and "authorized" (which really should be "authenticated"
> in this context are contradictions in terms. "Open" means
> "anyone can relay without authentication."
"O
on and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
auth socket (no
IMAP/POP3) and do the SQL lookups.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
er AUTH. You already have the
override set for submission.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
elo=
> Aug 26 21:21:36 [postfix/tlsproxy] DISCONNECT [209.85.219.51]:41193
>
> The IP is whitelisted:
>
> http://dnswl.org/s?s=209.85.219.51
Check again. Is the logging complete? Where are the dnsblog(8) log
entries? If this is in fact all the logging you got from this
connection, you're not getting your list.dnswl.org lookup.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
; > How could change this behaviour and block this email?
> >
> > If you can arrange for a database with all the valid addresses on
> > the internet, then I can show you how to query it with Postfix.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
mtp)
I'm surprised that gmail accepted this, because most sites will use
reject_unknown_sender_domain or equivalent.
--
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:
t's not unheard of that these message rejection texts might be
lying, or incomplete, for that matter.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
client like msmtp would meet your actual needs better.
It's trivial to rewrite all outgoing mail (that which is being
relayed by the smtp(8) client) to a single From: header and envelope
sender address:
smtp_generic_maps = static:yoursen...@example.com
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Sun, Sep 01, 2013 at 10:00:38PM -0500, /dev/rob0 wrote:
> On Sun, Sep 01, 2013 at 07:30:35PM -0700, warpspasm wrote:
> > I would like to be able to have a postfix server that only
> > allows outgoing emails from one From: address.
> >
> > Any ideas? Thanks
>
l smtpd instances.
smtpd_sender_restrictions=
(and no -o to unset it for submission)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
us DNS responses, and if interested, read
more on the DNS protocol. Wikipedia might be a good start.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
t_restrictions
-o syslog_name=postfix/10027
(I might also add: I am curious about your goal and doubtful that
you've found the right solution.)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
s
revenue at stake in your sending, spend a bit of it.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ven possible?
Of course it is. But it is not possible to guess what you did.
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:
might be to warn
against using special or whitespace characters in usernames. :)
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
and sure enough, we rejected that mail. The sender got a bounce and
knew that the mail didn't get through. So the sender called to ask.
See, it's a whole lot better for interoperability in the days of 90%+
traffic being spam and abuse to reject mail than to tuck it away in a
deep, dark quarantine where no one will ever have time to look.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
;
> Is there a way?
Why was always_bcc, as suggested upthread, not adequate? Oh, that
won't have your java-mail-added headers.
I guess you want to either add another step into the mix, use a
second instance as relayhost, and always_bcc from there; or just
include this archiving functionality into your Java code.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
lobal
smtpd_sender_restrictions?
Finally: you have some sort of compromise. Blocking a sender address
might solve the immediate problem, but it will not repair the
compromise. We'll have to see more before we can advise further.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
801 - 900 of 1152 matches
Mail list logo
