| |
| |
| |
|
Page: 1 2 3 4 5
Comments:
<0> all discarded it would seem
<0> ty
<1> right
<1> May 29 14:31:40 tin postfix/smtp[10813]: A20111AC28B: to=<croak@shadypond.com>, relay=shadypond.com[71.131.5.88], delay=4, status=sent (250 Ok: queued as E36FAFAE23)
<1> May 29 14:31:40 tin postfix/smtp[10813]: A20111AC28B: to=<linux@shadypond.com>, relay=shadypond.com[71.131.5.88], delay=4, status=sent (250 Ok: queued as E36FAFAE23)
<1> May 29 14:31:40 tin postfix/smtp[10813]: A20111AC28B: to=<pollywog@shadypond.com>, relay=shadypond.com[71.131.5.88], delay=4, status=sent (250 Ok: queued as E36FAFAE23)
<1> That was one message with three recipients
<1> (Same queue ID)
<2> f3ew: how would i tell postfix to.. use virtual transport first, then callback on local. I can change the fallback_transport to local but then how do I ensure virtual was looked at first?
<0> I did not know they had to have the same ID
<1> pollywog one message has one ID
<1> Queue IDs can be reused though
<0> so it only works if the sender uses CC?
<1> pollywog or bcc
<0> k thanks, that must be why many are getting through
<1> See, Yahoo! will send you multiple single recipient messages, rather than one multi-recipient message
<1> they split the mail
<0> oic
<1> My Postfix servers didn't
<3> hi
<0> does the spamtrapped address need to be in the recipient map?
<1> pollywog as a valid address, yes
<0> k thanks, that is probably another reason it was not working
<1> or rather, in check_recipient_access
<1> yes
<0> I added it an hour or so ago
<3> hm getting weird spam lately. random domains.. what do i do against that? like darlene62@inonesearch.com, or brtcl@paparoachmail.com, silverback29@generalmail.net etc
<1> Postfix needs to know the address to discard
<3> hm
<0> I have it in check_recipient_access but did not have it in recipient map
<3> packet filter?
<0> as a valid address for my domain
<3> f3ew they have stupid subjects.. very neutral, like "everything ok" or "give me your thoughts"
<0> jax I get lots of those, usually drug related
<0> I just feed them to spam******in
<3> or "i need your help"
<3> stupid stuff >;/
<3> actualy hmm.. those are non-existant domains
<3> should i perhaps check if domain exists they are sending from?
<4> Hello, I'm wondering how I can specify custom errors on specific reject situations. ie. helo server not found and how someone can remedy the problem.
<3> f3ew what was the smtpd_recipient_restrictions to check if the domain exists in the email part?
<3> or has a valid reverse lookup
<3> reject_unknown_recipient_domain or ?
<1> reject_invalid_sender? or something
<5> reject_unknown_sender_domain
<3> ah
<3> thanks
<3> is there an easy way to test that?
<3> hm
<6> would it be evil (or possible) to reject the connection if the 'helo blabla' doesn't match the hostname from which it connects? dunno if it's error prone
<3> i tried, EHLO hi.com, MAIL FROM: bad@paparoachmail.com, RCPT TO: my@user.com -> sends
<3> eventhough paparoachmail.com reverse lookup -> domain not found
<6> Jax: are you sure you're not connecting from a host in mynetworks?
<3> checking.
<6> usually you see a permit_mynetworks, ... other restrictions..
<3> mynetworks = XX.XX.XX.0/24 127.0.0.0/8
<3> and i didn't connect from there. let me check other setting
<6> ah ok
<6> maybe you'd like to use reject_unverified_sender too
<3> you see anything wrong with this? www.gabejackson.com/settings.txt
<6> for certain domains like gmail.com
<5> smesjz: policyd-weight.org ... policy service which scores things like HELO/sender domain/client rDNS matches.
<6> looks ok to me
<3> so should drop paparoachmail.com or ?
<3> anything with MAIL FROM: x@paparoachmail.com
<3> does it need a restart? i just reloaded...
<3> no, restarted, same evilness.
<3> what's the difference between reject_unverified_sender and reject_unknown_sender_domain
<3> aha
<3> Reject the request when Postfix is not final destination for the sender address, and the MAIL FROM address has no DNS A or MX record
<3> is reject_unknown_sender_domain
<3> don't ask me why it doesn't work...
<7> i know this is not postfix related... but how Can i get all emails originating from authenticated users NOT go to amavis or not be filtered by it at least?
<7> it is somewhat postfix related :)
<3> looks like reject_unverified_sender works.. but requires a lookup.. oh well
<3> ah i know why...
<3> root@dosim: ~ # host paparoachmail.comain.cf
<3> paparoachmail.com mail is handled by 10 sitemail.everyone.net.
<3> whoops *-main.cf
<0> apparently the spamtrap addresses do not need to be in the map of allowed recipients for the system
<0> the problem was just that all my test messages and many of the spams use different IDs for each copy of the spam
<1> yup
<0> thanks for your help f3ew
<1> individual messages
<1> yw
<3> looking better now
<5> !verify
<8> rob0: Error: "verify" is not a valid command.
<5> Jax: ADDRESS_VERIFICATION_README.html
<7> so no one knows how to tell amavis not to scan to authenticated hosts?
Return to
#postfix
or
Go to some related
logs:
#ai
cheela motherboard
qdvdauthor breezy
#ai
cakePHP multi dimensional arrays
#ai
kpax character encoding
slackware libperl.so
dt_textrel gentoo
#web
|
|