On 2007/09/25 00:08, patrick keshishian wrote:
If it's compatible with how you use the domain, it might help
to publish SPF records.
> When you speak of "misconfigured mail servers bouncing spam",
The correct behaviour is to reject it at the SMTP port, rather
than issue a bounce.
Also: all hosts listed in MX records should be aware of the
list of valid users and do the same. For sendmail, this is easy
to do with the access map. For Postfix, relay_recipient_maps.
> FYI, as of now my:
These are bounces, so they'll be coming from MTAs with retry
queues, so they generally will make it through to the real MTA
after (a minimum of) 3 retry attempts.
Depending on how many "normal" spams that spamd saves you
from, it may be a hindrance to use greylisting here. It might
be better just to get these mails handled quickly and out of
the sender's queues (depends on your bandwidth situation).
On 2007/09/24 20:01, patrick keshishian wrote:
Mail-Followup-To, actually - yes. It wouldn't totally surprise
me if gmail is doing something unexpected with it, though (-:
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| James Bottomley | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Michal Piotrowski | Re: 2.6.21-rc5-mm4 |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
| Lovich, Vitali | RE: [PATCH] Packet socket: mmapped IO: PACKET_TX_RING |
git: | |
